So, after testing, there’s one script I have that completely disables this one, it’s called “Advance Context Sentence 2”. I’ve disabled it and it works perfectly.
This is now fixed in version 2.24 of Advanced Context Sentence 2 (the problem was a bugged version of the Custom Icons library script). I also went ahead and updated Keisei and Niai to the newest version of the Custom Icons library script so that all scripts use the same version.
Hello! Thank you for a great extension, I’ve been using it quite a lot!
I’ve noticed that some kanji created using semantic-phonetic composition in fact don’t contain 音符 in its original form. For example, 払 is said to use 弗 as its phonetic component. It’s likely due to historical evolution and simplification.
So I wonder, if there is any extension that shows the original form of kanji?
I finished WaniKani a while ago so I can’t be bothered to hack scripts anymore, but I suppose it wouldn’t be too difficult for a motivated individual to take the data from this spreadsheet and integrate it into the script.
Note that I compiled the data using Wiktionary so it may differ a bit from this keisei script in some corners (I actually believe that my data is more complete, although the difference is probably insignificant).
I just installed this as my first user script, it looks very helpful!
One question though: What do the colored circles in the top left of the kanji mean? There are 天 and 下 circles in red, yellow, and green, as far as I’ve seen, but I can’t find an explanation on them.
This script checks if the readings from a kanji are based of the readings from one of its compounds. Compounds are also kanji, and as you probably know by now kanji can have multiple readings.
If all readings from a kanji are derived from any one of the readings from the compound, it is considered a perfect match. In the example above the compound has both てき and しゃく as reading. This means that kanji with either the てき or しゃく reading, as well as kanji with both readings, are considered a perfect match.
For me this means that the phonetic-composition is only really useful for compounds with just one reading. The non-perfect matches are usually even less usefull.
Using this on Firefox and doesn’t seem to be working as of right now. Does anyone know why? It says it is active according to tampermonkey but the actual section isn’t coming up.
Script does not work on Firefox, because it seems that jQuery is not injected by Firefox into script context (at least according to ChatGPT ).
I get the following error when script loads:
Uncaught (in promise) ReferenceError: $ is not defined
createKeiseiSection WaniKani-Keisei-Phonetic-Semantic-Composition.user.js:2158
injectKeiseiSection WaniKani-Keisei-Phonetic-Semantic-Composition.user.js:2794