Fix passing of non-ASCII characters as command-line arguments

[lassoan]

Should fix the issues described here: https://discourse.slicer.org/t/slicer-ignoring-command-line-path-with-accents/24569

[jcfr]

Overall looks great 👍

It the use of QLatin1String instead of QString::fromLatin1 for stylistic reason ?

[lassoan]

It the use of QLatin1String instead of QString::fromLatin1 for stylistic reason ?

Yes, I just chose QLatin1String because it indicates that it is simply a constant definition and it is not a conversion.

I could not test it (just the compilation), so it would be great if you could test it on Linux as described here.

[jcfr]

Thanks for the detailed explanation. I will test tomorrow and then move forward with creating a new release.

[achataigner]

Would it be possible to merge this branch ?
It would simplify my work which uses slicer python interpreter: https://discourse.slicer.org/t/python-interpreter-arguments-containing-special-characters/33466

[achataigner]

Any feedback ? @jcfr

[lassoan]

This is still a problem - https://discourse.slicer.org/t/patientname-and-rus-language-trouble/28870/9

[jcfr]

Once continuous integration is fixed, the branch associated with this pull request will be rebased.

Related pull requests:

• COMP: Fix GitHub workflow using current "macos-12" runner #129
• COMP: Fix appveyor package upload by using "Python38-x64" instead of "Python27-x64" #130
• COMP: Fix setup of CircleCI python env. used to upload package #131
• COMP: Update Appveyor ensuring latest version of scikit-ci-addons is installed #132
• COMP: Attempt to fix restoration of cache in upload job #133
• COMP: Update appveyor secure env. value associated with GITHUB_TOKEN #134