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

[Christopher Parker]

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


Christopher Parker cparker member fsf org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cparker at member.fsf.org




--- Comment #23 from Christopher Parker <cparker member fsf org>  2008-09-27 06:37:51 ---
I think the WONTFIX resolution is pretty ridiculous. It's taking functionality
away from a program and leaving an awfully broken mess behind.

I have a file server that I use to store all of my music that I access via SMB.
I use KAudioCreator to rip CDs to a local directory ($HOME/Music) and then I
move the music to the SMB share (ripping would take too long if I attempted to
rip directly to the share).

I recently ripped a CD with KAudioCreator from a Finnish band that has letters
with accents on them. I could access the files without a problem in the local
directory. I then moved the files to the SMB share, and had issues with moving
the files with accented characters in them (although the files appeared to have
been successfully moved, as they no longer appeared in the local source
directory).

Now, when I load the directory on the share that has these files in it, I'm
immediately told the files don't exist, even though they clearly do, as they're
showing up in the directory, although they show up as being 0B. I cannot rename
them (although for some reason I'm unable to rename anything on the share). I
cannot delete them. I cannot copy or move them back.

My question to you, Thiago, then, is: This is expected, normal behavior? I've
somehow supposedly had five years to change my file-naming ways, even though
another KDE application named the files to begin with? I think you need to
re-evaluate how you're looking at this show-stopping bug. I now have no way of
accessing these files, or other files that were pre-existing on the SMB shared
drive that were perfectly accessible before the upgrade to KDE4. I experience
this same issue when trying to access music from Björk, Green Jellÿ,
Queensrÿche, Rinôçérôse, and more, which were all ripped under KDE3. If
you're going to disable my access to my perfectly good files, you should at
least be failing a lot more gracefully than this and providing an option for
recovery while assuming I am an end user who doesn't know what a command line
is.


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