[Windows] Garbled filenames and broken extensions when using symbols in filenames

[Mr-Cyborg]

OS: Microsoft® Windows 7 Ultimate 64-bit
Filesystem: NTFS
Origin Hash: 50b3c3dda8717681a2c922b360b8262dc10ed30e

SYNOPSIS

File names containing symbols (e.g. ™, ©, ®, etc) produces garbled text and break the file extension under NTFS. Further testing on UNIX pending.

STEPS TO REPRODUCE

1. Start Nimble Writer.
2. Save a file using any currently implemented method with a symbol (e.g. ™, ©, ®, etc).
3. The final result will be garbled text in place of the symbol and any subsequent characters (including the file extension) will be gone.

NOTES

• Appending the ".nwd" file extension returns the file to a functional state with data preserved.
• Adding ".nwd" in the save file dialog(s) leads to an even more cryptic file name (see the third image).

RESOURCES

[codecat]

I believe this is fixed in the current build but I haven't had the chance to test it yet. Can you confirm?

[Mr-Cyborg]

ADDENDUM 05/09/2016 19:
OS: Microsoft® Windows 7 Ultimate 64-bit
Filesystem: NTFS
Addendum Hash: ef9bd9bfd8ca4e2561692ed86ef061e946f8b4c6

SYNOPSIS

Files whose name contains symbols (e.g. ™, ©, etc) do not display correctly on Microsoft® Windows 7's Windows Explorer running the NTFS filesystem. Testing still pending on UNIX systems.

STEPS TO REPRODUCE

1. Start Nimble Writer
2. Save a file using any currently implemented method with a symbol (e.g. ™, ©, ®, etc).
3. The file name will produce a garbled string of characters where the symbol should be present (see the image under "RESOURCES").

IMPROVEMENTS SINCE ORIGIN HASH

• The extension along with any subsequent text in the file name is now preserved.

NOTES

• Symbols show up perfectly fine in the title bar and in the open file dialog.
• Testing was conducted using the following file names: foobar™, foo™bar

RESOURCES