GNOME Bugzilla – Bug 744113
Recent files handling should handle non-filesystem file encodings
Last modified: 2017-12-13 19:10:17 UTC
As it stands, the recent files handling assumes that filenames can be round-tripped to and from the file system encoding, which is sadly very incorrect, and that therefore it's fine to store file names as UTF-8 encoded bytes. This works about 99.5% of the time, and then it breaks. When it breaks, it doesn't actually take out anything... you just can't open the recent comparison. As such, this isn't as drastically awful as it would otherwise be. For anyone interested in looking at this, we need to store the actual filename bytes in the recent comparison file, and be *very* paranoid about receiving Python unicodes as filenames, since it's almost certainly going to happen.
This has changed with Python 3. We should probably be using the surrogate escape mechanism, or investigate whether this is even an issue given that we're actually storing file URIs now.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/meld/issues/81.