Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix usu #290

Closed
wants to merge 28 commits into from
Closed

Fix usu #290

wants to merge 28 commits into from

Conversation

benkasminbullock
Copy link
Member

See #180 et al.

06b43.svg and 063d2.svg contained incorrect stroke types, but their
stroke order is actually the one required by issue 180.

The other change in this commit is to add various missing elements on
groups.
For the case that there is no HzFst file, explicitly swap the strokes
around within the XML.
This commit just renames files to fix issue 190. HzFst are renamed to
the plain file name, and the plain files with the stroke order error
are renamed to HzLst.
Also change original field on top element to be correct two boxes
The correct Kangxi radical for 0820a is 臼
This makes sure that the tradit radical has an element associated with
it.
In the cases where no variant Nelson radical exists, change the value
of kvg:radical to "general" from "tradit". The cases where a variant
Nelson radical exists are unaltered.
The five files in this commit all have a general radical in the
correct place plus a "nelson" radical in somewhere very unlikely, but
which uses the same original element as the general radical. Although
I don't have a copy of Nelson to check against, I'm fairly certain
these are errors, since Nelson was at least consistent.
This adds missing cases of nelson or tradit to the kvg:radical field
on the appropriate elements.
This kanji had its strokes muddled up, so I've hand-edited them into
the correct order.
@benkasminbullock benkasminbullock deleted the fix-usu branch April 13, 2022 00:29
@benkasminbullock
Copy link
Member Author

This got into a huge mess somehow, Anyway instead of spending a lot of time trying to work out what happened, I'm closing this pull request, because it's easy enough to just check out the newest version of the master branch again and run the script again to fix all the problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant