Open tamcy opened 2 years ago
For the items below, I suggest to remap the affected regions to another glyph to better match the required regional standard (or the one chosen by the font).
(The items listed below are mostly fixed. The only remaining item is A13, currently the HK form is mapped to the TW CID)
# | Codepoint | Character | Affected Regions | Remap Suggestion | Additional remarks |
---|---|---|---|---|---|
A13 | U+68C8 | 棈 | HK | uni68C8uE0101-JP |
For the following items, I believe a new glyph would be needed for the glyph to match the required regional standard or the one chosen by the font.
# | Codepoint | Character | Affected Regions | Current Glyph Name | Reason |
---|---|---|---|---|---|
B1 | U+99F5 | 駵 | CN,TW^,HK | uni99F5-JP | Incompatible stroke form for "匚" in 丣, it should be the same as the stroke form of "匚" in "亞". |
B2 | U+6F7B | 潻 | CN,TW,HK | uni6F7B-JP | Last stroke of 禾 is different |
# | Codepoint | Character | Affected Regions | Current Glyph Name | Reason |
---|---|---|---|---|---|
B3 | U+5DAF | 嶯 | TW,HK | uni5DAF-CN | Different design for 耳 |
B4 | U+69B3 | 榳 | TW,HK | uni69B3-CN | Different design for 廷 * |
B5 | U+7407 | 琇 | TW,HK | uni7407-CN | Last stroke of 禾 is different |
B6 | U+78F0 | 磰 | TW^,HK | uni78F0-JP | Vertical stroke of 𦍌 doesn't protrude |
B7 | U+7AE7 | 竧 | TW,HK | uni7AE7-CN | Incompatible design for 身 |
B8 | U+8A94 | 誔 | TW^,HK | uni8A94-CN | Incompatible design of 廷 * |
B9 | U+8B4F | 譏 | TW,HK | uni8B4F-CN | The 人 component doens't protrude the horizontal stroke (all other 幾-composed characters have their dedicated TW/HK glyphs (examples); U+8B4F 譏 is the only exception) |
B10 | U+8E8D | 躍 | TW,HK | uni8E8D-CN | Hooks exist for 羽 |
B11 | U+9385 | 鎅 | TW^,HK | uni9385-CN | Different design for 界 (Other similar characters for reference) |
# | Codepoint | Character | Affected Regions | Current Glyph Name | Reason |
---|---|---|---|---|---|
B12 | U+3C18 | 㰘 | HK | uni3C18-CN | Different design for 糸 |
B13 | U+5F5D | 彝 | HK | uni5F5D-CN | Different design for 糸 |
B14 | U+655C | 敜 | HK | uni655C-TW | Second stroke of 人 is different |
B15 | U+6F78 | 潸 | HK | uni69B3-CN | Last stroke of the second 木 is different |
B16 | U+7298 | 犘 | HK | uni7298-CN | Last stroke of the second 木 is different |
B17 | U+8EB2 | 躲 | HK | uni8EB2-CN | Different design for 身 |
^: HKSCS characters, out of scope for TW. Remap suggested anyway for better regional consistency.
This is similar to section B, but fixing the item doesn't involve a new glyph be added. I will also list the concept fix if the illustrated problem may not be obvious.
# | Codepoint | Character | Affected Glyph Name | Remarks | Concept (if available) |
---|---|---|---|---|---|
C1 | U+5C7E | 屾 | uni5C7E-TW | The composition should look like 昍, i.e. two components standing beside each other. | |
C2 | U+515C | 兜 | uni515C-HK | The second stroke of the topleft component ("└") is written as one stroke. | |
(Fixed in v2.003) | |||||
(Fixed in v2.003) | |||||
(Fixed in v2.003) | |||||
C6 | U+23256 | 𣉖 | u23256-HK | The 火 component is different from the chosen HK form. |
That's it, thanks again!
My additional notes:
A3 might probably need to have the JP glyph on all regions as per this issue. Then the CN glyph can be removed. A4 will need uni6F74uE0101-JP to map to CN as well, because like HK and TW, there is no extra dot in 者 for the CN region.
A26 appears to have an EDB reference error showing 阱 instead of 阪. Maybe @tamcy needs to edit the graphic and reupload.
B11 will also need the new glyph to be mapped to JP and KR for consistency sake.
EDIT: Funny that the CN region for 界 components is mapped to JP for both Sans and Serif. I suggest instead to adjust those two characters: 䛺 (U+46FA) and 鎅 (U+9385) to be more consistent with the other 界 characters. Don't add any new glyphs and don't change the mappings for B11.
As for 琾 (U+743E), restore the v1 JP glyph to replace the CN glyph.
For C1, the TW form, after adjustment, would also need to be mapped to JP and KR for aesthetics sake.
Now onto the topic of unifying glyphs for the sake of reducing unnecessary CIDs (as far as I can without breaking China's 新字形 rule):
As for A2, in the future I might need to make a new issue on both Sans and Serif issue pages concerning a potential unification of the 夕 and 多 components, on whether it's acceptable if the dot (丶) can touch the ク part for the CN region. 名 (U+540D) however, could be handled differently because of balance, so for now, I agree for A2 to be mapped to CN for TW/HK regions.
As for A8 and A15, same as A2 in terms of making a new issue, except it has to do with the 死 component, where all regions may need to have 匕 connect to 一 (Of course I know the TW region have to be treated differently for the 匕 part, so not entirely unifiable, and yes, unlike the JP style that I prefer for other components, the CN style would be preferred for JP and KR regions).
A23, for the time being, I agree that the HK region should map to the CN form, but on whether the 八 component can be unified with CN dropping that Song-style detail from the second stroke in favour of the JP-style glyph shape, I wonder if it could be possible without breaking the 新字形 rule? That I'll post a new issue soon.
UPDATE x2: I have made a new consolidated issue page concerning glyph unification.
U+7CEF: Currently mapped to CN, but the component design of 雨 should be the same as that of TW. The TW glyph cannot be used either because of the design difference for 米.
# | Codepoint | Character | Affected Regions | Current Glyph Name | Reason |
---|---|---|---|---|---|
B13 | U+7CEF | 糯 | HK | uni7CEF-CN | Different design for 雨 |
(also applies to v2.003)
U+7E6D: The TW glyph is used for HK but the design of 糸 is different.
# | Codepoint | Character | Affected Regions | Current Glyph Name | Reason |
---|---|---|---|---|---|
B14 | U+7E6D | 繭 | HK | uni7E6D-TW | Different design for 糸 |
First of all, congratulations and thank you for the hard work on the release of Source Han Serif v2.001! Here I am listing the issues I found as of version 2.001, which I think are all isolated cases.
Here I try to retrain from writing too many remarks if I think the sample image is enough to illustrate the problem, so please tell me if they are not obvious enough.