Comment 57 for bug 510018
Revision history for this message
|
|
#57 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
(In reply to comment #48)
> If wget can generate file names that are out of the locale encoding, wget needs
> to be fixed. Same as the Zip extractor.
>
I am OK if KDE's position is that my data is broken. For KDE, having a non-utf-8 file name is similar to have a corrupted filesystem. That would be OK for me, but:
* Base system tools allow me to create non-utf-8 filenames, so this is a requirement from KDE, not from my operating system.
* When I have broken data, I have tools to check if my data is corrupted. I have fsck, I have database consistency check tools. But I don't have _any_ tool to check if my filesystem is considered "broken" by KDE. All I have are cryptic error messages shown when I try to handle a non-utf8 filename. This, IMHO, is the worst part about this issue.