Lol! The edit (“
letterletting”) was … <chef’s kiss>
[Where’s the button to heart an image?]
Thank you so much! You’re awesome!
This is the script, thank you so much!
This script really helps in cases where I draw a blank on the meaning and/or reading of a kanji when seeing it in isolation.
…It’s just a darn shame I can only use it on WK on desktop. This and the ConfusionGuesser scripts are ones I desperately wish I could use on mobile apps like Tsukurame, since I use a mobile app to do pretty much all of my reviews (if I waited until I got home from work to do my daily reviews, I’d be stuck with like over 100-200 reviews on some days, lol.)
What I like to do on the Flaming Durtles app is have the reviews reverse sorted by type, so all vocabulary come first. Then when I’m down to only kanji (and radicals), I can opt to switch over to desktop browser.
I don’t know if Tsukurame has sorting, or if you’d even want to use sorting if available, but it’s worth considering.
Just to confirm, is your browser using a Japanese font or a Chinese font by default?
I wonder if WaniKani is using a style to set the font for the kanji, and my added section doesn’t have any applied to it. I’ll give it a look later.
My windows 11 is in portuguese brazilian and I installed japanese language in case I want to type here something.
No chinese or any extra japanese fonts.
Wrap the vocab in
Thanks for pointing me right to the best (and proper) solution, rfindley!
I’ve updated the script now, so you can update it now from here:
If you’ve changed any configuration options at the top of the code, you’ll need to manually set them again after updating.
This script feels a bit like cheating and yet like absolutely the right thing to use I dread kanji-only reviews and always questioned a bit the benefit of reviewing basically just part of a word, so I appreciate you making this very much - thank you!
I have set to show only unlocked vocabulary, though, because I think for the first few reviews at least it’s better to focus on actual shape recognition but have long term retention work with context.
Possible feature requests (no clue how difficult those are to implement):
For this one, I’m not certain if there’s a way for the script itself to know if it’s an kun or on review. Maybe there is, as I don’t know too much about what information is available to scripts.
I’m not certain offhand about implementing hotkeys. I’d have to figure out how to be sure it’s not a hotkey used by something else at the very least. But I can add an option that blurs the text until you move the mouse over the vocabulary bar.
I don’t know the best way to know if it’s asking meaning or reading, but I’ve found a usable method to implement.
I’m unable to reproduce this. Do you know if you were on the latest version of the script at the time? (I figure you probably were.) The worst bugs are the ones I can’t reproduce to determine the source of the issue.
I’ve updated the userscript to version 0.4.0:
Disclaimer: As per usual, all options are stored directly in the code. If you’ve changed any options, you’ll have to set them again after updating.
Isn’t there already a userscript that gives you a hint when you got no idea? @ChristopherFritz Maybe a combination could be useful, where the vocab only show’s up, after you toggle it or something when you got no idea on your own.
EDIT: just read the update that you already did that. Maybe I should finish reading a thread before I reply. ^^’
Remembering kanji by vocabulary is something I’m doing quite often on my own, which is why the combination of kanji/vocab from WK works so well for me. But as @rfindley said, I’d also be worried for myself, that I’d start having trouble recognizing the kanji by themselves and therefore in any new kanji-combinations from vocab I don’t yet know.
There’s a script that turns the on’yomi into katakana, so there should be a way to recognize it (if it wasn’t all manually put into the file).
The new option to blur until mouse-over is in this direction, so there is that.
This is definitely an understandable concern.
For me, I’m not able to learn the kanji in isolation very well. But if it’s in words that I see when reading, it’s a lot easier for me. From there, I start to notice the same kanji used in other words.
Results will definitely vary between different types of learners.
I do recall seeing mention of that script. I’ll have to check it out sometime to see what they’re using.
At the very learn, I expect the API makes it clear what answers are valid, as well as which answers on on, kun, etc. So checking to see which list the expected answer is in may also be a viable implementation if there isn’t something better available.
just checked it: the outdated one was called “Katakana Madness”, the one that’s currently up to date is “Katakana for On’yomi”.
The current item in
$.jStorage.get('currentItem') has a
.emph propery. I’m not sure what its intended purpose is, but it seems to always say either kunyomi or onyomi for kanji
It’s the reading category that WK emphasizes for that kanji. So, any of the readings in the corresponding category (on, kun, or nanori) will be accepted in the kanji review.