2 ms·
And the tragedy of early adoption! Microsoft looks antiquated for using UTF-16 today, but it was actually pretty cutting edge when it happened. They adopted a l
by jchw 7y ago
And the tragedy of early adoption! Microsoft looks antiquated for using UTF-16 today, but it was actually pretty cutting edge when it happened. They adopted a lot of tech pretty early too, like XML. All in all, pretty fascinating.
Windows 10 recently added the ability to use UTF-8 for the “ANSI” legacy codepage, which is awesome! I accomplished similar prior using API hooking but a Microsoft solution can simply do a much better job across the board. Now the only reason to set the encoding to anything else is to avoid mojibake when using non-English software. (Dear Japanese software developers: please consider using wide win32 APIs :( )