@mrthf those are very different things. the grave and the acute are different abstract characters; "à" in my language means something different than "á". the two "bone" variants are a matter of font styles, they are graphical design traits rather than linguistic information; in the same way that in my country we write "7" with a horizontal stroke crossing it but in the USA they don't, but it's still a "seven". recall that the Han unification was planed, decided and designed by native scholars from East Asia, not by foreign speakers. and the intended solution is technically correct: if your system is picking Chinese font glyphs when you set it to a Japanese locale that's a bug with your system, not a problem with Unicode.
however due to practical concessions, a mechanism was eventually provided to select specific visual variants of the same character in plain text anyway (the Variation Selector characters for Ideographic Variation Sequences, U+E0100 to U+E011F, aka "VS17" to "VS48"). the best solution to this problem if you need to display multiple-language character variants is still to use rich text, for example in HTML
…the Japanese version is <span lang=ja>骨</span> and the Chinese version is <span lang=zh>骨</span>…<br>
should display the specific glyphs, or else you can tag them to specific fonts, etc. but if for any reason you want to do that at plain text level anyway, you can follow the abstract codepoint with selectors, provided by the IVD on IVD_Sequences.txt. so one can do 骨󠄀, 骨󠄁, and also the historical forms 骨󠄂 and 骨󠄃. these will probably not display the visually variant glyphs in your system but they're
encoded for specific variants, cross-platform and stably, and will show as such on any system with the adequate fonts.
#Unicode #Chinese #Japanese
