Bug 167823 - usb flash drive mounts with wrong encoding
Summary: usb flash drive mounts with wrong encoding
Status: RESOLVED DUPLICATE of bug 165400
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-31 10:33 UTC by Alexey
Modified: 2008-10-12 02:51 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey 2008-07-31 10:33:22 UTC
Version:            (using KDE 4.1.0)
Installed from:    Unlisted Binary Package
OS:                Linux

I'm from Russia. I sometimes use Windows operating system. When I plug usb flash drive which was written in Windows with cyrillyc characters in filenames or names of directories I see "?????" instead the real filenames or names of directories. The system locale is UTF-8. This problem appeared when my system upgraded to KDE 4.1 from KDE 3.5.9
Comment 1 Rubens de Souza Matos Júnior 2008-08-11 15:58:28 UTC
I have the same problem. When I mount it with pmount, using konqueror, the charset is ok, but when i mount it on gui (dolphin or "recently plugged devices" plasmoid) the charset isn't correct, with ??? instead of accents, like á, ã ...
The problem appeared after the update to kde 4.1 .
Comment 2 Alexei 2008-08-26 18:19:56 UTC
I've the same problem on Kubuntu 8.10.1 & openSUSE 11.0
Comment 3 Rubens de Souza Matos Júnior 2008-09-18 06:30:41 UTC
(In reply to comment #1)
> I have the same problem. When I mount it with pmount, using konqueror, the
> charset is ok, but when i mount it on gui (dolphin or "recently plugged
> devices" plasmoid) the charset isn't correct, with ??? instead of accents, like
> á, ã ...
> The problem appeared after the update to kde 4.1 .
> 

The problem seems to be solved since kde 4.1.1
Comment 4 Dotan Cohen 2008-10-12 02:51:22 UTC

*** This bug has been marked as a duplicate of bug 165400 ***