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

About 亙 component

Abierto
#315 0 comentarios 0 reacciones 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

For 亙 component in TW/HK, I raise the following concerns:
1. there is no mention about the two dots inside 亙 should touch the left stroke or not in Taiwan MOE style. (P/S: it do mention the second stroke should be a 撇, not a 竪; this is debatable as even TW-Sung itself make this as a 竪)
![image](https://user-images.githubusercontent.com/33471049/140028414-48000946-e1ef-4ccb-ad22-07386dbae230.png)
Source: https://language.moe.gov.tw/001/Upload/files/SITE_CONTENT/M0001/BIAU/f46.htm?open
2. some of the touching strokes is tolerable in Hong Kong educational style. 亙 is not explicitly stated as tolerable in the examples, however it is also not compared to TW glyph in the following section as a point of difference in Reference Glyphs for Chinese Computer Systems in Hong Kong (thus assuming HK and TW are the same).

Source Han Sans separated most of TW/HK pairs from JP/CN which is touching the left side of the glyph. However, the character 亙 itself in TW is left mapped to CN. (there is also one glyph from JP that use the style too)
![image](https://user-images.githubusercontent.com/33471049/140030045-75521b21-7c97-4b30-8101-3de2edd88412.png)

Since the requirement is not present as a differentiable style in any of the TW/HK standard, I would propose to remove current TW/HK glyph and see as a unifiable component. Otherwise, it might require 亙 to map from HK to TW. Chiron Sans also map all related glyphs to the CN style.

I would like to ask @hfhchan and @tamcy to comment on this issue.

Guía de contribución

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

Línea de trabajo

Review the cited Taiwan MOE and Hong Kong educational-style references, along with the linked glyph comparison images, to establish whether 亙 has a distinct TW/HK requirement. Resolve the regional mapping question with the requested maintainers; done requires an agreed decision on retaining, removing, or remapping the current TW/HK glyph.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Área
design, internationalization
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
20/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.