-
Notifications
You must be signed in to change notification settings - Fork 648
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
JP glyphs uni2EA9-JP and uni5305uE0101-JP are not contained in SourceHanSerifJP-* ver.2.000. #125
Closed
3 tasks done
Comments
As noted in #123 this is fixed for the next release. |
The glyph names I found in version 2.000 that are contained in aj16-kanji.txt but not in AI0-SourceHanSerif are as follows.
|
3 tasks
trueroad
added a commit
to trueroad/HaranoAjiFonts-generator
that referenced
this issue
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
Prerequisites
Description
aj16-kanji.txt has uni2EA9-JP and uni5305uE0101-JP.
If I understand correctly, they are JP glyphs because they are contained in aj16-kanji.txt and have JP in the glyph name.
However, the JP fonts, SourceHanSerifJP-*.otf ver. 2.000, do not contain them.
I would like them to be contained in SourceHanSerifJP-*.otf.
The text was updated successfully, but these errors were encountered: