@TimSweeneyEpic What are the chances of trying to move UE towards UTF-8 by default?Converting to UTF-16 at the platform layer when required.
-
-
Replying to @RileyLabrecque
I like the idea but am not sure it would be worth the conversion pain. In retrospect, UTF-16 was a terrible decision for the OS and apps!
2 replies 0 retweets 7 likes -
Replying to @TimSweeneyEpic @RileyLabrecque
I'd rather just go to UTF-32. UTF-8 is a pain to deal with any time you need to do string manipulation or searching.
2 replies 0 retweets 2 likes
Replying to @NickDarnell @RileyLabrecque
The problem with UTF-32 is that many of its elements, such as combining diacritics, aren't semantically independent of their neighbors.
7:31 AM - 23 Aug 2017
0 replies
0 retweets
1 like
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.