This addon was coded entirely by Chat GPT with a reference code from the add-on (148002038) to help address bugs.
The author only guided the process and gave Chat GPT the requirements of the program.
This addon uses HTML ruby text for Japanese to make a hiragana field and kanji field
Requirements: 3 types of fields (not restricted by name)
Expression field ~ For Kanji/Hiragana/Furigana
program is looking for HTML ruby furigana
Reading Field ~ if empty the program will enter the furigana or hiragana from the expression field
it does not generate hiragana from kanji, only parses out the furigana or hiragana word
Kanji Field ~ Same as reading field but for just Kanji respectively
These three fields can be named anything, but they bust have been
created under tools>manage note type> fields
best keep the 'Reading' and 'Kanji' fields empty, and untested if bulk add occurs when something exists. If you need a
clean slate you can delete the reading or kanji field and remake it to start over.
How to use:
1) In the deck window, go to Tools in the top bar
2) Click "Extrapolate Meaning from kanji"
3) Follow the instructions
- The addon should display an alphabetical list of your decks
- Select a sub-deck or its parent deck
- Select the Note-Type of the cards you wish to add in bulk
You must have already
- Select Expression Field you want to use from your Note-Type
- Select Reading field to receive Hiragana / Furigana
- Select Kanji Field to receive the Kanji from the Expression field
- Continue
4) if all goes well, the program is completed
- (may take time depending on the number of cards selected)
- The program should display the number of cards skipped (already filled out)
- Number of Cards successfully filled
- Number of Cards failed (Katakana is not needed therefore Katakana will always fail)
5) Scroll through the deck in the browser to see if it looks correct.
The purpose of the addon was to make dedicated fields for hiragana and kanji from a downloaded deck.
Such as the Genki official deck which used HTML RUBY as opposed to Anki's default syntax. Although one may
not need this if their expression field already has both, it may be useful for convenient customization of many
cards from the same note type in decks.
The primary goal, however, was to improve the compatibility of an HTML ruby deck to other addons,
such as pitch accent generator addons, which could not handle the HTML ruby. Separating Kanji from furigana
into different fields may help some add-ons do their job.