-
Notifications
You must be signed in to change notification settings - Fork 1.3k
-
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
Report of characters that may need new glyphs for HK #215
Comments
U+465B 䙛: The CN glyph was fixed by changing the middle component on the right from 厶 to 口, causing a side effect that it's no longer sharable with HK. U+9834 頴: Top-left component is different, can't use JP glyph. U+72C5 狅: The HK glyph isn't correct. But TW glyph is probably wrong too, as it currently looks the same as U+72C2 狂. |
Also, whenever 女 is a left radical, as in 好 and numerous other characters, the strokes ㇒ piě and ㇀ tí for the HK glyphs should neither intersect (as in the current Source Han Sans HK font and in the TW standard), nor meet at their exact ends (as in the CN standard). Rather, ㇀ should touch ㇒ near its upper end. (Intersecting ㇒ and ㇐ héng are correct when there is no other component to the right of 女, as in 女, 妻, and for the upper and the lower right components of 姦, as opposed to the character's lower left component.) |
@LiliCharlie Unifiying the HK form of the left-side 女 component with the TW form was an intentional design decision, and therefore a non-issue. For comparison, Apple's Pan-Chinese PingFang family went to an extreme whereby the CN form of this component is used in its SC, TC, and HK fonts. |
Unlike all other CJK locales the 丱 component in HK-style 關 and 聯 has ㇑ instead of ㇓. |
@LiliCharlie You'll need to provide a much clearer explanation, because there is no HK-specific glyph for either U+95DC 關 or U+806F 聯. The former has only JP (shared by KR) and CN (shared by TW and HK) glyphs, and the latter has JP (shared by KR), CN, and TW (shared by HK) glyphs. The image below shows their JP, KR, CN, TW, and HK forms: |
In the HKSCS Reference Font "華康標準宋體"="DFSongStd" available from https://www.ogcio.gov.hk/en/our_work/business/tech_promotion/ccli/download_area/font_and_software.html the characters look like this: |
@LiliCharlie Note that Source Han Sans HK follows the "Reference Glyphs for Chinese Computer Systems in Hong Kong" released by OGCIO in 2017, which can be downloaded here. The document is more recent than the font you mentioned, which was released in around 2007. Here's an excerpt from the document. The non-vertical form is adopted for the second stroke of the 丱 component. |
@tamcy Oh, I see. And the same thing seems to have happened to the kai-style glyphs representing 關 and 聯. |
@LiliCharlie So far no downladable/purchasable font product was released alongside the Reference Glyph document. |
@tamcy That's a pity. My pdf analysing tool reports that fonts called "華康香港新標準宋體(P)", "DFHKNewStdSong-W3-HKSCSP-U", "DFHKNewStdKai-W5-HKSCSP-U", and "華康香港新標準楷書(P)" are among the ones used to produce the document. The people of DynaComware Corp. should know more. |
I think I've found the two fonts at https://www.dynacw.com.hk/en/product/product_download_detail.aspx?sid=2588 and https://www.dynacw.com.hk/en/product/product_download_detail.aspx?sid=2589 (replace /en/ with /zh/ to change the language to Chinese). |
HK and TW glyph additions from this issue are now reflected in the table in Issue #206. |
Thanks! As the design of 狅 is different for TW and HK (the middle horizontal stroke is narrower than the bottom one for TW, for HK the middle one is the widest), I think a new HK glyph will also be needed in addition to fixing the current TW one? |
The following HK characters cannot share glyphs with other regions. A new glyph would probably be necessary, but I didn't go through all CIDs so I'm not sure if any unmapped glyph could be used. That's why I open a new issue here.
[Edit: removed 巟 & 慌 as they're reported before]
A. 𦐇-related characters
(I do have doubt about why this form was chosen, and will take my query to OCGIO-CLIAC when I have time)
B. Others
The text was updated successfully, but these errors were encountered: