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 aj16-kanji.txt for added JP glyphs #123

Closed
wants to merge 1 commit into from

Conversation

trueroad
Copy link

Version 2.000 has added JP glyphs uni54E5-JP and uni68D7-JP.
However, aj16-kanji.txt contains uni54E5-CN and uni68D7-CN,
which were used for JP glyphs in version 1.001.

This commit fixes the glyph names in aj16-kanji.txt
to the added JP glyph names.

Version 2.000 has added JP glyphs uni54E5-JP and uni68D7-JP.
However, aj16-kanji.txt contains uni54E5-CN and uni68D7-CN,
which were used for JP glyphs in version 1.001.

This commit fixes the glyph names in aj16-kanji.txt
to the added JP glyph names.
@punchcutter
Copy link
Member

There are more than just these two glyphs that weren't updated properly in the aj16-kanji.txt file. I've fixed it and it will be in the next release. I also added a test to the test suite to make sure this can't ever happen again.

trueroad added a commit to trueroad/HaranoAjiFonts-generator that referenced this pull request Nov 1, 2021
Due to some issues with SourceHanSerif version 2.000,
the HaranoAjiFonts-generator was not able to generate HaranoAjiMincho.
This commit introduces some workarounds until SourceHanSerif is fixed.

adobe-fonts/source-han-serif#123
Fix glyph names in aj16-kanji.txt.
uni54E5-CN -> uni54E5-JP
uni68D7-CN -> uni68D7-JP

adobe-fonts/source-han-serif#125
Remove two glyphs that are not contained in SourceHanSerifJP.
AJ1 CID+13729
AJ1 CID+14019
This causes the two glyphs in HaranoAjiMincho to be missing
until SourceHanSerifJP is fixed in its next version.
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.

2 participants