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

The 尤, 冘 and 无 components may need unification

Abierto
#322 1 comentario 1 reacción 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
17.2k
Forks
1.4k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

I suggest that we should unify the 尤 and 冘 components (with my preferred JP form where 丿 and 乚 touches) for all regions whenever possible, saving a bit of glyph space. There's nothing that says the 丿 and 乚 should not touch for CN/TW/HK locales. [This similar issue which I reported earlier for Serif](https://github.com/adobe-fonts/source-han-serif/issues/148) is separate for Source Han Sans to avoid confusion.

Screenshot 2022-01-14 at 04 03 48

Here are the characters to review:
冘抌帎沈忱妉枕眈衴耽紞酖躭訦鈂馾黆魫黕邥瓭鸩鴆髧沊醓
莐霃萙
尢尤优扰犹沋忧肬蚘紌訧鱿魷就駀疣嵆鑙諬嵇稽
莸就僦噈憱殧蹴鹫鷲蹵

Screenshot 2022-01-14 at 03 32 14

The v1 reference is from a Source Han Sans fork called GenYoGothic (源樣黑體 TW version) as I cannot install v1 and v2 at the same time. Glyphs are largely the same as v1 Sans, especially those which are removed v1 JP glyphs.

Screenshot 2022-01-14 at 03 46 53
Screenshot 2022-01-14 at 03 47 11

**LEGEND**
Green - the v1 glyph can be restored to replace all locales.
Blue - if possible, the v1 glyph may be restored to replace only the JP/KR/CN locales.
Red - the glyphs to be replaced by the v1 JP glyphs.
Orange - the glyphs to be adjusted, even those within the JP/KR locales, if ever so slightly.
Magenta/Pink - Replace with v2 JP/KR forms and remove existing glyph.
Light green - replace with HK form and adjust glyph.
White - no change needed.

For 尤, I did put the character through my font list and it appears that maybe it should be treated separately for the CN region, but how the 丿 and 乚 strokes are applied is still inconsistent, especially between Sans and Serif. I probably suggest we review first and whether conforming all these characters containing 尤 to JP forms is acceptable for the CN region, and please comment with concrete evidence to prove otherwise.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.