This is a third-party script/app and is not created by the WaniKani team. By using this, you understand that it can stop working at any time or be discontinued indefinitely.
Overview This script transforms everything in reviews and lessons related to kanji onyomi readings into カタカナ.You may find this helpful as this is the dictionary standard, and is also a great opportunity to become more familiar with these characters.
Known Issues:
The input shakes when inputting on’yomi readings if the final letter is N. Shaking can be avoided by typing NN. I don’t think I can fix this, so I am declaring it a feature to encourage you to type NN in preparation of less lenient IMEs.
** Known incompatible scripts **
Wanikani Anki Mode (onyomi will not display as katakana while in anki mode)
It’d be nice to have an option to switch everything over to katakana. I presume it’s trivial to do in the code, so I’m going to try and tweak it for myself.
Depends on what you mean by everything. Making the current replacements work for all items should be pretty trivial (delete some if statements), replacing additional content is more annoying.
Seems to be working perfectly in Recently learned extra study, I don’t plan on making a kanji mistake just to test that out though, so I’ll let you know if I ever do.
It seems I cant write ン during lessons. It always enters N and readings cant get validate.
Is this a specific known issue of Katana for onyomi ? or I do I have to much userscripts etc ?
Hey, I’m having an issue that I think might be with the script, but I’m not 100% certain. I can reproduce it with most of my other scripts off, but I do have Reorder Omega enabled because it would be terrible to test this without it, given the stack of 700 reviews I’m still whittling down (From 1500, halfway there, woo). I do see that you have Script Compatibility mode as required, and I do have that enabled at least.
At least during reviews, the reading mnemonic section seems to have its formatting stripped away on items with an on’yomi reading that are converted.
I tried to fix this, and think I found something, I’m testing currently and will release it on tampermonkey if I don’t see any issues.
If you want to test it yourself before then, you can edit the script by changing the line that contains
var reviewItemInfoDropDownReadingLocator
to be
var reviewItemInfoDropDownReadingLocator =‘#item-info-reading-mnemonic span:lang(ja)’;
Just tried it out on my machine, and looks to be working fine now. Hope your testing goes just as well.
As a side note, being out of kanji reviews for another hour and only having vocabulary to test it on… I don’t think I’ve thought about how many words are just “If you know the readings of your kanji you’ll know how to read this as well” until having to go look for one that isn’t. At least there’s the header and hint section of that block being fixed to sanity check that I didn’t somehow mess something up putting that in until I hit one.
Thanks for this! I like being able to know what reading I’m using, and Katakana helps. However, it seems this script breaks the WaniKani Pitch Info userscript. It may be that the Pitch Info userscript will need updating to support Katakana being present
I tried changing the UserScript order in Tampermonkey, but that did not work
Hmm, that is strange. This script should only impact kanji, and I assume pitch info is only valid for vocab? It’s certainly possible they interfere anyway, but it is odd.