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

Distinguish 市 (U+5E02) from 巿 (U+5DFF) along with similar characters containing the former component (JP only) #418

Open
Marcus98T opened this issue May 6, 2023 · 0 comments

Comments

@Marcus98T
Copy link

Marcus98T commented May 6, 2023

There can be confusion if the top vertical stroke looks like it's connected to the bottom vertical stroke in 市 (U+5E02), making it look like 巿 (U+5DFF). These two characters are etymologically different, and therefore a distinction must be made between these two characters for the JP/KR locale. There's even an additional etymological character called 𣎵 (U+233B5, not in Source Han Sans/Serif), for which the component is likely to follow 巿 (U+5DFF), not 市 (U+5E02).

Screenshot 2023-07-16 at 22 43 12
EDIT: Graphic provided for U+233B5 (set in BabelStone Han) because all the default CJK fonts don't support this character.

Screenshot 2023-05-06 at 16 12 40

I understand that Kozuka Gothic has the distinction (left character, circled), but because of the placement of the bottom vertical stroke, it may not be obvious. Unfortunately this means its open source derivative Source Han Sans, with the "gothic serifs" removed, makes it look like 巿 (U+5DFF).

Screenshot 2023-05-06 at 16 14 06

To distinguish 市 (U+5E02) from 巿 (U+5DFF), please separate the two vertical strokes in 市 (U+5E02), similar to how Chiukong Gothic (a fork of Source Han Sans) did it as pictured.

Screenshot 2023-05-06 at 16 08 55

And here are the affected glyphs, separated by etymology. The ones in dark grey are outside Adobe-Japan1, so they can be ignored.

Screenshot 2023-05-06 at 16 35 43

So please adjust the glyphs for 市 (U+5E02), 鬧 (U+9B27), 姉 (U+59C9) and 鈰 (U+9230), all marked in yellow.

For 肺 (U+80BA, in orange), the JP locale has 市 (U+5E02), which is etymologically incorrect. However, the two vertical strokes in 市 (U+5E02) does not meet, so it's technically correct. Meanwhile, the KR locale (and subsequently CN, TW and HK) has the two vertical strokes connected as one, which is etymologically correct.

But Adobe-Japan1 is not etymologically correct, so it should probably update the glyph reference to ⿰月巿, not ⿰月市, then the JP glyph can be removed. Unfortunately virtually all Japanese fonts follow ⿰月市, so the damage is already done.


For Serif, I request some minor adjustments to make the spacing look consistent.

Screenshot 2023-05-06 at 16 45 07

Adjust 市 (U+5E02), 姉 (U+59C9) and 柿 (U+67FF) to move the bottom vertical stroke slightly downwards, so it matches 鬧 (U+9B27) and 鈰 (U+9230).

However, similar with 肺 (U+80BA), 伂 (U+4F02) is not etymologically correct on Adobe-Japan1, it should basically be ⿰亻巿, not ⿰亻市. If Adobe decides to follow etymology, the glyph must be adjusted to make the vertical stroke connect all the way, which means removing the middle serif decoration as circled.

Screenshot 2023-05-06 at 16 58 55

Unfortunately CN, TW and HK is also mapped to JP, which means the character still looks like ⿰亻市 with traditional orthography which is fundamentally incorrect, but if we can adjust 伂 to follow etymology, then it will be fine.

Here are the commercial fonts with the 𣎵 component compared to i.Ming (which claims to follow etymology, thus the name Inherited Glyphs), only 杮 (U+676E) and 旆 (U+65C6) are etymologically correct. Only YuGothic and YuMincho got 伂 (U+4F02) correct, the rest are all etymologically wrong.
Screenshot 2023-05-06 at 17 12 11

And while Source Han Serif did get 沛 (U+6C9B) correct, Kozuka Mincho and consequently the rest of the Japanese fonts got it wrong. Thus Adobe-Japan1 needs to update the glyph reference for 沛 (U+6C9B) to ⿰氵巿, likewise for 肺 (U+80BA) and 伂 (U+4F02).

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

1 participant