You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a separate glyph is provided for 系 component in TW/HK, with the top throw stroke (丿) varying from not touching (in ExtraLight) to touching (in Heavy) the bottom 糸 component.
However, current TW/HK does not mandate that the two components must not be touching. TW education reference only say there is a throw stroke above 糸, but nothing about if it should be touching or not and the relative lengths. HK reference does not state if the touching are required o Given the loose requirement, I will say that the 系 component is unnecessarily differentiated and just wasting glyph counts.
Thus, I would like to propose using the CN version of 系 in TW/HK. The CN version offers a better balance (both geometric balance and white space balance) relative to TW/HK. It also avoid the unclear touching-or-not problem that currently exist across weights and characters, such as 遜 which is clearly touching at ExtraLight.
By merging 系 component in TW/HK to CN, 11 glyphs can be freed up for other usages such as the pending Macau extension or GB18030-2022 compliance.
11 TW/HK glyphs that can be removed and merged to CN: 係喺孫愻(HK)搎槂猻綔緐緜鯀
15 TW/HK glyphs that need to be edited: 愻(TW) 懸(TW) 懸(HK) 縣(TW) 縣(HK) 繇(TW) 繇(HK) 纛(TW) 纛(HK) 蓀蘨㘥𤄏𦅚𧪾
No changes needed (probably): 遜(TW) 遜(HK)
The text was updated successfully, but these errors were encountered:
Currently a separate glyph is provided for 系 component in TW/HK, with the top throw stroke (丿) varying from not touching (in ExtraLight) to touching (in Heavy) the bottom 糸 component.
However, current TW/HK does not mandate that the two components must not be touching. TW education reference only say there is a throw stroke above 糸, but nothing about if it should be touching or not and the relative lengths. HK reference does not state if the touching are required o Given the loose requirement, I will say that the 系 component is unnecessarily differentiated and just wasting glyph counts.
Thus, I would like to propose using the CN version of 系 in TW/HK. The CN version offers a better balance (both geometric balance and white space balance) relative to TW/HK. It also avoid the unclear touching-or-not problem that currently exist across weights and characters, such as 遜 which is clearly touching at ExtraLight.
By merging 系 component in TW/HK to CN, 11 glyphs can be freed up for other usages such as the pending Macau extension or GB18030-2022 compliance.
11 TW/HK glyphs that can be removed and merged to CN:
係喺孫愻(HK)搎槂猻綔緐緜鯀
15 TW/HK glyphs that need to be edited:
愻(TW) 懸(TW) 懸(HK) 縣(TW) 縣(HK) 繇(TW) 繇(HK) 纛(TW) 纛(HK) 蓀蘨㘥𤄏𦅚𧪾
No changes needed (probably):
遜(TW) 遜(HK)
The text was updated successfully, but these errors were encountered: