-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Please clarify in the readme that not all GB 18030 characters in the SC/CN version of the fonts follow the PRC glyph conventions #412
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
Comments
Just for reference, here's another quote from Dr Ken Lunde on 22 November 2018 with regards to why some GB Extension CN glyphs were removed in favour of JP forms, and why some out-of-scope JP glyphs that were coincidentally suitable for CN use were removed in favour of TW forms, for occasional-use or rare-use Chinese characters:
|
Maybe I will help by writing something like this in the known issues section:
|
Since GB 18030 isn't a glyph standard you can't really say anything is not "GB compliant". I'm not opposed to having a note somewhere, but I wouldn't call it a known issue or an issue at all. It's just a statement of clarification that not all glyphs follow PRC representative glyph conventions. |
@punchcutter Thank you for the much needed reply. I have made some edits to my posts and my comments on other issues so the wording will better reflect the status of not following PRC glyph conventions, not the GB standard. |
Uh oh!
There was an error while loading. Please reload this page.
I know this issue has been reported several times before, but this pertains to the readme, although I think it will only be updated when a new version of Source Han Sans/Serif is released.
Due to limited glyph space, some Chinese characters now show JP forms or TW/HK forms as the only glyph shape for CN. Granted those characters are occasionally or rarely encountered in a Chinese context. I have since listed down every single GB18030 character showing JP forms and my suggestions on whether to restore them.
This above graphic is just an example of some hanzi following non-standard forms and using STHeiti (a Mac font) as a reference for PRC glyph conventions (although yes, the reference may not be entirely accurate).
In the Glyph Set & Region-specific Subs section of the readme, it does state that for Traditional Chinese, "the glyphs may or may not adhere to the Taiwan MOE glyph standard". Adobe can try to get as much GB 18030 characters to follow CN conventions as possible with a major redesign of Sans (and merging unnecessary regional components), but because of the aforementioned 65K glyph limit, it is likely they won't be able to get all of them to do so. Therefore and regardless, the readme should be updated to state that "some glyphs may not adhere to the PRC glyph conventions due to limited glyph space" or something similar for the Simplified Chinese row.
This issue also applies to Serif, although the good thing is there are less CN glyphs removed than in Sans.
EDIT: The known issues section in Sans 2.004 does not mention anything about this issue.

Same for Serif 2.002, and I filed this very issue months before its release.

I have also edited the issue title several times for clarity.
EDIT 2: I moved the list of GB standards here because I have deleted some inappropriate comments, for organizational purposes.
Here is the list of GB standards according to Unicode which I believe are basic standards for characters to follow the PRC glyph conventions:
Reference: https://www.unicode.org/reports/tr38/tr38-33.html
If there is any GB list in the reference link that I missed out on (or if I put a standard that is not necessary), let me know.
The text was updated successfully, but these errors were encountered: