12 Jun
2017
12 Jun
'17
12:11 p.m.
Artyom Beilis wrote:
Converting invalid UTF-16 to WTF-8 and other way around is not obvious behavior and has potential of security risk especially for users that are not aware of such an issue. So invalid UTF-8/16 sequences are rejected by design.
Implying that there are Windows file names that can't be handled by the library?