[Bug 204768] Dolphin-Konqueror plugin to solve encoding problems marked as WONTFIX

[Diego Calleja Garcia]

https://bugs.kde.org/show_bug.cgi?id=204768


Diego Calleja Garcia <diegocg at teleline.es> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |diegocg at teleline.es




--- Comment #4 from Diego Calleja Garcia <diegocg teleline es>  2009-09-19 15:55:59 ---
It's certainly possible to handle broken encodings well if paths are handled as
what they really are (streams of bytes separated by the '/' character), just
like many command line tools do. Which is why cp -av will never miss a file and
will always print the name (and will print the byte string if the encoding is
broken), no matter how broken the encoding is, dolphin on the other side can't
copy some of my files because it can't see them. Now, if QT can't do anything
else, there's not a lot we can do. Files with broken encodings exist (I just
got a few GB of them from an XP box, and amarok can't see most of them). But
more importantly, files with broken encodings will _continue_ existing forever,
its selfish to think the contrary. So KDE is condemned to have unhappy people
hitting this bug. Sight.

IMO the worst thing about the current behaviour are the wrong messages -
instead of telling you that the encoding is wrong, dolphin will tell you it
can't find file, even if you are seeing the file in the window (with a name
with weird characters, but hey, it's clear it _is_ there, i'm seeing the icon).
it confuses users. Maybe it could be possible to try to use the native unix
apis when you find such error (as thiago suggest here
http://lists.kde.org/?l=kde-core-devel&m=122025063320264&w=2) to implement a
simplistic "renamer". It is not portable, but ...

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