sbseltzer / ja-srs-utils Goto Github PK

Furigana may also be useful for not non-kanji characters, such as katakana (and perhaps other things?) as well. Much like Japanese toddlers, I learned hiragana before katakana, so it's a legit use-case in my eyes.

In any case, a quick solution would be "if furigana braces are encountered and the character before is a non-kanji, seek backwards to the next space" or something. It may be worth considering the merits of making this the general case, since it's a necessary workaround when you only want to specify furigana for a few particular kanji. The spaces could be trimmed after the fact.

JS Booster breaks when your Anki User directory path contains non-ASCII characters. For AJATTers who have switched their OS to Japanese, such as I have, this leads to breakage when their Documents folder (which is where Anki stores its media) has been renamed to a Japanese counterpart. Such is the case on my Ubuntu partition.

I see three potential solutions:

1. Make step-by-step instructions on how to modify your Anki path and username.
2. Fix JS Booster and resubmit it to AnkiWeb.
3. Make some kind of conversion script to reconfigure Anki in such a way that it won't break.

Number 2 is attractive since it's the most hands-off approach, but the others still deserve attention.

See if there's a solution for this that doesn't involve manually installing the font on the OS.

Some users may prefer hovering over clicking to activate things. Some may want to make a button separate than target content to activate stuff.

Example: font cycling could happen on click of its element, hovering over the element, or clicking some other element. Doing the same for showing/hiding furigana would also be useful.

Combining/compressing the JS and CSS will be more important as this project grows. See if there's a nice way to do that locally.

While reviewing cards, the javascript appears to stop functioning after the first view, that is:

1. View front face (working)
2. View back face (not working)
3. View front of next card (still not working)

And so on...

This does not seem to occur when in edit or preview mode.

There is code laying around the stylesheet that was ripped from jisho.org to support furigana displaying similarly to <ruby> tags, which are not supported on all HTML browers. They appear to be available in Linux and Windows versions of Anki, but it may be a good idea to support the CSS replacement in card.js.

jQuery is pretty big. See if a suitable replacement can be found.

Cloze cards surround your cloze deletion with <span class="cloze"></span> which interferes with furigana parsing.

When furigana braces are set to "()"

Doing text{{c1::kanji(furi)}}text works.

Doing text{{c1::kanji(furi)::placeholder}}text works.

Doing text{{c1::kanji(furi)::placeholder(furi)}}text does NOT work.

Doing text{{c1::kanji::placeholder}}(furi)text does NOT work.

Doing text{{c1::kanji}}(furi)text does NOT work.

ja-srs-utils is pretty dry and doesn't make for nice prefixes. Come up with something better before people start actually using this.

After some initial testing, it looks like Mnemosyne is a definite go.

Media directory on Windows: %APPDATA%/Mnemosyne/default.db_media