-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Consolidation of Post-V2 Glyph Sharing Suggestions #203
Comments
I think there is no need to create a separate set of glyphs for characters with the 尺 components for HK.
Therefore I suggest to remove the HK-specific glyphs for characters with the 尺 components, and use the JP/CN version (where appropriate) instead. Followings are the codepoints concerned:
|
@tamcy I am actually inclined to map U+4F2C 伬, U+544E 呎, U+54AB 咫, U+5C3A 尺, U+5EB9 庹, and U+8687 蚇 in the TW CMap resource to the corresponding HK glyphs. Also note that there are three additional cases whose forms are consistent, and used for both the TW and HK CMap resources: U+7C8E 粎, U+9FC8 鿈, and U+26B28 𦬨. These six mapping overrides are now reflected in the table in Issue #202. |
@kenlunde Ah yes, I forgot to also include the codepoints without regional-specific glyphs. Thanks. |
Because actual glyph removal won't happen until Version 3.000 (unscheduled), I am closing this issue, and will track such cases in Issue #227. For Version 2.000 dot releases, such cases will be handled via mapping overrides to the appropriate CMap resources (see Issue #202), leaving some glyphs unused. |
The following table shows the glyphs that have been explicitly targeted for removal due to glyph sharing or other reasons:
The text was updated successfully, but these errors were encountered: