3 ms·
This is neat. >Potential fields for usage include font design and machine learning. Am I correct that this scheme doesn't capture stroke info? I think that wo
by Arnavion 8y ago
This is neat.
>Potential fields for usage include font design and machine learning.
Am I correct that this scheme doesn't capture stroke info? I think that would be needed for fonts / handwriting recognition. Fonts have serifs / varying brush widths depending on stroke order and direction. Hand-drawn characters can also look quite different from the printed form (angles of strokes, two consecutive strokes being drawn without lifting the pen even though the printed form has two separate lines, etc).
Edit: As an example, 人 is defined as 257 which is certainly how it appears in print. However it is usually hand-written as something closer to 357, with 37 being the first stroke and 5 being the second. https://www.tanoshiijapanese.com/dictionary/stroke_order_details.cfm?entry_id=56003 https://www.tanoshiijapanese.com/dictionary/stroke_order_det...
- olalonde 8y agoIsn't stroke order something a set of rules you learn once (e.g. top to bottom, and left to right)? If so, you could programmatically determine the correct stroke order for each character.
- garmaine 8y agoThere are exceptions.
- fao_ 8y agoStroke order differs for japanese and chinese, as well.
- yorwba 8y agoFor stroke-level information, you'll probably want something like https://github.com/skishore/makemeahanzi https://github.com/skishore/makemeahanzi (for Chinese) or https://github.com/kanjivg/kanjivg https://github.com/kanjivg/kanjivg (for Japanese).
- jason_slack 8y agoThe "Inkstone Chinese" writing app by this same author seems useful for when I am riding someplace and can't pull out my notebook to practice on paper. https://www.skishore.me/inkstone/ https://www.skishore.me/inkstone/