[Bug 165044] Dolphin can't handle well files/folders with wrong encoding

[Thiago Macieira]

http://bugs.kde.org/show_bug.cgi?id=165044





--- Comment #18 from Thiago Macieira <thiago kde org>  2008-09-01 10:25:47 ---
Windows and MacOS X are fully Unicode. There's no such thing as broken paths on
Windows, since it uses UTF-16; on MacOS X, which is UTF-8, Finder shows as
"C%F3digo" (i.e., URL encoding, which we do support), but simple applications
like TextEdit crash while trying to use the file.

No, broken encodings are a thing of the past and should be confined to the
terminal, where it belongs. Applications for the past 5 years have created
files in UTF-8 encoding. Pen-drives use often VFAT, which is also Unicode
clean. 

It's not like a recent convert will get those broken-encoded files.

I think a 5-year transition period is more than enough. KDE 4 does not support
non-UTF-8 locales anyways.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.