build: unpin Hugo version #1086

Author: nroduit

content/basics/commands.en.md

@@ -58,7 +58,7 @@ COMMAND is (sequence|winLevel|zoom|pan|rotation|crosshair|measure|draw|contextMe
 g! dcmview2d:move
 Pan the selected image
 Usage: dcmview2d:move -- X Y
-X and Y are Integer. It is mandatory to have '--' (end of options) for negative values
+X and Y are Integer. It is mandatory to have '--' (the end of options) for negative values
   -? --help       show help
 {{< /highlight >}}
 
@@ -102,7 +102,7 @@ VALUE is (None|Stack|Tile)
 g! dcmview2d:wl
 Change the window/level values of the selected image (increase or decrease into a normalized range of 4096)
 Usage: dcmview2d:wl -- WIN LEVEL
-WIN and LEVEL are Integer. It is mandatory to have '--' (end of options) for negative values
+WIN and LEVEL are Integer. It is mandatory to have '--' (the end of options) for negative values
   -? --help       show help
 {{< /highlight >}}
 
@@ -126,9 +126,9 @@ Load DICOM files remotely or locally
 Usage: dicom:get ([-l PATH]... [-w URI]... [-r URI]... [-p] [-i DATA]... [-z URI]...)
 PATH is either a directory(recursive) or a file
   -l --local=PATH   open DICOMs from local disk
-  -r --remote=URI   open DICOMs from an URI
+  -r --remote=URI   open DICOMs from a URI
   -w --wado=URI     open DICOMs from an XML manifest
-  -z --zip=URI      open DICOM ZIP from an URI
+  -z --zip=URI      open DICOM ZIP from a URI
   -p --portable     open DICOMs from configured directories at the same level of the executable
   -i --iwado=DATA   open DICOMs from an XML manifest (GZIP-Base64)
   -? --help         show help
@@ -172,7 +172,7 @@ g! image:get
 Load images remotely or locally
 Usage: image:get ([-f file]... [-u url]...)
   -f --file=FILE     open an image from a file
-  -u --url=URL       open an image from an URL
+  -u --url=URL       open an image from a URL
   -? --help          show help
 {{< /highlight >}}
 
@@ -220,7 +220,7 @@ arg is an XML text in UTF8 or an url with the option '--url'
   -x --xml         open Patient Context from an XML data containing all DICOM Tags
   -i --inbound     open Patient Context from an XML data containing all DICOM Tags, decoding syntax is [Base64/GZip]
   -s --iurlsafe    open Patient Context from an XML data containing all DICOM Tags, decoding syntax is [Base64_URL_SAFE/GZip]
-  -u --url         open Patient Context from an URL (XML file containing all DICOM TAGs)
+  -u --url         open Patient Context from a URL (XML file containing all DICOM TAGs)
   -? --help        show help
 {{< /highlight >}}
 
@@ -239,6 +239,6 @@ A command containing special characters like '&' or space must be within quotes
 {{< highlight text >}}
 dicom:get -w "http://localhost/weasis-pacs-connector/manifest?patientID=97026728&modalitiesInStudy=MR"
 {{< /highlight >}}
-Depending the command line system, quotes or double quote needs to be escaped with a backslash. Ex. simple quote must be escaped in Eclipse but not in Intellij.
+Depending on the command line system, quotes or double quote needs to be escaped with a backslash. With IDE, a simple quote must be escaped in Eclipse but not in Intellij.
 {{% /notice %}}
 

content/basics/customize/build-plugins.en.md

@@ -16,7 +16,7 @@ The following list describes the types of plugins, the interfaces they implement
 1. **Media Viewer or Editor**
     - Represents the main central panel and implements either `ViewerPlugin` or `ImageViewerPlugin`.
     - The factory for this type implements `SeriesViewerFactory`.
-    - For DICOM special modalities, you can use `DicomSpecialElementFactory` to associate a viewer to a specific DICOM object.
+    - For DICOM special modalities, you can use `DicomSpecialElementFactory` to associate a viewer with a specific DICOM object.
 2. **Toolbar Associated with a Viewer**
     - Implements the `Toolbar` or `DynamicToolbar` interface.
     - The factory for this type implements `InsertableFactory`
@@ -147,7 +147,7 @@ This feature will be available soon. It will allow you to manage the plugins and
 ### Build OSGi Services
 
 All the plugin type described in the list above are OSGi services that are registered and aggregated in the GUI. Building the plugin from the Maven archetype will configure the OSGi service automatically. For adding new OSGi services, here is the procedure:
-1. Create a class that implements the `Insertable` interface and represents a visual component. For example:
+1. Create a class that implements the `Insertable` interface and represents a visual component. For example,
     {{< highlight java >}}
     public class MyPrefView extends AbstractItemDialogPage {
 
@@ -173,7 +173,7 @@ All the plugin type described in the list above are OSGi services that are regis
     }
     {{< /highlight >}}
 
-2. Create a class that implements one of the plugin factories and include the annotations `@Component` and the `@Service` parameter. For example:
+2. Create a class that implements one of the plugin factories and include the annotations `@Component` and the `@Service` parameter. For example,
 {{< highlight java >}}
 @org.osgi.service.component.annotations.Component(service = PreferencesPageFactory.class)
 public class MyViewerPrefFactory implements PreferencesPageFactory {

content/basics/customize/integration.en.md

@@ -7,13 +7,13 @@ keywords: [ "workflow", "integration", "dicom viewer", "free dicom viewer", "ope
 
 ## <center>How to launch Weasis from any environments</center>
 
-Here we present how to launch Weasis with associated images from any context either [using weasis-pacs-connector](#use-weasis-pacs-connector) or [ViewerHub](../../../viewer-hub) as its successor,
+Here we present how to launch Weasis with associated images from any context either [using weasis-pacs-connector](#use-weasis-pacs-connector) or [ViewerHub](../../../viewer-hub) as its successor
 or by [building your own connector](#build-your-own-connector). The launch of the application is based on the [weasis protocol](../../../getting-started/weasis-protocol) available since {{% badge title="Version" %}}3.5.3{{% /badge %}}.
 
 Using [weasis-pacs-connector](https://github.com/nroduit/weasis-pacs-connector) or [ViewerHub](../../../viewer-hub) allows a high degree of integration and facilitates connection to a PACS. Here are some of the advantages:
 
 - Automatically build a manifest according to a configuration with a PACS
-- The initial URL starts with HTTP and is then redirected to weasis://? (useful when custom URI scheme is not allowed by wiki, blog platforms, etc.)
+- The initial URL starts with HTTP and is then redirected to weasis://? (useful when a custom URI scheme is not allowed by wiki, blog platforms, etc.)
 - Efficiently manages to build the manifest simultaneously with the start of Weasis, optimizing loading time
 - Easily handles secure manifest requests and manages tokens for the DICOMWeb services
 

content/demo.en.md

@@ -69,7 +69,7 @@ Expected Output:
 
 #### Pixel Depth (9-bit to 16-bit)
 
-Tests with different pixel depths to ensure correct image rendering.
+Tests with different pixel depths to ensure the correct image rendering.
 
 {{% notice info %}}
 **Expected Output**: Images rendered identically regardless of pixel depth.
@@ -247,7 +247,7 @@ $dicom:get -w "https://nroduit.github.io/demo-archive/demo/video.xml"
 {{< /launch >}}
 
 {{% notice info %}}
-Open the default viewer (associated to the video mime type) of the operating system.
+Open the default viewer (associated with the video mime type) of the operating system. On Windows, it uses the Windows Media Player, which does not have an MPEG-2 codec installed by default. You can use VLC or any other video player.
 {{% /notice %}}
 
 ------------------------------------------------------------------------

content/description-2.en.md

@@ -5,8 +5,8 @@ Weasis has been designed to meet the evolving needs of clinical information syst
 - **Data type support**
   - Weasis provides a highly detailed implementation of the DICOM standard, enabling effortless display and interaction with most types of DICOM files.
   - Display most DICOM files including multi-frame, enhanced, MPEG-2, MPEG-4, MIME Encapsulation, DOC, SR, PR, KOS, SEG, AU, RT, and ECG
-  - Display DICOM image containing float or double data (Parametric Map)
-  - Import DICOM files with DICOM Query/Retrieve (C-GET, C-MOVE and WADO-URI) and DICOMWeb (QUERY and RETRIEVE)
+  - Display DICOM images containing float or double data (Parametric Map)
+  - Import DICOM files with DICOM Query/Retrieve (C-GET, C-MOVE, and WADO-URI) and DICOMWeb (QUERY and RETRIEVE)
   - Import and export DICOM CD/DVD with DICOMDIR
   - Import and export DICOM ZIP files
   - Viewer for common image formats (TIFF, BMP, GIF, JPEG, PNG, RAS, HDR, and PNM)

content/free-dicom-viewer.en.md

@@ -25,7 +25,7 @@ Weasis has been designed to meet the evolving needs of clinical information syst
     - Weasis provides a highly detailed implementation of the DICOM standard, enabling effortless display and interaction with most types of DICOM files.
     - Display most DICOM files including multi-frame, enhanced, MPEG-2, MPEG-4, MIME Encapsulation, DOC, SR, PR, KOS, SEG, AU, RT, and ECG
     - Display DICOM image containing float or double data (Parametric Map)
-    - Import DICOM files with DICOM Query/Retrieve (C-GET, C-MOVE and WADO-URI) and DICOMWeb (QUERY and RETRIEVE)
+    - Import DICOM files with DICOM Query/Retrieve (C-GET, C-MOVE, and WADO-URI) and DICOMWeb (QUERY and RETRIEVE)
     - Import and export DICOM CD/DVD with DICOMDIR
     - Import and export DICOM ZIP files
     - Viewer for common image formats (TIFF, BMP, GIF, JPEG, PNG, RAS, HDR, and PNM)

content/getting-started/_index.en.md

@@ -16,7 +16,7 @@ Since version 4, only the distribution with a native installer is maintained to
 For details about GLIBC versions and Linux distribution compatibility, see this [page](https://repology.org/project/glibc/versions).
 
 {{% notice note %}}
-To manage Weasis version at the server side, it is possible to install the [Weasis web package](https://github.com/nroduit/weasis-pacs-connector#installation) which will upgrade the native installation at the client side (it works for minor releases by updating all the plugins except the launcher).<br>
+To manage a Weasis version at the server side, it is possible to install the [Weasis web package](https://github.com/nroduit/weasis-pacs-connector#installation) which will upgrade the native installation at the client side (it works for minor releases by updating all the plugins except the launcher).<br>
 Explore more integration possibilities with other systems [here](../basics/customize/integration).
 {{% /notice %}}
 

content/getting-started/dcm4chee.en.md

@@ -11,7 +11,7 @@ Weasis is launched from the dcm4chee administrative web interface with the [weas
 
 ![dcm4chee-arc-light](/gallery-dcm4chee/1Weasis%20in%20dcm4chee-arc-light.png?classes=border "dcm4chee-arc-light")
 
-For a simpler and faster installation without server components, please follow these [instructions](../../basics/customize/integration/#download-directly-with-dicomweb-restful-services); no need to consider the following points on this page. Otherwise if you need more advanced configurations then follow these steps:
+For a simpler and faster installation without server components, please follow these [instructions](../../basics/customize/integration/#download-directly-with-dicomweb-restful-services); no need to consider the following points on this page. Otherwise, if you need more advanced configurations, then follow these steps:
 
 1. [Install dcm4chee](https://github.com/dcm4che/dcm4chee-arc-light/wiki), if not already done (Installation with Docker is straightforward).
 
@@ -51,9 +51,9 @@ deployment-overlay add --name=dcm4chee-arc --deployments=weasis-pacs-connector.w
 5. To activate Weasis in the dcm4chee-arc-light user interface (see the matrix of the required versions in the table below):
  you need to add attributes by either editing docker-compose.env (from 5.22.0) or from the left menu Configuration > Devices > dcm4chee-arc > Extensions > Edit extension > Child Objects > Web Applications > DCM4CHEE (add `&cdb` to the URL if weasis.war has not been deployed on the server-side):
      - Configure the URL for having a view button for the patient or study level.
-        - From dcm4chee-arc-light 5.10.2 to 5.19.0 the left menu Configuration > Devices > dcm4chee-arc > Extensions > Archive Device
+        - From dcm4chee-arc-light 5.10.2 to 5.19.0, the left menu Configuration > Devices > dcm4chee-arc > Extensions > Archive Device
         - From dcm4chee-arc-light 5.19.1 the left menu Configuration > Devices > dcm4chee-arc > Extensions > Edit extension > Child Objects > Web Applications > DCM4CHEE
-        - From dcm4chee-arc-light 5.22.0 by editing docker-compose.env (It allows you to directly apply the properties when deploying, then the can be edited in the web portal). Note: the character ‘&’ must be escaped (e.g. IID_STUDY_URL=../../weasis-pacs-connector/weasis?studyUID={{studyUID}}\\&access_token={{access_token}})
+        - From dcm4chee-arc-light 5.22.0 by editing docker-compose.env (It allows you to directly apply the properties when deploying, then they can be edited in the web portal). Note: the character ‘&’ must be escaped (e.g., IID_STUDY_URL=../../weasis-pacs-connector/weasis?studyUID={{studyUID}}\\&access_token={{access_token}})
 {{% notice note %}}
 **URL parameters**
 

content/getting-started/guidelines.en.md

@@ -28,7 +28,7 @@ Weasis uses [google-java-format](https://github.com/google/google-java-format) a
 ### Getting the source and building Weasis
 
 - Getting the Source
-  - For external Git client, see [Building Weasis](../building-weasis).
+  - For an external Git client, see [Building Weasis](../building-weasis).
   - From IntelliJ IDEA: *New > Project from Version Control...*
     - In the *Get from Version Control* dialog, select the menu *Repository URL* and enter the following URL: `https://github.com/nroduit/Weasis.git` (public repository)
 - Building Weasis plugins
@@ -75,7 +75,7 @@ In Eclipse launcher parameters, '&' within URLs needs to be escaped with a backs
   - Defines a new user (for getting specific preferences): `-Dweasis.user=user1`
   - Examples with specific configuration files:
     - For launching Weasis Dicomizer: `-Dfelix.extended.config.properties=file:target/conf/dicomizer.json`
-    - Configuration from an URL: `-Dfelix.extended.config.properties=https://mysite.com/weasis/conf/config.json`
+    - Configuration from a URL: `-Dfelix.extended.config.properties=https://mysite.com/weasis/conf/config.json`
 {{% notice note %}}
 **felix.config.properties** defines the location of base.json (the OSGI configuration and the list of plugins to install/start)<br>
 **felix.extended.config.properties** defines the location of a json file (extends/overrides base.json)

content/getting-started/translating.en.md

@@ -8,7 +8,7 @@ weight: 80
 Translation files are hosted and managed on the [Transifex](https://app.transifex.com/weasis/public/) website. Get an account and help to translate to your language! If your language is missing, just head over to Transifex and request a new language.
 
 {{% notice warning %}}
-**Text length**: The translations for many languages frequently exceed the length of the corresponding English source. It could be a problem for the layout of graphical components (e.g. buttons). Some elements have a character limit on the translation tool.
+**Text length**: The translations for many languages frequently exceed the length of the corresponding English source. It could be a problem for the layout of graphical components (e.g., buttons). Some elements have a character limit on the translation tool.
 {{% /notice %}}
 
 {{% notice tip %}}
@@ -23,7 +23,7 @@ For special words or particular contexts look at the "Instructions" text box (gi
 To obtain daily built packages, see this [page](https://github.com/nroduit/weasis-i18n).
 
 {{% notice note %}}
-That means the translation packages can be deployed at any time, it does not need to follow the Weasis life cycle. With remote packages, the plugin translation will be updated by Weasis only if the timestamp number has changed. This timestamp is set during the build phase described below.
+That means the translation packages can be deployed at any time; it does not need to follow the Weasis life cycle. With remote packages, the plugin translation will be updated by Weasis only if the timestamp number has changed. This timestamp is set during the build phase described below.
 {{% /notice %}}
 
 {{% notice info %}}
@@ -54,7 +54,7 @@ Go in the *weasis-i18n* directory, Compile and install all the plugins in the lo
 $ mvn clean install -Dtransifex.token="<your-token>"
 {{< /highlight >}}
 
-All the APIs require to be authenticated. So the value "your-token" must be replaced by your generate token, see how to [get this token](https://docs.transifex.com/account/authentication) on Transifex.
+All the APIs require to be authenticated. So the value "your-token" must be replaced by your generated token, see how to [get this token](https://docs.transifex.com/account/authentication) on Transifex.
 
 Command if you are behind a proxy server:
 {{< highlight bash >}}
@@ -67,7 +67,7 @@ The distribution files are located in the *weasis-i18n-dist/target/dist* folder.
 
 ### Apply the translations
 
-The translation package can be built manually as described below or it is automatically built every 24 hours and can be downloaded from [here](https://github.com/nroduit/weasis-i18n#download-the-binary-package). When [Building Weasis](../building-weasis), the last package is downloaded automatically.
+The translation package can be built manually as described below, or it is automatically built every 24 hours and can be downloaded from [here](https://github.com/nroduit/weasis-i18n#download-the-binary-package). When [Building Weasis](../building-weasis), the last package is downloaded automatically.
 
 * In order to update Weasis with new translations, unzip weasis-i18n.zip and either:
   * Pass the weasis.i18n location into the [launch command](../weasis-protocol/#modify-the-launch-parameters):