Love that bit where MS says the future of UI is HTML5 + JS (a bit early to tell, but sure)... and UTF-16.
@rygorous When MS originally adopted it, it was fixed 16 bits per character, IIRC. I assume the eventual standard has added escape codes?
-
-
@rygorous (I have never used UTF-16, since I'm not sure what the point of it would be). -
@cmuratori@rygorous Yep, UCS-2 was old thing, then Unicode folks actually reserved enough code points in UCS-2 range to make UTF-16 to work
End of conversation
New conversation -
-
-
@cmuratori MS initially adopted UCS-2 (before there were UTFs). Since Win2k, it's UTF-16, which adds surrogate pairs. http://msdn.microsoft.com/en-us/library/windows/desktop/dd374069(v=vs.85).aspx … -
@rygorous I feel like what we really need is UTF-64, because once we make contact with the aliens, we're going to need a lot of new glyphs. - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.