4 ms·
I bet that came down as strings coming from the filesystem, or user for that matter might be in a language that requires UTF16 to properly be used.
by jetbalsa 4y ago
I bet that came down as strings coming from the filesystem, or user for that matter might be in a language that requires UTF16 to properly be used.
- pjc50 4y agoIt came about because Microsoft deployed what they called "unicode" before UTF-8 was standardized. In Microsoft-land "Unicode" means UTF-16. This isn't great but it's also baked into all the APIs.
- account42 4y agoThey could always use WTF-8 for the filesystem APIs which can encode all WTF-16 strings (i.e. the encoding that Windows actually uses).