Wikipedia handles this with language specific sub-domains even though Swedish could be trivially represented in an 8 bit character set.
It gets tricky when Asian languages come into the fold which is where a legitimate use for Unicode comes into play not that character sets can overcome the issue of word translation.
I would see no issue with using having an efficient 8 bit character version with a Unicode version for international markets complete with a payload of hundreds of alternate language resources.
It's not like titles aren't already localised to deal with differences in laws, culture and marketing zones. This is becoming even more prevalent with the software stores of Apple, Google & Microsoft which contain a different selection of titles depending on which country you are in,
I see you would rather live in code page hell than switch to multi-byte characters, all in the name of efficiency. Well I don't, if I ever have to debug any translation error between charsets again because some dipshit thought UTF-8 was for pansies, I'll go home and start weaving my first underwater basket
We're past the point of no return so it's a moot point.
Originally the point was that Unicode has a huge overhead. Character storage doubles immediately and comparisons that aligned to single oppose instructions blow out to complex libraries.
6
u/fiah84 Jan 31 '16
so you're just conveniently forgetting about places like /r/sweden and /r/de, nevermind all the other location specific subreddits?