Comment 12 for bug 135320
Revision history for this message
| codeslinger (codeslinger) wrote Re: bzr merge - exceptions.UnicodeDecodeError | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
people working on this bug should also consider Bug #3918 these bugs have much in common and are probably related.
special characters ought to be allowed in file names, however misguided they may be, they do exist in common user scenarios.
consider for instance a Japanese freeware icon editor, which although published in English, it has a file with Japanese characters in the name... but this is on a windows system which sees those as being single byte special characters, and being accessed on Linux via FUSE. Suddenly you have a mess. It is not okay to arbitrarily disregard characters however strange they may appear to be. Bottom line is that if the file system allows it to exist then bzr ought to support/preserve it.