View Single Post
Old 01-15-2017, 09:42 AM   #61
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by slowsmile View Post
@Kevin & @DiapDealer.
I found out that the Windows NTFS file system(used on Windows 7, 8 & 10) uses UTF16 for all file names.
See Doitsus test case. It works properly.

No worries about utf-8 vs utf-16, as both encodings can encode every codepoint in the full unicode. That is simply not true of any of the single byte encodings.

So somehow you are reading or writing filenames/paths as latin 1 encodings.

I will take a look a look at it.

KevinH
KevinH is offline   Reply With Quote