3 ms·
Windows uses potentially-ill-formed UTF-16. No language or environment that uses UTF-16 validates it, ever. Not a single one that I know of. But that doesn’t m
by chrismorgan 3y ago
Windows uses potentially-ill-formed UTF-16.
No language or environment that uses UTF-16 validates it, ever. Not a single one that I know of. But that doesn’t make it UCS-2, it just makes it potentially-ill-formed UTF-16.
- GoblinSlayer 3y agoWindows validates UTF-16 when ansi functions are called, they convert string arguments to UTF-16 and call unicode function, then convert results from UTF-16 to ansi.
- chrismorgan 3y agoThat’s nothing to do with validating UTF-16. What you’re describing is converting from code pages to UTF-16, which incidentally should produce well-formed UTF-16.
- hnfong 3y agoI just have the impression that they s/UCS-2/UTF-16/g without changing anything. Was that not the case? Genuinely curious whether there were UTF-16-specific changes made before they declared that Windows uses/supports UTF-16.