rpos: and grade: already work as valueless searches but not with "n/a" standing in as no value (as is the case with Onyomi and Kunyomi). e.g. https://app.kanjialive.com/search/advanced?rpos= gives you all kanji without an explicit radical position classification but https://app.kanjialive.com/search/advanced?rpos=n/a gives zero results.

We're still offering eot, ttf and swf webfont formats. These aren't needed by recent browsers. And we should add woff2 as first choice since its files are about a third smaller than woff.

Are you interested by internationalization ?

By i18n, I mean only for https://app.kanjialive.com/.
I looked in the differents files :

• https://github.com/kanjialive/kanji-web-app/tree/master/partials
• https://github.com/kanjialive/kanji-web-app/blob/master/static/js/detail-controller.js#L234
• https://github.com/kanjialive/kanji-data-media/tree/master/language-data

I can propose french translations and help to adapt some files (such as endpoints for languages, e.g. https://app.kanjialive.com/fr/search).

If so, I don't really know what the best approach is. I was thinking of exporting the English sentences / words and using software like Poedit.

Trying to print anything from the web app (result or detail view) is effectively not possible. At minimum, it should resemble a screenshot. Beyond that, one could imagine more advanced layouts.

Just found this wonderful app, thanks so much for making it!

I'm currently learning stroke order, and their directions. For this purpose it would be useful if the step-by-step images contained a symbol as to where the current stroke starts. This would be faster to skim than playing the animation.

This is still under discussion.

Add social media buttons in the free space beneath the Hints field so that students can share their ability to read/write kanji. e.g. for Twitter, "I learned to how to write 森 today" etc.

Just a placeholder for now.

It would be nice if we could make some hand-drawn components bigger and easier to read. Kanji IDs with small components: 30, 45, 47, 53, 54, 55, 56, 57, 60, 64, 71, 74, 75, 76, 78, 80, 84, 85, 87, 89, 96, 97, 98, 100, 104, 116, 123, 124, 127, 129, 131, 133, 136, 140, 144, 146, 150, 151, 161, 165, 166, 178, 183. Not sure if this will involve editing the SVG file or the CSS.

Although the app will work on large mobile devices such as tablets it doesn't adapt its layout for use on smartphones.

CORS prevents JavaScript fetch from retrieving assets from the media CDN. Will you consider allowing traffic from any origin? Thanks

Public API could to be updated to also return kanji_svg files e.g. http://media.kanjialive.com/kanji_animations/kanji_svg/9_00.svg

See https://en.wikipedia.org/wiki/Goj%C5%ABon

Gojūon_order.xlsx

High-quality open-source Japanese fonts (Source Hans Sans) are now bundled with Windows and freely available from Adobe TypeKit. Could also look into variable fonts.