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
There is a minor issue in the JP glyph where there is no feet on the 口 part in the top 敬 part as circled, but I think it's okay to have the left feet on the 口 part because there's enough space for it. The TW/HK glyphs keep the left feet on the 口 part. And the irony is that the v1 CN glyph looked better. Honestly I do not know which glyph is based off Kozuka Gothic, as both the JP glyph and the v1 CN glyph look slightly different from Kozuka Gothic.
For JP, either adjust by adding the feet to the 口 part, or restore the v1 CN glyph to replace it. If Adobe takes the adjustment approach, maybe try to match the proportions of Kozuka Gothic.
On another note, the v1 CN glyph is technically wrong, and the JP glyph that is also currently mapped to CN in v2 is actually unsuitable for CN use, because the right part of the top 敬 part is not supposed to be a throw stroke (捺) but rather a drop stroke (點), because of the unwritten rule of 避重捺 (no repeated throw strokes) in China's 新字形 glyph standard. That is why a new CN glyph is needed. Suggest to create it after adjusting the JP glyph to add the left feet on the 口 in the top 敬 part (or restoring the v1 CN glyph for JP use).
Design-wise, the right part of the top 敬 part should be similar to the TW/HK glyph, but I'm not sure if the drop stroke should be connected to the surrounding strokes.
This is the list of commercial fonts on my Mac, the ones circled in red (Heiti SC, Hiragino Sans GB, Lantinghei SC) shows the drop stroke not connected to the surrounding strokes, similar to the TW/HK glyph of Source Han Sans. The ones circled in cyan (Pingfang SC and Yuanti SC) shows the drop stroke connected to the surrounding strokes.
檠 (U+6AA0) is a G0 source according to the Unicode charts, and a GB2312 character. Therefore, it is considered an essential character that will require a new GB-compliant CN glyph.
This is my mockup of the new CN glyph, assuming the drop stroke in the right part of the top 敬 part should be connected to the surrounding strokes.
Source Han Serif is fine as it is.
The text was updated successfully, but these errors were encountered:
There is a minor issue in the JP glyph where there is no feet on the 口 part in the top 敬 part as circled, but I think it's okay to have the left feet on the 口 part because there's enough space for it. The TW/HK glyphs keep the left feet on the 口 part. And the irony is that the v1 CN glyph looked better. Honestly I do not know which glyph is based off Kozuka Gothic, as both the JP glyph and the v1 CN glyph look slightly different from Kozuka Gothic.
For JP, either adjust by adding the feet to the 口 part, or restore the v1 CN glyph to replace it. If Adobe takes the adjustment approach, maybe try to match the proportions of Kozuka Gothic.
On another note, the v1 CN glyph is technically wrong, and the JP glyph that is also currently mapped to CN in v2 is actually unsuitable for CN use, because the right part of the top 敬 part is not supposed to be a throw stroke (捺) but rather a drop stroke (點), because of the unwritten rule of 避重捺 (no repeated throw strokes) in China's 新字形 glyph standard. That is why a new CN glyph is needed. Suggest to create it after adjusting the JP glyph to add the left feet on the 口 in the top 敬 part (or restoring the v1 CN glyph for JP use).
Design-wise, the right part of the top 敬 part should be similar to the TW/HK glyph, but I'm not sure if the drop stroke should be connected to the surrounding strokes.
This is the list of commercial fonts on my Mac, the ones circled in red (Heiti SC, Hiragino Sans GB, Lantinghei SC) shows the drop stroke not connected to the surrounding strokes, similar to the TW/HK glyph of Source Han Sans. The ones circled in cyan (Pingfang SC and Yuanti SC) shows the drop stroke connected to the surrounding strokes.
檠 (U+6AA0) is a G0 source according to the Unicode charts, and a GB2312 character. Therefore, it is considered an essential character that will require a new GB-compliant CN glyph.
This is my mockup of the new CN glyph, assuming the drop stroke in the right part of the top 敬 part should be connected to the surrounding strokes.
Source Han Serif is fine as it is.
The text was updated successfully, but these errors were encountered: