It seems that the fonts 'Sazanami Gothic','さざなみゴシック' and Sazanami Mincho','さざなみ明朝' have the wrong graph at
U+7e6b (繫) which should have thread 糸 at the bottom, not hand 手.
Screenshot of a font test of 繫:
A more recent version of the font may have been fixed, I'll try it later. Accessing the (possible) webpage of the developer failed:
This page is a reminder, I'll come back to it later.
In Japanese I know 曖 from the word aimai 曖昧. When I look 曖 up in jdict, I only get compounds with this same word, often written in kana, like for example aimai seigyo あいまい制御 (apparently a computer term for “fuzzy control”).¹
Out of context, I mistook 曖 for 暖 (the graph used in for example atatakai 暖かい “warm” or danbou 暖房 “indoor heating”). After my mistake I looked up 曖 in wiktionary, and noticed to my surprise that the PRC has simplified 曖 to 暧. That looks even more like 暖!
And yet both 暖 and 暧 are being used in Chinese. For example, there is “vague; ambiguous” àimèi, written as 暧昧, and “warm (up)” nuǎnhuo 暖和. That must be hard.
I looked up 暧昧 and 暖和 in LINE Dict, which gives example sentences. Under 暧的 it lists these examples:
In the first example sentence it has the word nuǎnhuo 暖和, which I cited as an example word for 暖. Here however, it is incorrectly spelled with 暧. (The transcription is automatic, and therefore also incorrect.) The other two example sentences contain similar errors. Just a few minutes after I thought, gee, why would they simplify a graph in such a way to make it almost identical to that other graph, I already find confusions between the two.
Truthfully, I can hardly believe this.
- To write the Japanese word aimai 曖昧, you have to learn two graphs that are not used in any other word (strictly, 昧 occurs in a few Buddhist names). Aimai shares this dubious feature with aisatsu 挨拶 “greetings”. It comes as no surprise to see it spelled in kana.
In a book for children:
Fuyu no daigomi to ieba..
My brain knows 大好き daisuki (very much like [something]) and 大嫌い daikirai (very much dislike or hate [something]) so, by analogy - considering that gomi is ‘‘garbage; rubbish; trash’’ - daigomi should be something like ‘‘very much consider garbage [something]’’?
Want to know what I think is really garbage in winter?
Wrong of course. Firstly, gomi does not fit the pattern of suki (something [I] like, from the verb suku) and kirai (something [I] dislike, from the verb kirau). Gomi does not derrive from a verb
gomu, it’s simply means trash. Secondly, daigomi turns out to be a completely independent word:
1. [n] the real pleasure (of something); the real thrill; the true charm
2. flavour of ghee; delicious taste
3. [Buddh] Buddha's gracious teachings
And BTW, gomi is also:
1. [n] five flavors (sweet, salty, spicy, sour, bitter); five palates; five tastes
2. [Buddh] five flavors (milk at various stages of making ghee: fresh milk, cream, curdled milk, butter, and ghee); the five periods of the Buddha's teachings
Fuyu no daigomi to ieba...
Takibi de yakiimo yo ne! Oishii ne.
Want to know the true pleasure about winter?
Roasting sweet potatoes on an open fire! Man, that is delicious.
Leonardo F.S. Boiko’s post Jōyō kanji variants: The curious case of 叱 and 𠮟 is among other things an interesting discussion of the acknowledgement of variants of characters in the 常用漢字表). It also pointed me to a project he is working on:
Might be useful for dealing both with the latest 常用漢字 and their variants. The output folder contains lists that his script generates (from the official 常用漢字表 that is in PDF).
However, the post also explained that Unicode has embraced a method to hard code local variants of characters that have been unified earlier (that for a long time to come won’t be supported by any software no doubt). It’s amazing that after so many years Unicode gets a kind of after the fact fix for the controversial choices made in the unification. I’m not sure what to think about it.
Currently search engines seem to unify even not-unified characters like 圧/壓. Example for Google using 外壓:
If I want to search for 外壓 only, excluding 外圧, I have to choose a language in the advanced search options page. Which is a workable solution.
Currently I’ve ‘unified’ the characters with separate code points for old words in entries of 日蘭辭典, just like Google, but not for modern entries. (I did use a universal solution earlier, but it was a bit slow, so I removed the code. I lack real programming skills.)
Will I update www.jiten.nl, when the new options come available? Maybe, if I’m still around then, and really bored.