Skip to content
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

Can we continue removing the feet from 口 when other components are below it? #293

Open
CoolMarvel43 opened this issue Apr 9, 2021 · 9 comments

Comments

@CoolMarvel43
Copy link

CoolMarvel43 commented Apr 9, 2021

It's been a long time, and I forgot to bring this up again until now. I suppose while this may not be important, and nobody at Adobe really reads through the consolidation of glyph threads anymore since Dr. Lunde left, I still think maybe the feet of 口 should be removed from all characters (especially JP and KR forms) where any other component is below or near 口. Hopefully this can be addressed for v2.005. (EDIT: v2.004 is an emergency patch release, so should have been v2.005) I will quote my own issues again for a start:

I have five more JP glyphs 廸廹廻廼廽 to do likewise.
Screen Shot 2019-04-11 at 19 26 10

And finally, feet removal time. I have decided that any 口 component within ⿵ like 門, or when 口 is on the left side of this ⿰ and there is a 丿 on the right side, then only the right feet be removed, keep the left feet.
Screen Shot 2019-06-08 at 12 59 38
Affected glyphs are 阁搁.
For the 屰 component, I find the feet inconsistency between characters baffling, and I think they should be removed from these characters: 塑槊愬厥闕 (JP), 磀縌 (SC and TC/HK).
If you think it's not appropriate to deal with 屰 as it is admittedly a tough nut to crack, maybe revert the glyphs to 2.000 for 逆 and 遡 (JP and KR) (adding back the feet), then add the right feet for 阙闕 (SC version). I must have been too far over what feet in what components to remove.

Every component with 中 above the ⿱ forms should have the feet removed (JP and KR affected): 虫忠盅𨨩 (not exhaustive).
Also these characters need to have the feet removed: 慥 (JP, KR and CN) 糙簉 (JP and KR), 瓲 (JP only), 瀜 (虫 part, JP only), 起趈趡趞趦趥趭趯 (JP, KR and SC), 鼬鼫 (JP, KR, TC and HK), 鼯(TC only), 兘 (JP only), 廸廹廻廼廽 (JP only, as mentioned before), 搥縋槌磓鎚 (JP only), 螸 (the 欲 part), 訄 (CN only).
Remove only the right feet: 訚誾 (CN and JP), 勂, 斮 (EDIT: Also include 啟 (SC and TC)).

In addition, the JP and KR glyphs are affected: 璡魋滙匯燞暹

@punchcutter
Copy link
Member

Thanks for writing this up. As you can see from the 2.003 release the recent focus has been on mostly minor corrections and moving to a variable font workflow, but we will start looking at these issues again.

@CoolMarvel43
Copy link
Author

CoolMarvel43 commented Jun 23, 2021

I forgot these following characters (now including CJK Extension A characters) with the 麦/麥, 风/風, 鬼 and 走 components, which the feet need to be removed.

麺 (JP), 麵 (JP, TW), 麯 (JP, HK), 䰠 (JP), 䰨, 飗, 飀 (CN, TW), 飅, 飜 (remove only the right feet from the 番 component), 魋 (JP, CN, TW), 鼯 (TW only), 䟒, 䞦 (CN, TW), 䞧, 䞩, 䞱.

List may not be exhaustive.

@NightFurySL2001
Copy link

It should be noted that which glyphs have their feet removed are pretty inconsistent:
image

Also, 简 (U+7B80) was changed from v1.004 to v2.004, which IMO actually looks worse:
image

@CoolMarvel43
Copy link
Author

Also, in case you missed it, I think the feet from any 隹 component in CN and TW should be removed to match the JP glyphs, here is the quote from 2019:

Then finally, for the 隹 component in all CN, TW and perhaps HK glyphs, the feet must be removed only when 隹 is on top of ⿱, similar to the JP glyphs which have no feet, so as to remove the noise when viewed on lower resolution screens.

Screen Shot 2019-06-08 at 14 19 28

Apologies for potential duplicates. Here are the affected glyphs, probably not exhaustive:

趡隼隻隽售集雋焦魋滙匯燞暹壅甕赝贋雘雟雥雧

焦 - 僬谯譙撨噍嶕潐憔嫶樵膲燋礁瞧穛蟭醮鐎劁鹪鷦顦蕉嶣癄趭
雋 - 儁擕懏檇臇觹鐫嶲寯
集 - 㗱襍潗㙫磼㠍㠎穕鏶雧
赝譍噟膺軈應鹰鷹
隼 - 㔼準㢑榫鎨鶽
壅饔罋甕㽫
隽 - 携槜镌鎸
隻 - 愯謢蒦篗
矍匷
矍攫玃戄彏欔䦆钁矡蠼躩貜籰

雟巂儶攜孈瓗欈蠵纗觿讗鑴驨酅

奪奮
蒦擭嚄獲濩嬳瓁檴臒雘矆矱穫鹱鸌耯蠖艧彟彠護鑊鳠鱯韄頀劐籆

戁臡




赝贋

雙 and 讐 has the feet removed, so no change for those two. I'm not sure about 閵躙藺 as nothing is obstructing the feet.

@CoolMarvel43
Copy link
Author

Also please remove the feet from 巨 (U+5DE8, JP only).

Screenshot 2023-02-28 at 14 36 21

@CoolMarvel43
Copy link
Author

Suggest to remove feet from the following glyphs containing the Japanese kyujitai variant form of 並:

  • uni4E26uE0101-JP (並󠄁)
  • uni63BD-JP (掽󠄀)
  • uni78B0-JP (碰󠄀)
Screenshot 2023-06-27 at 17 41 23

Referencing commercial fonts like Toppan Bunkyu Gothic and YuGothic, they have no feet on the characters with the variant form of 並, although YuGothic is inconsistent with not having feet on the base character itself. But it's possible for Source Han Sans to not have feet on the variant form of 並.

@CoolMarvel43
Copy link
Author

Remove top right feet from 弖 (U+5F16) as circled.

Screenshot 2023-06-28 at 19 19 01

@CoolMarvel43
Copy link
Author

CoolMarvel43 commented Jun 28, 2023

Remove feet from inner 山 part of 匩 (U+5329) as circled.
Screenshot 2023-06-28 at 23 11 07

Also remove right feet from 劰 (U+52B0) and 劶 (U+52B6) as circled.
Screenshot 2023-06-28 at 23 14 17

Remove feet from 尶 (U+5C36) and 筪 (U+ 7B6A) as circled.
Screenshot 2023-06-28 at 23 22 58

And finally remove feet from 爿 part of 匨 (U+5328) and 糚 (U+7CDA) as circled.
Screenshot 2023-06-28 at 23 22 38

EDIT: I have extra characters I found out of random while checking something.

@CoolMarvel43
Copy link
Author

CoolMarvel43 commented Oct 23, 2023

Just recently noticed two similar glyphs for 亞 (U+4E9E). The CN glyph already has the feet removed, so remove the JP glyph? Alternatively, remove the feet from the JP glyph and remove the CN glyph.

Screenshot 2023-10-23 at 18 25 36

Also either restore the v1 CN glyph for 亜 (U+4E9C) as per this issue, which I already mentioned there, to replace the JP glyph, or just remove the feet from the JP glyph.

Screenshot 2023-10-23 at 18 26 05

I will eventually consolidate all these posts into one table, so the previous posts might be amended or deleted, but no information will be lost as they will be transferred into one organized table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants