GNOME Bugzilla – Bug 423271
normalize saved filenames for conflict
Last modified: 2009-06-03 14:18:32 UTC
When saving a file, if there's already a file existing with a canonically equivalent name, they should conflict and be considered to have the same name, i.e. ask the user to overwrite the other. For example, a file "école" is in the working directory, and a file "école" is going to be saved. These are the same name for the user, they should be considered as such by the application. Note: first name has <U+0065 LATIN SMALL LETTER E + U+0301 COMBINING ACUTE ACCENT> second name has <U+00E9 LATIN SMALL LETTER E WITH ACUTE> When saving a new file, the name should probably be normalized, NFC is probably the safest for compatibility with legacy systems.
blocks meta bug 423036
Do you have examples of gnome applications that do this? - Mike
Mike: I don't know any gnome application that does this for file saving. Actually looking at the gthumb code it seems it just uses the default gtk filechooser. So it would be fixed if the filechooser handled it. See bug 421736 For other things this should be fixed in gthumb, like for the File > New Folder. It must also be fixed for categories and catalog are created.
Partly fixed in svn rev 1516 - category / library names are normalized. Do we want to normalize all new file filenames, or will users be annoyed by that assumption? - Mike
In trunk, filenames are handled using gfile, so this is obsolete. Closing bug.