While the original show context sentence script was pretty awesome, I wanted something that didn’t inline the sentence with the review item. This script slots a single sentence into the space just above the kanji/vocabulary question header.
Over on GreasyFork: Show Context Sentence
Thanks! I’m giving your script a try! ^>^
Good script!
Congratulations on your script. Very useful.
Just one thing, where do you get that context sentence from? Is it from the wanikani sentences or somewhere else?
It’s from the WK sentences that you see in the lessons, or if you expand the subject material on the reviews page. There are three sentences for each vocab item. It just pulls the first because, from my experience that seems to consistently be the easiest of the three.
Great! I wanted to use the context sentences more anyway.
Also the style is quite beautiful.
I’ll definitely give it a try! Thanks
~T 
This seems really cool!
Do those who have gotten a lot of use out of this and similar scripts feel like it could make things too easy? What I mean is, when I’m reading normally it’s much easier for me to understand the meaning of a word using context. So I’m wondering if relying too much on context will hurt my recall of the word. Is that a thing?
Too easy? Hahahaha, he said, “Too easy”! 
My experience is, no, this is still one of the most difficult things I’ve ever attempted.
But ultimately my goal is to be able to read. My perception is that reading a vocabulary word in context is more useful to that end goal than recognizing it out of context. I mean, if you are working through みんあの日本語 you’ll almost never see a kanji vocabulary word out of context except for it’s initial introduction and definition. So I consider this a legitimate learning tool. Of course I respect that everyone’s process may differ.
It’s also helping to solidify grammar, so I consider it a win/win.
Thank you! That makes sense.
As a followup, if you think about how a native Japanese school child learns kanji, they are mapping readings to vocabulary they already know. This seems to me to be quite a bit easier than what the average WK user is attempting to do. The context sentence helps a bit with meanings, while still forcing you to know the translation, but does nothing to help with readings. One still has to remember if it’s にん or じん or rendaku or not, or a kunyomi exception or one of a dozen other things I find so challenging about this whole process.
Yeah definitely!
I started Wanikani at N3 level, took a 2 year break, then came back after getting to N1, and now there are a fair amount of words I’m familiar with but don’t know the kanji for. Those ones are a lot easier, for sure, my worry was that in a context sentence I would be able to recognize one of those words in a sentence without actually reading the kanji, which felt like cheating.
After using the script it doesn’t feel gratuitous at all though. Reading the context sentence has given me the answer several times I probably would have gotten it wrong otherwise, but that’s pretty rare, and like you said it feels legitimate because it’s a realistic way of figuring out the word, as in reading. And it’s not like the kanji becomes invisible when you figure it out from context anyway.
Thanks!
It works great with vocab
This is great, I came looking for scripts that would make the example sentences more accessible since the amount of clicking of scrolling required to access them means I am underutilising them at present.
I suppose it is a lot more complex to get the sentence translation to show up when you answer correctly? Still seems to end up with a lot of clicking and scrolling to access the sentences to check the meaning, I’m just slightly more motivated to do so having seen the sentence pop up already.
Thanks!
I use a script that automatically opens the more info tab on a wrong answer from which I can just use spacebar to scroll to the sentence translation. That at least automates one step of getting to the translation, but I can see how a keyboard shortcut to display the translation might be a nice improvement.
Ah, that sounds really good, any chance you’ve got a link to that script?
Huh, interesting. That character has two of the radicals correct and the third one wrong, although the cleat vs evening radical could be considered visually similar.
The script pulls the item data from WaniKani Open Framework’s cached instance. Given that that is the only character in the sentence that is incorrect, I’d assume that either the WK api is returning the sentence that way, or the font is rendering the character incorrectly. Both seem unlikely. When I have a bit of time, I’ll go ping the API directly (independent of WKOF) to see what it’s returning for that slug.
Even more interesting, I have an android application that uses Google ML to recognize kanji and then provide a list to redirect to jisho,org and it recognizes the kanji in the sentence above, shows it rendered above
…but then redirects to 将 - Jisho.org
I suspect that just has two ways to write the same thing?
Yes. Apparently, the simplest resource to understand this isn’t a dedicated Japanese dictionary - 将 - Wiktionary
A dedicate Japanese font wouldn’t stray too far from this, even if [lang="ja-JP"] isn’t tagged, or the device is wrongly set somehow.
“Sawarabi Mincho” is indeed a Japanese font, but it isn’t complete… (therefore fallback to machine settings, and right now I force Chinese locale just to be sure.) …and I think WaniKani already supplied some good fallback Japanese fonts as well.
