@eapache ever since XP, Windows has supported the notion of "subsystems" within the operating system. This allows support of, for example, a POSIX subsystem within Windows. In theory, this is a useful feature, but really almost no one uses any other subsystem except for the standard Windows NT one. So ntfs-3g can't make the assumption that a certain character is invalid for a filename, since even if it's invalid in one subsystem, it may not be in another.
The best way to fix this bug would be to add some kind of check in nautilus (or dolphin, etc.) so that if it detects you are trying to write a file to an ntfs filesystem, it warns you. This could be expanded to support other filesystems as well. For example, if you have some filesystem for BeOS mounted that doesn't support some random character, nautilus can warn you before you write to it. This would be kind of a big fix though. Anyone want to draw up a blueprint or do a brainstorm for this or otherwise take the lead? -- Using special characters in filenames prevents Windows from opening https://bugs.launchpad.net/bugs/230906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
