they weren't there originally, then there is a commit where they were added which says "Recover stroke numbers from SVG directory". But in the same commit the stroke orders for kana were also added, so it might have been just a side effect of something useful.
Another thing I don't really understand is why all the ASCII characters were copied into the "wide ascii" positions:
The commit summary actually says "The ascii characters copied to the full width character positions." which I think was completely pointless. KanjiVG doesn't have the entire JIS character set, since that includes Greek and Russian letters, and various graphical symbols, as well as half-width katakana (narrow katakana), so there wasn't any clear reason to stuff these duplicates into there.
I might bring these two issues up on the mailing list at some point.
https://github.com/KanjiVG/kanjivg/commits/master/kanji/0004...
they weren't there originally, then there is a commit where they were added which says "Recover stroke numbers from SVG directory". But in the same commit the stroke orders for kana were also added, so it might have been just a side effect of something useful.
Another thing I don't really understand is why all the ASCII characters were copied into the "wide ascii" positions:
https://github.com/KanjiVG/kanjivg/commits/master/kanji/0ff2...
The commit summary actually says "The ascii characters copied to the full width character positions." which I think was completely pointless. KanjiVG doesn't have the entire JIS character set, since that includes Greek and Russian letters, and various graphical symbols, as well as half-width katakana (narrow katakana), so there wasn't any clear reason to stuff these duplicates into there.
I might bring these two issues up on the mailing list at some point.