https://bugs.kde.org/show_bug.cgi?id=165044
Nathan Shearer <kde-20091...@nathanshearer.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kde-20091112@nathanshearer.
                   |                            |ca

--- Comment #166 from Nathan Shearer <kde-20091...@nathanshearer.ca> ---
I just extracted an archive which contained a file that I could not
copy/edit/move/rename/delete with dolphin. The file was simple readme file
inside a nested subdirectory called L'$'\351''ame.html'

The error messages in dolphin were extremely vague and did not indicate in an
way that KDE and QT are incapable by design of handling files with these
encoding. They did not inform the user why the file was causing these problems
or even hint that they needed to be renamed in a terminal because of a WONTFIX
on this bug.

The only reason I knew what to do is because I encountered this bug years ago
when operations on these files actually worked. Any normal user will have
absolutely no idea what to do, and higher level systems will not handle these
failures gracefully when these directory structures can't be modified because
of a simple filename.

The file or folder L'$'\351''ame.html' does not exist.
 - This is _false_ it does exist!
Could not delete file L'$'\351''ame.html'.
 - No reason provided whatsoever. The user will not know how to solve this
problem.
Could not remove folder "".
 - All other files deleted, but the nested file was ignored leaving the user
confused.

This is ridiculous.

It might be a lot of work, but a solution to this problem would be to store
these strings as a tuple, where there is a degraded and user-friendly version
of the string and the original unmodified string. If no changes are made to the
string, use the original unmodified string. If the user decides to change the
string, then they are interacting with the degraded version and deciding to
keep that new string.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to