![]() |
|
Automatic vocab for RTK - Printable Version +- kanji koohii FORUM (http://forum.koohii.com) +-- Forum: Learning Japanese (http://forum.koohii.com/forum-4.html) +--- Forum: Learning resources (http://forum.koohii.com/forum-9.html) +--- Thread: Automatic vocab for RTK (/thread-12654.html) |
Automatic vocab for RTK - HelenF - 2015-04-02 I wrote an Anki plugin to choose vocab for an RTK deck, to add extra information to the question without actually switching over to Japanese keywords. The aim is to prioritise known words and common words, and avoid putting words on the front which might be misleading (but if they're known or common, it's nice to have them on the back). It loads the user's MorphMan DBs to detemine what is "known". By default, a word is "common" if the expression and reading are both tagged with JMDICT "nf10" or less (first 5000 words in "news1"). It's "not misleading" if either there is one possible kanji to fill in the blank from the whole of JMDICT; or the answer (expression and reading) is tagged "gai1"/"ichi1"/"news1"/"spec1" (the EDICT "P" tag) and the alternative answers have no JMDICT priority tag (the above plus "gai2"/"ichi2"/"news2"/"spec2"). Some examples are shown below. They use css classes: in the screenshots, the yellow highlight means "you should be able to read this", purple text means "not unique but you probably won't pick the wrong kanji", and red text means "risk of picking the wrong kanji". My current css (not pictured) uses green highlight for "you should be able to read this in kanji" and yellow highlight for "you should be able to read this in kana". If choosing the words by hand, it would be fine to put おる on the front because 居る and 織る don't mean "fold". But automatic choices are never going to be perfect. https://github.com/HelenFoster/misc/tree/master/anki/addons/kanjivocab Currently, a word is "common" if the expression and reading are both tagged with JMDICT "nf15" or less (first 7500 words in "news1"). It's "not misleading" if either there is one possible kanji to fill in the blank from the whole of JMDICT; or the answer (expression and reading) is tagged "gai1"/"ichi1"/"news1"/"spec1" (the EDICT "P" tag) and the alternative answers have no JMDICT priority tag (the above plus "gai2"/"ichi2"/"news2"/"spec2"). "Known" words are a messy hack at the moment. Not sure about the best way to do this. Some examples are shown below. They use css classes: currently, the yellow highlight means "you should be able to read this", purple text means "not unique but you probably won't pick the wrong kanji", and red text means "risk of picking the wrong kanji". Is this interesting? Would it be worthwhile for me to work this thing into a reusable state? (Has someone done this already and I missed it?) ![]() ![]() ![]() ![]() ![]()
Automatic vocab for RTK - Chomskyan - 2015-04-03 Man if only you'd been around a month or so ago when I was looking for something similar. I ended up making my own deck. this is the front. ![]() and the back ![]() ![]() It's based on Heisig's Second RTK book so each individual on reading has its own card. This means the same kanji may have multiple cards, but it also helps really cement the onyomi in your mind. Automatic vocab for RTK - kraemder - 2015-04-05 Those both look like nice decks. I was thinking of redoing RKT but I just don't want to use all English keywords etc. I have a lot of Japanese knowledge now I'd like to utilize. Automatic vocab for RTK - HelenF - 2015-05-24 I wrote an Anki plugin for this which I've been using myself. I wrote some documentation for it today, so here it is if any other MorphMan users are interested. https://github.com/HelenFoster/misc/tree/master/anki/addons/kanjivocab It should be considered beta testing at this stage. If I get some positive feedback here, I'll put it on AnkiWeb later. (Actually, only if MorphMan returns to AnkiWeb too, otherwise it would just confuse people.) Automatic vocab for RTK - ReneSac - 2015-08-29 I already have my japanese keywords chosen, but I would like to make anki display them with the ◯ and furigana like in those screenshots. Is that an automatic script/plugin? And by the way, what is the source of the images with the stroke order in those pictures? Automatic vocab for RTK - HelenF - 2015-08-30 Quote:I already have my japanese keywords chosen, but I would like to make anki display them with the ◯ and furigana like in those screenshots. Is that an automatic script/plugin?My plugin loads word-reading pairs out of JMDICT, and does the ◯ and furigana automatically. How easy it would be to do with your already-chosen words depends on what format you have them in currently. Quote:And by the way, what is the source of the images with the stroke order in those pictures?I'm using the stroke order font from http://www.nihilist.org.uk/ ---- Update: I've been using my plugin since the previous post, and it's working out pretty well for me. After recalculating, it's always fun to see a word that I learned recently come up during RTK reviews. Automatic vocab for RTK - ReneSac - 2015-08-30 Well, I just converted from this format (oldkey): 大(タン)な、きも To this one (newkey): 大胆な、胆 Using this simple script that worked on the exported csv: https://gist.github.com/ReneSac/90900f23a790262ecd61 I still have both formats. In the simplest form, I want a function to which I give the word (eg: 大胆な), and it gives me back a tuple with the ◯ form and the only furigana form. No need to colour it. Bonus points for disambiguating the reading based on the "oldkey" field. And thanks for the stroke order font. Automatic vocab for RTK - HelenF - 2015-08-31 I had a go at editing your script. It uses core.py and jmdict_freqs.txt from my GitHub link. Note that my code is Python 2 while your original was Python 3. I figure you know enough to debug the script if it's not quite correct... For the words it missed in your sample, looks like JMDICT only has 朝早く and not 朝早い. And JMDICT doesn't have the trailing な in its entries, so might be worth making the script remove those before looking up the word. Also, ideally it would split the furigana over the correct kanji (since the information is there already in the source csv). http://pastebin.com/RshFJE4P RE: Automatic vocab for RTK - rainmaninjapan - 2016-04-24 This is very useful! I converted from RevTK to Anki just for this. You should post it as a shared addon on Anki though, it was kind of a hassle to get it off github (I resorted to copy and pasting). RE: Automatic vocab for RTK - HelenF - 2016-04-26 Thanks for posting, I'm glad it was useful for someone! You're right, that could be awkward for non-git-users. Since my addon depends on MorphMan, I'd prefer not to post it as a shared addon. But I added a zip file to the repo like MorphMan has. (I looked into the GitHub "release" system, but it doesn't really make sense for a repo with more than one thing in it.) https://github.com/HelenFoster/misc/blob/master/anki/addons/kanjivocab-1.0.0.zip RE: Automatic vocab for RTK - polyturn - 2016-04-28 Looks like an interesting plugin. Is there a way to tweak this so that it rearranges my vocab deck in i+1 order instead? (based on my Kanji deck). I've been looking for a way to do that for ages.. RE: Automatic vocab for RTK - HelenF - 2016-04-28 I don't think my plugin has any relation to that. Sounds more similar to what MorphMan does, except it deals with morphemes and not individual kanji. Cangy had a Core6K spreadsheet with various sort indices for kanji sequence sorting on the sentence field. http://forum.koohii.com/thread-5091.html Looks like it was done with the kanji-sort script (itself not available now): "given a kanji list sort the input according to the furthest position in the list of all the kanji in a designated field of the input". http://web.archive.org/web/20101216055624/http://ankisrs.net/docs/ContribFugounashi.html#kanji-sort |