I’ve noticed it before with 直 too on Chrome, but didn’t know enough to know what was going on. I assumed it might be just a font difference.
It sounds like only occasional unicode characters have this setting matter with them:
Japanese users prefer to see Japanese text written with “Japanese” glyphs.
There are occasional instances of unified characters whose typical Chinese glyph and typical Japanese glyph are distinct enough that the Chinese glyph will be unfamiliar to the typical Japanese reader, e.g., 直 U+76F4. To prevent legibility problems for Japanese readers, it is advisable to use a Japanese-style font when presenting Unihan text to Japanese readers.
I’m guessing there is at least some device setting involvement, because on my work computer, using Chrome, everything always showed Japanese characters, and I haven’t done anything to edit anything.
But I’m in Japan, so presumably there is some setting on the device overriding it.
For optimal results a system localized for use in Japan, for example, should use a font designed explicitly for use with Japanese, rather than a generic Unihan font.
(from the same page)
This was pretty interesting!
The key is it sounds like it’s unicode’s fallback in a way - some characters look odd for all possible languages (I’d imagine those expecting simplified Chinese characters would notice instantly, for example).
Since the language is unset, it’s not Chinese or Japanese, it’s just… unicode.
I had a phone that used to show Chinese versions for any Japanese if I had my default language as English. My current phone doesn’t have the same issue.
But any time I had my phone set to English I couldn’t stand the Japanese showing Chinese versions, but maybe that’s just my low tolerance.
It does also sound like the initial feedback is valid since it’s a Japanese language learning forum and all.
It should probably have the characters set to Japanese by default, to avoid ignorant folks like me with non-Japanese setups from making the same (minor) mistake of not noticing.
Seems like you can change them with tags if other forms are specifically needed for some reason.
(assuming that applies to potential site-level fixes and all that anyway)
Couldn’t get mine into English, but it does like Spanish now. It’s a redirection problem so if you use the language options at the bottom or a direct URL like minecraft.net/en-us it works. I imagine this sort of solution should work in the vast majority of cases.
EDIT: After using the en-us page, my browser seems to remember that preference and redirects there from minecraft.net on it’s own now. So that’s good.
I have never used minecraft.net, but yes, you are right. With my settings, minecraft is Japanese. I don’t know why … (good for your immersion to Japanese? )
I have now added German and French in the order EN (US), DE, FR, EN (GB), JP and now minecraft has turned from Japanese to German. Do they ignore English?
Why not? They are there for your personal preferences. The Unicode coding for 直 is the same for the Chinese or Japanese character, so there is only the local preference to select between them (if the website doesn’t provide the information that it prefers the Japanese variant).
Because I don’t have to change anything for deepl, google translate or wiktionary and countless other sites.
Also considering that it’s users who pay WK and not the other way around, IMO it’s naturally to expect WK to do the work so their site display Japanese correctly, not the users.
(I also don’t like when sites display Japanese without me explicitly asking them)
That’s neat I guess… 空 空 (I used the same character here, or tried to anyway)
)