5

Good day, I've just noticed that the kanji 誤, while displayed almost everywhere that way, when pasted in my Anki deck, suddenly changes into (see picture below)enter image description here

I can't get it to display anywhere else like that, when displayed on the card itself during review it's also displayed like 誤. And the sites which recognize kanji by writing strokes don't seem to know the second writing. Can someone shed some light why Windows IME decides to insert a different writing for this particular case.

3
  • 1
    Some Simplified Chinese fonts (e.g. Heiti SC) render it that way. It's like a cross of Japanese (誤) and Simplified (误). Traditional fonts render it differently from both. – aguijonazo May 2 at 10:51
  • Try 直 and see how it goes. – aguijonazo May 2 at 10:56
  • 1
    FYI, as you've already discovered, this is due to default font locale issues. In case you haven't figured it out yet, though, you can usually fix this in an Anki deck by adding the lang="ja" attribute to an enclosing HTML tag in the card template (for example, <span lang="ja">{{kanji}}</span>). In my deck, I just added that attribute to the top-most enclosing tag (a div that contains the entire card contents), so it applies to all text on the card. – Foogod May 5 at 1:27
10

The cause is most likely that your font setting (of a program or OS) have gone wrong. As far as I can see the said character in the input box looks rendered with a Chinese font.

The glyph you see and the intended Japanese one share the same meaning and the same code point in Unicode (Han unification). Thus computers cannot tell which is which binary-wise, and it is a font's responsibility to render it correctly according to the locale. Wiktionary usually provides useful information regarding regional variants.

enter image description here

Of course, it does not mean that those shapes are interchangeable, and you will be deemed miswritten if you write it in the first form in Japan. You will have to change the font somehow, but how to actually fix it can be only explained on a case-by-case basis (and I'm not sure it's in the scope of this site).

PS
The effect of Han unification is not always logically consistent, as it had to deal with backward compatibility with existing standards in each country. For example, the right side component alone 呉 is separately encoded for all China, Taiwan/Korea, and Japan standard variations, so you wouldn't be caught in the same situation simply by font corruption.

enter image description here enter image description here enter image description here

1
  • 3
    Yes, in hindsight, should have bee more obvious the problem was with the font. For anyone wondering, the font in the fields through "MS Shell Dlg2" was chosen as "Tahoma". Since the system locale was not Japanese, the program didn't know what version of Tahoma to use, and defaulted to the Chinese one. Here is the answer in detail to this problem superuser.com/questions/1269319/…. Your answer helped in either case, thank you. – Narrava May 2 at 12:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.