adobe-fonts / adobe-fonts/source-han-sans

Unnecessary differentiation for the component 又

Offen
#563 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
17.2k
Forks
1.4k
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

I know there are tons of issues on glyph unifications and differentiations, but this one is extremely obvious and easy to solve. It is so absurd that I have no idea why Adobe did not realize it before releasing the font.

Currently, the component 又 has two forms: the open form used in JP/KR and the closed form used mainly in CN/HK/TW but also in JP/KR sometimes.

Image

The two forms can be unified for several reasons.

Firstly, the standard glyphs in all regions show the closed form:

Image

Image

And the open form is also acceptable for CN, especially for bold fonts, Microsoft YaHei Bold as an example:

Image

I am not sure whether the open form is acceptable for TW and HK, but the closed form is definitely acceptable for all regions.

In addition, there are characters where both CN and JP use the closed form, such as U+53CC 双 (the simplified form of 雙 used in both mainland China and Japan) and U+53CB 友, so current JP glyphs are not consistent:

Image

Image

Finally, Serif uses the closed form for all regions:

Image

To choose one from the two forms to be used, I personally prefer the closed form, since it is used more widely in the current version, and is consistent with Serif.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.