source-han-serif icon indicating copy to clipboard operation
source-han-serif copied to clipboard

(Low priority) Replace uglier looking CN glyph for components with 侖 with JP glyphs, perhaps even restoring them from v1.001

Open Marcus98T opened this issue 2 years ago • 3 comments

I have edited my original post to expand on my issue with 侖, and I honestly think that it should have been a unifiable difference. In the CN glyph, the bottom right component, 冊, the vertical strokes are not level because of the hook. The JP glyphs (including some that were removed) managed to keep the balance. Screenshot 2021-11-15 at 22 17 39

Maybe someone can correct me on why the lopsided balance is a must for CN and subsequently TW/HK glyphs, which is why I put it as low priority. Otherwise it is a unifiable difference.

Screenshot 2021-11-15 at 22 09 46

The ones in green (v1.001 JP glyphs) means they can be restored to replace the CN glyphs (marked in yellow) for all locales: 陯埨腀碖稐蜦踚鯩. 菕 only for JP/KR/CN locales as TW/HK have the split 艹 radical, so for TW/HK, adjustment is needed (as mentioned below). v1.001 婨 (in red) cannot be restored because the left radical cannot be used for CN/TW/HK locales. The ones in orange means please adjust the bottom right part to match the aesthetics of the JP glyph: 崘 (CN and HK), 婨 (CN and HK), 耣, 綸, 論, 菕 (TW/HK only, it was supposed to be coloured orange, but it's yellow due to my error, instead I suggest basing the TW/HK forms off the restored v1 JP glyph), 崙, 圇 (TW/HK only), 癟 The ones in blue means please map them to v2 JP forms and remove the CN glyphs: 倫掄淪棆輪錀

Originally when I wrote this, for 溣 U+6EA3, I was thinking perhaps they didn't listen to my suggestion, or I was way too late (I asked to reconsider in October 2018 with a reply from Dr. Lunde), and now the uglier looking CN glyph for 溣 U+6EA3 remains and is mapped to all locales. Therefore like the glyphs marked in yellow above, please restore the v1.001 JP glyph and replace the CN glyph for 溣 as well. Screenshot 2021-11-15 at 21 31 31

Source Han Sans also has this issue as well, but glyphs to change would be different due to different design choices. There is actually no issue with the 侖 component on Source Han Sans. But still, I want them to adjust the component on Serif so it's like Sans.

If this is not possible, leave it until a future v3.

P.S. High priority: Fix TW mapping of 婨 and 崘 to the HK glyph. UPDATE 1: And also map the JP glyph of 耣 to TW and HK. UPDATE 2: Corrected some errors in my post. UPDATE 3: No issue on Source Han Sans actually. Amended the post to reflect this.

Marcus98T avatar Nov 15 '21 13:11 Marcus98T

Apologies if I accidentally mentioned this issue on my glyph consolidation page on Source Han Sans due to me not checking properly before I post, because I just checked on Sans that it was not an issue at all. Please disregard what I did and just fix Serif (the bottom 冊 part) so they look like the below image (which is Sans). Screenshot 2022-02-03 at 21 08 22

Marcus98T avatar Feb 03 '22 13:02 Marcus98T

It might related, I checked with 匾<U+5338> for JP mapping, which maps to the TW glyph, it also has a similar issue. If such design is intended to be "regional difference" (Which I deem unnecessary as JP can also use TW mapping for U+5338), maybe rearrange a specific JP glyph for it as it is part of Adobe-Japan1-7.

TW Glyph: uni5338-TW

Mock-up JP Glyph: uni5338-JP

ChiuMing-Neko avatar Jan 07 '24 06:01 ChiuMing-Neko

It might related, I checked with 匾<U+5338> for JP mapping, which maps to the TW glyph, it also has a similar issue. If such design is intended to be "regional difference" (Which I deem unnecessary as JP can also use TW mapping for U+5338), maybe rearrange a specific JP glyph for it as it is part of Adobe-Japan1-7.

TW Glyph: uni5338-TW

Mock-up JP Glyph: uni5338-JP

Also see this issue (there is a table for Serif):

  • https://github.com/adobe-fonts/source-han-sans/issues/425

Marcus98T avatar Jan 07 '24 17:01 Marcus98T