Bug 397119

Summary: Should be able to show non-printable characters in filenames
Product: [Applications] dolphin Reporter: Jaime Torres <jtamate>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: elvis.angelaccio, mail
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jaime Torres 2018-08-03 08:52:07 UTC
The same as kate has an option to show Non-printable spaces, dolphin should have it too.
It is quite weird to see 1.txt sorted after 9.txt, just because 1.txt in fact has two unicode characters, one of them invisible, in hexadecimal: 80 8B 31 2E 74 78 74 (​1.txt)

You can get that character, for example, from TestFile.txt from https://github.com/DavidJacobson/SafeText
Comment 1 Julian Steinmann 2018-08-03 16:42:47 UTC
Hello and thanks for reporting this bug/wish. If I simply download the raw file mentioned, I do not get any invisible chars at all (everything sorts perfectly fine). Do I need to clone the full repository, or do I need to copy a specific character from this TestFile.txt?
Comment 2 Jaime Torres 2018-08-03 16:49:12 UTC
You need to copy a specific character from that file: in the second line, that vim shows in this way: Lorem<200b>Ipsum<200b>Dolor<200b>Sit

In my first comment, and in this one, the last ​1.txt also has that character.
Comment 3 Christoph Feck 2018-08-04 06:03:13 UTC
> 80 8B 31 2E 74 78 74

Are these Unicode code points or raw bytes? If they are bytes, the filename is not UTF-8 encoded.
Comment 4 Jaime Torres 2018-08-04 07:14:20 UTC
Raw bytes as seen by okteta.
I haven't figured out how to get the unicode code points.
Comment 5 Christoph Feck 2018-08-04 09:39:41 UTC

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