Should the kanji 雄 also include its「お」 訓読み reading? Seems like that’s used in a good number of proper names, though also words like 雄牛.
I also noticed おん, such as in 雄鶏 and some proper names, and more rarely おう also in some other proper names, though I don’t know what all goes into your decision making with these sorts of specifics, so I figured I’d focus on the one that’s seems most prevalent.
Requesting that the kanji 苦 have “suffer” added to it’s list of accepted meanings. I just missed it because I put in “suffer” instead of “suffering”, which is dumb. There’s a lot of that going around, but it’s more of a problem on my work computer where I don’t have doublecheck installed.
I’ll pass this on to the content team
Update: We have added the「お」 訓読み reading to 雄 as we might add words that use the reading in the future but as it stands we have no plans to add words using the「おう」or「 おん」readings so we decided not to add them for now.
I’ve added “suffer” to the allow list for 苦
Why is the answer “skill” for 能力 not correct when it is translated as “skill” in two context sentences?
Thanks for pointing that out–I’ve added skill to the allow list.
Just discovered the JLPT coverage statistics at wkstats: Within the first ten WK levels we already learned 98.73% of the JLPT-N5 Kanji !
The only kanji left then for the full coverage is 書. However this kanji only appears at level 16, while the related radicals are covered at Level 9.
So what about moving the kanji down to have 100% of the JLPT-N5 content covered by the end of 快 Pleasant? I guess the vocabulary words prevent the change, right?
Since there are no official JLPT kanji lists, all such lists are just someone’s approximation of what might be on JLPT, loosely based on what was on tests 15-20yrs ago. The tests have been improved since then to focus more precisely on what a typical learner should have conversational experience with: daily-life stuff like family, travel, shopping, school, work, etc. So, rearranging WK kanji to match the old lists wouldn’t be all that helpful, to be honest.
That being said, I do think it would be great if they could provide vocabulary packs that focus on the same kinds of daily-life vocab.
To be fair, 書く qualifies pretty easily on the daily life front. The question as always though is “what kanji and vocab do you choose to move out of the lower levels to make space for this one?”…
Didn’t even know that there are no official lists and it’s all just an old assumption, guess I should have done some more research there. Anyways, thanks for the information. With that in mind, I totally agree with you.
We took a look at this suggestion and have now added そ to the kanji reading. We also agree that writing “None” for kanji readings we haven’t listed might be confusing, and we’re going to discuss this further to see if we can improve the UI. Thanks again!
Thank you RachelG and everyone at wanikani. I always knew the page design was effective, didn’t realize the extent of the visual cues effectiveness until that weird incident happened.
Trying to think about a fast fix that can be deployed at least temporarily. If there was a way for the time being to write a line of code that changes all the ‘None’ to ‘Not in Wanikani database’ or something similar, you won’t have to go over your entire database to add more readings (no idea how many None instances still exist).
@Mods
Petition to add “frustrating” and “disappointing” as synonyms for [悔しい] (https://www.wanikani.com/vocabulary/悔しい). That’s usually how I see it translated and I was surprised to see it not already listed as a synonym.
“Frustrating” and “Disappointing” are actually already on the allow list, we added them in December 2023
I’m gonna take a wild guess and say their intention was for it to appear in the normal alternatives list in a more official manner.
I have no stance on the matter, but I feel like a miscommunication was likely.
Really minor thing, but 督 lists “Director” under both the primary kanji meaning and the allowed whitelist.
Just wondering: how/where can you see the allowed whitelist?
The API within the auxiliary_meanings
property.
Or, more practically, with WaniKani Open Framework or my Show Hidden Allowed Answers userscript.
yeah that was my original intention! I didn’t know they were white-listed though… I could have sworn my answer was flagged as incorrect when I typed frustrating. I probably just misremembered.
I still stand by having them as official synonyms.
Fair enough, apologies for the misunderstanding, I’ll pass that on to the content team to see if they’d like to add them.
Thanks for the heads up, I’ll have a look at that now.