In Windows it is appropriate to associate a program to a file extension. For a file named myfile.myext, with myapp.exe associated to the extension myext, typically myapp.exe is called with the following command line:
All the user has to do, is double-clicking on myfile.myext to start myapp for myfile.ext. Windows creates above commandline and starts the application.
If myfile.myext its name start with an accent, such as eg.: 'accentedName.myext (including the accent) the command line will be "path_to_my_app\myapp.exe" "path_to_myfile\'accentedName.myext"
Another solution would be to interpret a program parameter specifying whether to interpret the escape sequence or not. For instance -noEscapeQuote
"path_to_my_app\myapp.exe" -noEscapeQuote "path_to_myfile\'accentedName.myext"
could leave the (next) program argument unchanged.
would interpreted in the actual way.
An actual workaround in Windows could be by explicitly calling GetCommandLine and using a function inspired by qWinCmdLine and the remarks above.
Similar remarks are valid if a folder in the path to the application first letter is an accent.