Fix encoding in recent browsers. Use query param in weasis protocol

Author: nroduit

.github/workflows/hugo.yaml

@@ -32,7 +32,7 @@ jobs:
   build:
     runs-on: ubuntu-latest
     env:
-      HUGO_VERSION: 0.140.2
+      HUGO_VERSION: 0.145.0
       HUGO_GH_TOKEN: ${{ secrets.HUGO_GH_TOKEN }}
     steps:
       - name: Install Hugo CLI

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

@@ -130,13 +130,13 @@ To test the plugin with an installed version of Weasis without making any change
     - Build a valid URI with the above parameter (see [How to build an URI](../../../getting-started/weasis-protocol/#how-to-build-a-uri)) and launch Weasis from the command on a terminal:Construct a valid URI using the parameter mentioned above (refer to [How to build a URI](../../../getting-started/weasis-protocol/#how-to-build-a-uri))) and launch Weasis from the terminal using a command:
       {{< tabs groupid="launchPlugin">}}
       {{% tab title="Windows" %}}
-      start weasis://%24weasis%3Aconfig%20pro%3D%22felix.extended.config.properties%20file%3A%2F%2F%2FD%3A%2Fgit%2Fmyplugin%2Fmyplugin.json%22
+      start weasis://?%24weasis%3Aconfig%20pro%3D%22felix.extended.config.properties%20file%3A%2F%2F%2FD%3A%2Fgit%2Fmyplugin%2Fmyplugin.json%22
       {{% /tab %}}
       {{% tab title="Linux" %}}
-      xdg-open weasis://%24weasis%3Aconfig%20pro%3D%22felix.extended.config.properties%20file%3A%2F%2F%2Fgit%2Fmyplugin%2Fmyplugin.json%22
+      xdg-open weasis://?%24weasis%3Aconfig%20pro%3D%22felix.extended.config.properties%20file%3A%2F%2F%2Fgit%2Fmyplugin%2Fmyplugin.json%22
       {{% /tab %}}
       {{% tab title="macOS" %}}
-      open weasis://%24weasis%3Aconfig%20pro%3D%22felix.extended.config.properties%20file%3A%2F%2F%2Fgit%2Fmyplugin%2Fmyplugin.json%22
+      open weasis://?%24weasis%3Aconfig%20pro%3D%22felix.extended.config.properties%20file%3A%2F%2F%2Fgit%2Fmyplugin%2Fmyplugin.json%22
       {{% /tab %}}
       {{< /tabs >}}
 

content/basics/customize/integration.en.md

@@ -13,7 +13,7 @@ or by [building your own connector](#build-your-own-connector). The launch of th
 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 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
 
@@ -135,15 +135,15 @@ Use [$dicom:rs](../../commands/#dicomrs) to load DICOM files. Here are some conf
 
 This configuration requires at least dcm4chee-arc-light 5.22.2 and Weasis 3.6.0. To activate Weasis in dcm4chee-arc-light user interface, you need to add the four following properties in the web portal from the left menu *Configuration > Devices > dcm4chee-arc > Extensions > Edit extension > Child Objects > Web Applications > DCM4CHEE*
 {{< highlight text >}}
-IID_PATIENT_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "patientID={{patientID}}" --query-ext "&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
-IID_STUDY_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "studyUID={{studyUID}}" --query-ext "&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
+IID_PATIENT_URL=weasis://?$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "patientID={{patientID}}" --query-ext "&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
+IID_STUDY_URL=weasis://?$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "studyUID={{studyUID}}" --query-ext "&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
 IID_URL_TARGET=_self
 {{< /highlight >}}
 
 The properties can also be passed directly to the docker-compose.env file:
 {{< highlight text >}}
-IID_PATIENT_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "patientID={{patientID}}" --query-ext "\&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
-IID_STUDY_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "studyUID={{studyUID}}" --query-ext "\&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
+IID_PATIENT_URL=weasis://?$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "patientID={{patientID}}" --query-ext "\&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
+IID_STUDY_URL=weasis://?$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "studyUID={{studyUID}}" --query-ext "\&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
 IID_URL_TARGET=_self
 {{< /highlight >}}
 

content/getting-started/weasis-protocol.en.md

@@ -5,41 +5,41 @@ keywords: [ "web", "launch", "dicom viewer", "free dicom viewer", "open source d
 weight: 15
 ---
 
-The **Weasis Protocol** enables the launch of Weasis (starting from {{< badgeC "v3.6.0" >}}) in a web context using a specific URI scheme: `weasis://commands`.
+The **Weasis Protocol** enables the launch of Weasis (starting from {{< badgeC "v3.6.0" >}}) in a web context using a specific URI scheme: `weasis://?commands`.
 
 ### How to Use the Weasis Protocol
 
 To launch Weasis from various contexts:
-1. **From a Web Page**: Create a link that begins with `weasis://` (see below [How to build an URI](#how-to-build-a-uri)).<br>
+1. **From a Web Page**: Create a link that begins with `weasis://?` (see below [How to build an URI](#how-to-build-a-uri)).<br>
    If certain web frameworks (e.g. WIKI) or contexts only support HTTP protocols, you can use a URL redirection starting with `https://`. A tool such as [Weasis PACS Connector](https://github.com/nroduit/weasis-pacs-connector">weasis-pacs-connector) can assist with this.
 2. **From the Command Line**: Utilize the appropriate Weasis command from the terminal:
 {{< tabs groupid="launchWeasisProtocol">}}
 {{% tab title="Windows" %}}
 {{< highlight shell >}}
-start weasis://%24dicom%3Aget+-w+%22https%3A%2F%2Fnroduit.github.io%2Fdemo-archive%2FLumbar%2Fmf.xml%22
+start weasis://?%24dicom%3Aget+-w+%22https%3A%2F%2Fnroduit.github.io%2Fdemo-archive%2FLumbar%2Fmf.xml%22
 {{< /highlight >}}
 {{% /tab %}}
 {{% tab title="Linux" %}}
 {{< highlight shell >}}
-xdg-open weasis://%24dicom%3Aget+-w+%22https%3A%2F%2Fnroduit.github.io%2Fdemo-archive%2FLumbar%2Fmf.xml%22
+xdg-open weasis://?%24dicom%3Aget+-w+%22https%3A%2F%2Fnroduit.github.io%2Fdemo-archive%2FLumbar%2Fmf.xml%22
 {{< /highlight >}}
 {{% /tab %}}
 {{% tab title="macOS" %}}
 {{< highlight shell >}}
-open weasis://%24dicom%3Aget+-w+%22https%3A%2F%2Fnroduit.github.io%2Fdemo-archive%2FLumbar%2Fmf.xml%22
+open weasis://?%24dicom%3Aget+-w+%22https%3A%2F%2Fnroduit.github.io%2Fdemo-archive%2FLumbar%2Fmf.xml%22
 {{< /highlight >}}
 {{% /tab %}}
 {{< /tabs >}}
 
 ### How to Build a URI
-The `weasis://` URI scheme allows you to launch Weasis directly from the system's URI handler. By constructing the correct URI path, you can execute [Weasis commands](../../basics/commands) to load images or perform other actions.
+The `weasis://?` URI scheme allows you to launch Weasis directly from the system's URI handler. By constructing the correct URI path, you can execute [Weasis commands](../../basics/commands) to load images or perform other actions.
 
 [Weasis PACS Connector](https://github.com/nroduit/weasis-pacs-connector#launch-weasis) can dynamically generate manifests (listing references for images to load) and build the required URI through an API. This tool also manages user preferences and other launch parameters.
 
 If you're not using the Weasis PACS Connector, you can build a URI manually by following these steps:
 1. **Choose Commands**: Select one or more [commands](../../basics/commands) to execute.
 2. **Encode the Commands**: Use a URL encoder to format the commands correctly for URI inclusion.
-3. **Prefix the Commands**: Add the `weasis://` scheme at the beginning of the encoded command string to create the final URI.
+3. **Prefix the Commands**: Add the `weasis://?` scheme at the beginning of the encoded command string to create the final URI.
 
 ##### Example: Loading a Remote Image
 1. Use [$dicom:get](../../basics/commands/#dicomget) to load an image from URL
@@ -50,7 +50,7 @@ $dicom:get -r "https://nroduit.github.io/demo-archive/us-palette.dcm"
 {{< highlight text >}}
 %24dicom%3Aget+-r+%22https%3A%2F%2Fnroduit.github.io%2Fdemo-archive%2Fus-palette.dcm%22
 {{< /highlight >}}
-3. Make the final URI by adding "weasis://" at the beginning
+3. Make the final URI by adding "weasis://?" at the beginning
 {{< launch title="Open the remote image" >}}
 $dicom:get -r "https://nroduit.github.io/demo-archive/us-palette.dcm"
 {{< /launch >}}

layouts/shortcodes/launch.html

@@ -3,7 +3,7 @@
 {{- $style := .Get "style" | default "transparent" }}
 {{- $title := .Get "title" | default "Launch" }}
 <span class="btn cstyle {{ $style }}">
-  <a href="weasis://{{ urlquery $cmd }}" class="no-lightbox">
+  <a href="weasis://?{{ urlquery $cmd }}" class="no-lightbox">
     <i class="fa-fw fas fa-play"></i>
     {{ $title }}
   </a>