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

"Pair" kanjis in practice #146

Closed
polandreh opened this issue Jun 5, 2024 · 2 comments
Closed

"Pair" kanjis in practice #146

polandreh opened this issue Jun 5, 2024 · 2 comments

Comments

@polandreh
Copy link

When practicing a set, kanjis are shuffled randomly every time we want to practice (if the option is selected).

However, depending on the set, it would make more sense if certain kanjis can be grouped so that they stick together during the shuffling.

For example, I have a practice relating to food. So,
菓, 米, 果, 菜, 豆, 卵, 肉, etc. But 海苔 (nori) is a jukujikun, so 海 (sea) and 苔 (moss) by themselves don't work in this list.

Could we create a custom pair or group with our own expressions and hints so that we can practice them consecutively?

Maybe, we could have a "group" editor or object section where we can create these bundles of kanji, and add the groups in practice sets along with single characters.

@syt0r
Copy link
Owner

syt0r commented Jun 6, 2024

I can see some reason in this, but kanji in existing sets pretty much don't have any common context. I think it would make more sense for users to create custom sets if they want to review kanji with some specific context. Moreover, it would require categorizing a lot of kanji. I don't think there're a lot of benefits considering efforts

But this gave me another idea that I find more useful - creating kanji sets based on vocab sets. It will encourage learning vocab as well as kanji with similar context. Maybe a feature to post and view user created kanji and vocab sets withing the app could help with it too

@syt0r
Copy link
Owner

syt0r commented Oct 7, 2024

There are related issues #154 and #210 so I'm closing this one

@syt0r syt0r closed this as not planned Won't fix, can't repro, duplicate, stale Oct 7, 2024
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