CLI on Windows fails when using non-ASCII characters in directories or filenames

If you are used to using OSX or some *inx variant you might get stuck when using the CLI on Windows if your file/directory names contain non-ASCII characters. One example might be some filenames looking like this:

./.domino/repo/my_files/my_files?inary_siso_lstm_catembedd.csv
./.domino/repo/my_files/my_files?ocal_binary_siso_single_layer_lstm_model.csv
./.domino/repo/my_files/my_files?inary_siso_multi_layer_lstm_model.csv
./.domino/repo/my_files/my_files?inary2_miso_lstm_catembedd.csv
./.domino/repo/my_files/my_files?inary_siso_single_layer_lstm_model.csv
./.domino/repo/my_files/my_files?inary_simo_single_layer_lstm_model.csv
./.domino/repo/my_files/my_files?inary_simo_lstm_catembedd.csv
./my_files/my_files?inary_siso_lstm_catembedd.csv
./my_files/my_files?ocal_binary_siso_single_layer_lstm_model.csv
./my_files/my_files?inary_siso_multi_layer_lstm_model.csv
./my_files/my_files?inary2_miso_lstm_catembedd.csv
./my_files/my_files?inary_siso_single_layer_lstm_model.csv
./my_files/my_files?inary_simo_single_layer_lstm_model.csv
./my_files/my_files?inary_simo_lstm_catembedd.csv

The offending characters, in this case, is showing up by displaying a question mark. Looking in the UI will most likely (depending on what the character is) show as a block or something else.

If you try to use the CLI on Windows it will generate an error looking something like this:

Unexpected error: failure getting the project myproject.  
domino.client.command.GetCommand.get(GetCommand.scala:44) 
domino.client.Domino.executeCommand(Domino.scala:195) 
domino.client.Domino$.main(Domino.scala:41) domino.client.Domino.main(Domino.scala) 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
java.lang.reflect.Method.invoke(Method.java:498) com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84) 
com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25)

To fix this you need to rename/remove the offending files. As you might have thousands of files to locate this is easiest by launching a Workspace and running a simple shell command.

LC_ALL=C find . -name '*[! -~]*'

Fix the offending files/directories and you should be good to go.