Bug 349996

Summary:	Dolphin doesn't display unicode characters correctly
Product:	[Applications] dolphin	Reporter:	Victor Tran <vicr12345>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	File with unicode filename.

Description Victor Tran 2015-07-07 11:22:38 UTC

In a filename, Dolphin doesn't show unicode characters. I was transferring a file from a mac called Pokémon, and Dolphin displays it as PokÃ©mon.

NOTE: This also happens in the Terminal, so it may be a system-wide problem.

Reproducible: Always

Steps to Reproduce:
1. Get a file with a unicode character in it
2. Open Dolphin and change directory to it

Actual Results:  
The unicode character shows up in a fully way

Expected Results:  
The unicode character shows up properly

If you try to delete the file, Dolphin throws an error saying that the file does not exist.

Comment 1 Victor Tran 2015-07-07 11:26:36 UTC

Created attachment 93513 [details]
File with unicode filename.

This file has a unicode filename, and the data inside was generated from /dev/urandom. Try this file with Dolphin and hopefully you will see what I mean. In contrast, cd to the directory you downloaded this file to in uxterm and ls.

Comment 2 Victor Tran 2015-07-07 11:28:28 UTC

Actually, turns out that the KDE bugtracker changed the name to download :/

Comment 3 Frank Reininghaus 2015-07-07 18:48:55 UTC

Thanks for the bug report. Are you sure that the characters in the file name are all Unicode characters? Actually, it should work fine with Unicode, but it is known that Qt cannot handle file names with non-Unicode characters, see bug 165044.

(In reply to Victor Tran from comment #0)
> If you try to delete the file, Dolphin throws an error saying that the file
> does not exist.

This really sounds pretty much like bug 165044.

Comment 4 Victor Tran 2015-07-09 09:03:51 UTC

OK, in that case, I think that this bug can be marked as a duplicate of #165044.

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