|
So in OS X, the replaced characters won't cause you problems - OS X, like most UNIXes, doesn't assign special meaning to characters in file names. If you are using Windows instead, you would find files with certain characters incredibly difficult to create in the first place, and even harder to work with if you do manage to create them. The reason is that Windows declares certain characters as forbidden in file names and, instead of writing NTFS to forbid them, assumes that you never create them in the first place.
For myself, it was simpler to just write the driver to replace all the characters all the time. As for why it's not in the base driver or in calibre, that's probably because it hasn't come up outside this crowd or no one's reported it to Kovid. Is there a reason you need the characters to not be replaced?
|