Comment 15 for bug 318625

Isn't the whole idea of NTFS-3G to allow proper and full compatibility with the *Windows* implementation of NTFS? Isn't it to allow true interoperability? Thus, given that Windows considers certain characters to be illegal should mean that they are treated as illegal for NTFS drivers on other platforms, purely based on the premise that it is about full interoperability.

Yes, the fact that Windows doesn't like certain characters in its implementation of NTFS is likely an aberration from the POSIX namespace guidelines, but then it is the *reference implementation*.

Additionally, consider that there are many exceptions to rules within the Win32 API. The WINE project is constantly working around exceptions that are undocumented and/or that go against existing documentation on aspects of the API.

Making workarounds in every little app is redundant and counter productive when it could and, in my view, should be solved by making this simple change in NTFS-3G.