font docs; bad-translation-food for RU/PL fonts #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not necessarily intending for this to be merged.
It is rather to be used as supplemental information for a pr to odudex/MaixPy where font.c files were touched, so you know how those values were created.
README.md is updated because I find it easier to vi all font.c files at once, move to the unicode array definition, delete its r-value, read in the appropriate .kff file, write it, and onto the next font.c file. Also, I've altered a .kff filename to include yahboom... but maybe "small.kff", "medium.kff" and "large.kff" (or "three_cm.kff", "six_cm.kff" and "nine_cm.kff") could work too.
ru-RU.json and pl-PL.json are 100% google-translate filled. Additionally, the translated string for "ABC" has been given more food just after the space character (which would look funny in the keyboard, so remove those extra chars and re-bake if building to see RU and PL). Still they're at least initialized and up to date with develop_rc code base.