utf8 filenames / QDir::entryList

[sedi]

Are you sure with Latin1 "U+00FC" ? For me it seems like Ã+00BC, with à being sort of an escape character.

I've looked up the codes in this Utf8 table here. With that information I can just string-replace all Umlauts and other important chars. But for my case, it actually works as expected.

This said, it's probably quite slow to tackle the problem this way, it seems like reassembling the debris instead of preventing the accident.


Many thanks for the idea to actually look into the bytes myself - sometimes I don't see the wood for the trees. If anyone has a better idea (in terms of performance or safety of use), I'd be very happy to improve or entirely change my approach, but for the moment I can use that.

[ChrisW67]

U+00FC is a Unicode code point for the character 'ü'. When encoded in UTF-8 that single Unicode character becomes 2 bytes 0xC3 0xBC.

If you interpret those two bytes as Latin1 characters (which are always one byte-one char) you get, as you point out, Ã and ¼.

So, the file name is encoded in UTF8 on the device. It is read as a set of bytes that are then incorrectly treated as a Latin1 string.