Anyway, it’s a good read and is what I have been doing too. One historical note:
> Microsoft has often mistakenly used ‘Unicode’ and ‘widechar’ as synonyms for both ‘UCS-2’ and ‘UTF-16’.
While Microsoft’s continued defaulting to UTF-16 is misguided, and continued conflation of “Unicode” to mean “UTF-16” is very confusing for everyone who isn’t a Unicode expert, it didn’t start as a mistake. Now it’s a sustained mistake - mainly because of inertia + backward compatibility at this point. And there has been movement, but inertia is real.
At one point Windows had prototype UTF8 support as the ANSI codepage. Does anyone know where this went, or if it will be supported? The docs [1] indicate issues with GDI, which makes it sound still in prototype stage.
4 years ago|281 comments - https://news.ycombinator.com/item?id=22867503
8 years ago|153 comments - https://news.ycombinator.com/item?id=11933113
10 years ago|149 comments - https://news.ycombinator.com/item?id=7070944
12 years ago|2 comments - https://news.ycombinator.com/item?id=4695863
12 years ago|182 comments - https://news.ycombinator.com/item?id=3906253