In HTML5, the browser is supposed to not sniff the document for a meta charset if the server headers specify a charset in the Content-type.
Google distributes Chrome on Linux on tens of millions of devices every year, it displays fonts just fine for almost everyone.
Chances are that it's not that weird. If you have enough memory I recommend building Chromium from source. There's probably some library somewhere which is behaving in a way which packaged Chrome isn't fond of (and it seems like maybe the maintainer of the chrome binary package you're using needs to update it in some way).
(Aside: funny enough, Chrome OS is Gentoo-based IIRC.)
When you say it's barely recognizable, do you mean simplified vs traditional? Because to me (as a native Chinese speaker) the Japanese and traditional look almost identical. I can't comment on traditional vs simplified because I can read both.
If it's simplified vs traditional, I wonder why OS/browser prefers to render the character in simplified form (I assume the Chinese font you are using has both styles).
They have different radicals on the lower right. Unless there's some reason to consider the two radicals equivalent (there isn't in JP, I wouldn't know about CN) they're different characters.
Maybe it's related to font you specified which may directly or indirectly (fallback) cause the problem. After all, `font-family` overrides language (which essentially just helps to get the right font(s)).
If you don't mind to provide a test page I can help debugging.
My Korean company website loads a subset of Noto Sans, but uses the system default sans-serif if it is accessed with a mobile device. Fortunately most Koreans don't use Hanja (Kanji/Hanzi) anymore, so visual consistency is not an issue.
The Web Speech API already exists for Speech Recognition and Speech Synthesis, so hopefully they add a translation API directly to Chrome. Can't call it an _inter_net if it doesn't easily support multiple languages!
Seems pretty straight forward to make a plugin that generates those URLs if you want one.
Their translator can also be accessed via API, but again not "allowed." It's not a huge issue since they don't do much other than try to 503 you, but it's still "illegal."
The feature still seems to be built into Chrome: https://random.spillett.net/stuff/tmp/translate.png
Or was there a plug-in for other browsers too, that is now AWOL?
This appears to be a reference to Google's universal Noto font set, released in 2014:
I recently had to build a large site that was English, Spanish, and Chinese. Which was fun considering that some of the audience was es-mx, some was es-es, and some were es-419.