I tried to pass a filename like this to a CMD file in NEXUS v26.6:
Testː Some other Text.pdf

As the usual colon ( : ) is a forbidden character in Windows, I have replaced it with a similar-looking character ( ː ) U+02D0 MODIFIER LETTER TRIANGULAR COLON.

As soon as I try to pass such a file name from Windows File Explorer to an icon in the NEXUS dock, a new element is created. There is no way to execute it using one of the added tools. The same is true for elements like "Show properties".

Why are special characters replaced with a zero?
("Test0 Some other Text.pdf" in this example)


Is there a way to retrieve the original, unmodified file name as passed from Windows File Explorer?

Unfortunately one of the biggest limitations of the Winstep application due to when it started being developed, is that internally it is ANSI, not Unicode.

It is able to run and function properly under different Windows languages (even with DBS character sets like Korean, Japanese, Chinese, etc) provided the proper code page (system locale) is set, but if you pass it a character that cannot be properly converted according to the current system code page, you get a "?".