paploo / goi Goto Github PK

Need a way to encode simple prefix/suffix grammar pieces onto cards without affecting text-to-speech.

Use cases include:

• -て + {word}, such as 「もいいです」 or 「はいけまっせん」
• {word} + negative, such as 「ぜんぜん」、「何も」, and 「別に」
• 〜 used as a prefix or suffix qualifier

Possible solutions include:

• Using a word type or sub-type to capture (e.g. PREFIX and SUFFIX already tell me about one of the cases)
• Explicit encoding of prefix/suffix fields, giving flexibility.

Note: In Anki these should be japanese_prefix and japanese_suffix fields so that I can control which cards to put them on (e.g. definition vs listening cards).

SequelImporter (which is currently not used in my workflows) was missed when adding conjugation support.

AC

• SequelImporter needs conjugation_set and conjugation loading support.

Namely:

• The title should check that capital letters (when not directly next to other roman characters) are full-width.
• The meaning should contain no full-width or half width letters, but just normal letters.

Now that the feature set is starting to stabilize, do some polishing:

• Make the input/output files clearer by arranging in directories and documenting.
• Make first-time use of schema migrations and the various data load files (including the kanji!) easier, including making loader scripts and updating documentation.
• Use OptionParser on arguments to bin

AC
Insert validation and/or reporting into vocabulary transcode via the transformer tooling:

• Report on any entries with same preferred spelling or kanji spelling (this is not always wrong, but should know to make sure since hard to clean-up in Anki).
• Fail if more than one vocabulary entry has the same ID.

• In Goi, the grammar rule title is rendered using Goi furigana templating, which uses curly braces; this means curly brace literals are stripped out as being part of the furigana.
• In Anki, in the grammar rule title, square brackets are taken for its furigana template, and thus don't render right.

Would like to have the following behavior:

• Square brackets in the JSON for the title should—in the Anki exporter—output as HTML entities to make them render correctly (And or use an alternative bracket character).
• Curly braces should continue to generate furigana correctly into braces in Anki, allowing for furigana.

Additionally:

• Parens in JSON should render as parens in Anki.
• Angle brackets in the JSON can be used for HTML tags for formatting; as this is potentially useful, no policy is set for them at this time.

Need a grammar rules deck.

Each rule should have one or more examples. see JLPT先生 for some structure ideas.

The necessary cards are still TBD.