I'm considering requiring file names to be UTF-8 on Sortix. Traditionally Unix allows any byte sequence (except '\0' and '/') in an unspecified encoding. This just creates problems. File names you can't type. Programming languages with UTF-16 strings can't access them.
Japan is pretty much the only partial holdout, and decreasingly so. Shift_JIS presence on the web dropped by ~50% between 2014 and 2018.
-
-
Because of the great firewall of china, you mean?
-
what
-
perhaps http://xahlee.info/w/what_encoding_do_chinese_websites_use.html … is out of date and nobody has legacy data.
-
I just checked all sites there, and all have them except qq and 163 have converted to UTF-8. :)
-
curiously, 163 seems to have reverted to GBK since that list was made...
-
I'd be more comfortable if the call for utf-8 was coming from the people affected...
-
It's not a "call". You're arguing about something that was over/decided nearly a decade ago. We're just describing what happened.
-
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..
End of conversation
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.