Would love to see Windows support codepage 65001 (UTF-8). Then all existing Windows 8-bit character APIs would magically support UTF-8, instead of this horrible old UTF-16 encoding.
-
-
Replying to @TimSweeneyEpic
Those should be separate APIs anyway. Clients of existing 8-bit APIs expect 1-byte chars.
1 reply 0 retweets 0 likes
Replying to @storm4d
I’m good with that! I’ll be happy with OpenFileU, etc.
11:26 PM - 9 Apr 2018
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.