Actually, there is code to either use ANSI or UNICODE API of windows, but either way, it will convert any string to CP1252.
Convertion from UTF-16 to CP1252 creates data loss as some characters can't be converted.
This leads to having some files unreachable.
Unicode support should always be set, and convertion should be made into UTF-8 to avoid getting conversion problems, and avoid to break all the API to manager UTF-16 variables everywhere.
Any string should then be exposed in UTF-8, and have eina to internally manage conversion to UTF-16 before using windows functions.
Actually, there is code to either use ANSI or UNICODE API of windows, but either way, it will convert any string to CP1252.
Convertion from UTF-16 to CP1252 creates data loss as some characters can't be converted. This leads to having some files unreachable.
Unicode support should always be set, and convertion should be made into UTF-8 to avoid getting conversion problems, and avoid to break all the API to manager UTF-16 variables everywhere.
Any string should then be exposed in UTF-8, and have eina to internally manage conversion to UTF-16 before using windows functions.