Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vocab SRS #33

Open
morgenman opened this issue Jul 18, 2021 · 1 comment
Open

Vocab SRS #33

morgenman opened this issue Jul 18, 2021 · 1 comment

Comments

@morgenman
Copy link

I just found this, and am pretty happy with using it to memorize kanji.
However, I have found that for vocabulary, it is a bit difficult to use.
For example: I have several vocabulary words that I am trying to memorize right now. I need to know first and foremost the pronunciation/meaning of them, and then, for some, the kanji. When studying under SRS however, I am presented with Kanji I don't know, and asked for a definition.
Here's my proposed setting to fix this:
Add a "dynamic kanji" option. When adding a 'vocab' word, show it in hiragana/katakana, unless the kanji it uses is 1. in the kanji deck, and 2. reached a certain level of mastery.
As a sub option, you could allow the program to "auto-add common kanji" to the kanji deck. That is, if the word you are learning contains a kanji that is frequently used in japanese, add it to your deck to learn. Of course, once you have a certain level of knowledge of said kanji, it could start quizzing you on the reading of said vocab word with the kanji included.
This would allow for far more efficient studying (at least for me).

@RudeBoyEEEE
Copy link

RudeBoyEEEE commented Aug 17, 2021

I just added a boat-load of vocabulary from Genki by searching for it in-app, and I'm having this same issue right now. Maybe a furigana option during SRS could help, too.

EDIT: On second thought, after discussing it with some other Japanese language students, this might be a bad idea. Getting some of them (or most of them) wrong is all part of the process, after all. I think the option should be there, but I'd advise heavily against the user choosing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants