3 ms·

UTF-8 Everywhere

12 points by throw0101d 2y ago

deleted 2y ago
[deleted]
mcfig 2y ago
I see this was [posted 12 years ago](https://news.ycombinator.com/item?id=3906253 https://news.ycombinator.com/item?id=3906253) too! 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.
vintagedave 2y ago
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. https://utf8everywhere.org/#windows https://utf8everywhere.org/#windows may be outdated if that goes ahead. [1] https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page https://learn.microsoft.com/en-us/windows/apps/design/global...
belter 2y ago
4 years ago|147 comments - https://news.ycombinator.com/item?id=25124988 https://news.ycombinator.com/item?id=25124988 4 years ago|281 comments - https://news.ycombinator.com/item?id=22867503 https://news.ycombinator.com/item?id=22867503 8 years ago|153 comments - https://news.ycombinator.com/item?id=11933113 https://news.ycombinator.com/item?id=11933113 10 years ago|149 comments - https://news.ycombinator.com/item?id=7070944 https://news.ycombinator.com/item?id=7070944 12 years ago|2 comments - https://news.ycombinator.com/item?id=4695863 https://news.ycombinator.com/item?id=4695863 12 years ago|182 comments - https://news.ycombinator.com/item?id=3906253 https://news.ycombinator.com/item?id=3906253
frank_bb 2y ago
[dead]

12 points by throw0101d 2y ago

deleted 2y ago

[deleted]

I see this was [posted 12 years ago](https://news.ycombinator.com/item?id=3906253 https://news.ycombinator.com/item?id=3906253) too! 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.

vintagedave 2y ago

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. https://utf8everywhere.org/#windows https://utf8everywhere.org/#windows may be outdated if that goes ahead. [1] https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page https://learn.microsoft.com/en-us/windows/apps/design/global...

belter 2y ago

4 years ago|147 comments - https://news.ycombinator.com/item?id=25124988 https://news.ycombinator.com/item?id=25124988 4 years ago|281 comments - https://news.ycombinator.com/item?id=22867503 https://news.ycombinator.com/item?id=22867503 8 years ago|153 comments - https://news.ycombinator.com/item?id=11933113 https://news.ycombinator.com/item?id=11933113 10 years ago|149 comments - https://news.ycombinator.com/item?id=7070944 https://news.ycombinator.com/item?id=7070944 12 years ago|2 comments - https://news.ycombinator.com/item?id=4695863 https://news.ycombinator.com/item?id=4695863 12 years ago|182 comments - https://news.ycombinator.com/item?id=3906253 https://news.ycombinator.com/item?id=3906253

frank_bb 2y ago

[dead]