I think that this solution is complex to implement (it's very clever, but complex at coding level), and I'm not sure it worths it given the amount of users who can be suffering from this issue.
What worries me the most is: * the translation table/function needs a lot of care and design and test, it can be very easy to make a tiny mistake. How long will it takes us to stabilize it? * the end users will start reporting that "the file names were messed up" by Ubuntu One. Usually, end users are not aware of encodings, and much less of the possible encoding issues, and if they see the same file with different name they'll report that as a bug. Likewise, they may think that a file disappeared, and actually the file may have been renamed. -- We should support utf8-invalid filenames https://bugs.launchpad.net/bugs/368626 You received this bug notification because you are a member of Ubuntu Bugs, which is a subscriber of a duplicate bug. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
