First of all, thank you very much for this wonderful plugin (Vocabulary Builder). This used to be the "killer feature" of Kindle. Just a small problem though. Koreader's vocabulary builder seems to store whatever the dictionary query is, before combining the previous and next part of the context to form the whole. This works quite well with English, where fuzzy search can match different forms of a word (migrate, migrated, migrating etc.) However, when I try to look up korean words, more often than not, the user has to tweak the query to get a hit. For non-Korean speakers I will use English as an example. "He migrated to America and got married last year". If this sentence is rendered in Korean and the user tries to look up "migrated", often there is not a single hit. So the user has to manually change "migrated" to "migrate" ( The korean original form of a verb and its past tense in the middle of a sentence differ too much for fuzzy search to find a match). If the user chooses to add to VB in the modified lookup, The context would be "He migrate to America and got married last year", with the wrong form and tense. I also hope to export the words to Anki for future review, so getting the original form is necessary because of the need to fill the definition field.
Possible solution
A quick and fairly easy solution would be to take the approach of Kindle's VB where both original word(word stem) and word form in the sentence are stored along with the context sentence.
Word stem: migrate
Word in context: migrated
Context: He migrated to America and got married last year.
When user has to manually tweak the query and do another lookup, the VB should store the second look up as word stem.
This will also be useful even for English words. Because if words are to be exported to Anki, their stems(original forms) will be needed to query the definitions that form the back of a card.
I don't know if I have made myself clear. If it is necessary, I can provide screenshots to clarify.
@weijiuqiao
First of all, thank you very much for this wonderful plugin (Vocabulary Builder). This used to be the "killer feature" of Kindle. Just a small problem though. Koreader's vocabulary builder seems to store whatever the dictionary query is, before combining the previous and next part of the context to form the whole. This works quite well with English, where fuzzy search can match different forms of a word (migrate, migrated, migrating etc.) However, when I try to look up korean words, more often than not, the user has to tweak the query to get a hit. For non-Korean speakers I will use English as an example. "He migrated to America and got married last year". If this sentence is rendered in Korean and the user tries to look up "migrated", often there is not a single hit. So the user has to manually change "migrated" to "migrate" ( The korean original form of a verb and its past tense in the middle of a sentence differ too much for fuzzy search to find a match). If the user chooses to add to VB in the modified lookup, The context would be "He migrate to America and got married last year", with the wrong form and tense. I also hope to export the words to Anki for future review, so getting the original form is necessary because of the need to fill the definition field.
Possible solution
A quick and fairly easy solution would be to take the approach of Kindle's VB where both original word(word stem) and word form in the sentence are stored along with the context sentence.
Word stem: migrate
Word in context: migrated
Context: He migrated to America and got married last year.
When user has to manually tweak the query and do another lookup, the VB should store the second look up as word stem.
This will also be useful even for English words. Because if words are to be exported to Anki, their stems(original forms) will be needed to query the definitions that form the back of a card.
I don't know if I have made myself clear. If it is necessary, I can provide screenshots to clarify.
@weijiuqiao