ExpandFileNameUTF8 broken
Original Reporter info from Mantis: Martin @martin_frb
-
Reporter name: Martin Friebe
Original Reporter info from Mantis: Martin @martin_frb
- Reporter name: Martin Friebe
Description:
The current implementation converts the filename using UTF8ToSys
This looses all chars in the filename that can not be encoded in the current sys encoding.
For example, I have an english w32. If a filename contains Russian chars, they are converted to "?"
Additional information:
This can be tested, trying to open a file via drag and drop. It fails if file or folder contain such chars.
There are many other functions with the same issue.