Oh, right. Either UCS-2 or potentially-invalid UTF-16, depending on how you describe it.
-
-
The fun part is that countries like Japan widely adopted a mutibyte encoding long before utf8 was invented, and have stuck with them.
4 replies 0 retweets 0 likes -
Japan is pretty much the only partial holdout, and decreasingly so. Shift_JIS presence on the web dropped by ~50% between 2014 and 2018.
1 reply 0 retweets 0 likes -
Because of the great firewall of china, you mean?
3 replies 0 retweets 0 likes -
-
Replying to @dev_console @RichFelker and
perhaps http://xahlee.info/w/what_encoding_do_chinese_websites_use.html … is out of date and nobody has legacy data.
1 reply 0 retweets 0 likes -
Replying to @landley @RichFelker and
I just checked all sites there, and all have them except qq and 163 have converted to UTF-8. :)
1 reply 0 retweets 0 likes -
Replying to @dev_console @landley and
curiously, 163 seems to have reverted to GBK since that list was made...
2 replies 0 retweets 0 likes -
Replying to @dev_console @RichFelker and
I'd be more comfortable if the call for utf-8 was coming from the people affected...
1 reply 0 retweets 0 likes -
Replying to @landley @dev_console and
It's not a "call". You're arguing about something that was over/decided nearly a decade ago. We're just describing what happened.
1 reply 0 retweets 0 likes
FWIW the popular Japanese encodings, ISO-2022 and Shift_JIS, were *never* options on real-world unices because they're incompatible with filesystem, format strings, etc. EUC-JP was, but anyone using it was already incompatible with the majority Windows-world..
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.