Looks like renshuu is outdated on [uk] since it was removed from the glosses a while ago, so maybe when the [sK] spellings were added, no [uk] was detected then?
Is this feature supposed to interact with Kanji helper schedules yet? I marked two words to studio rate Kanji (いす->椅子 and どこ->何処), which have new Kanji for me. The words are both in the "Words for Beginner Japanese" schedule, which has the Kanji Helper schedule "Kanji for Words for Beginner Japanese" helper schedule attached, but the Kanji didn't appear there.
(Totally fine if it's not implemented yet, as both are experimental features so I wouldn't be surprised if they don't work together yet.)
I'll look at the jmdict stuff after, but thanks for posting it.
it "should" work for everything - there is nothing i'm aware of that is not implemented, it's just a matter of fixing bugs.
For the helper schedule, if you do the "settings reset" (that's where you go into the settings, change one of the helper settings (say, kanji level from n3 to n2, save, then back from n2 to n3), do the kanji pop up?
This will help me determine if it's the helper schedule settings that have an issue, or the actual point at which they are toggled on or off.
I may be able to spend some time working on this, so please continue to report bugs as you see them. At the moment, I believe the only known bug is the one mentioned above with the kanji helper schedules, which I'll hopefully get to soon.
Not sure if I should rather post this to the kanji helper post, but I noticed that the kanji helper adds the rare kanjis to the schedule, even if the word toggle is not on.
I would think it would be expecting that it would only add those kanji where I toggled "show rare kanji".
Yeah, I made a list of words that I want to toggle it on for (though I did it manually for myself). I assumed that was what the advanced search to-do was?
I was toggling rare readings on many words, and I found an issue that happens rarely, but it causes a word to not get toggled. There is no feedback to the user when this failure case happens (is there any feedback if the request fails?). I only have these screenshots.
I marked hundreds of words. This issue happened often in the first few hundred, but then stopped happening often after I realized that there was something fishy in the request logs. I managed to get a screenshot of the request logs one time when this happened. I saw it at least 3 times, and it looked similar, but I don't have those screenshots.
For one request of mark_rkanji, instead of a 200, it does a (very slow, 878ms in this case) 302 redirect, followed by a request with the restats parameter. The usual mark_rkanji is a POST request (with a request body containing the word id), but as you can see in the restats screenshot, it sends a GET instead. GET is definitely problematic because no request body is sent, and therefore no word is able to be marked.
