|
It only happens with very few specific national characters with specific Windows languages/regional setting. No, I can't duplicate this, it seems to be limited to some specific languages or something.. (I use english Windows)
Reason: for some weird reason "ansi" (iso-8859-1 and other non-unicode charsets) to unicode conversion converts some national characters to "plain" version. (or perhaps it was unicode to "ansi", don't remember), for example ñ becomes n. (even if destination charset does support both..)
(btw, Windows internally uses UTF-16)
This was originally reported by AmiKit author but as usual, I "can't" fix anything unless I can duplicate it myself..
Does anything change if you add "win32.filesystem_codepage=0" to configuration file?
|