adobe-fonts / adobe-fonts/source-han-sans
Updating TW glyph shape to CNS11643 Amendment 1
- Vorherrschende Sprache
- Python
- Sterne
- 17.2k
- Forks
- 1.4k
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
There is a recent update for CNS11643 as shown on the CNS site (https://www.cnsonline.com.tw/?node=detail&generalno=11643&locale=zh_TW). The main changes in this amendment, apart from newly added glyphs, is 35 glyph changes and 1 new glyph addition to CNS Plane 1 and 2. This is also reflected in the [IRGN2586 document](https://appsrv.cse.cuhk.edu.hk/~irg/irg/irg59/IRGN2586_21TglyphsUpdatedand4HorizontalExtension.pdf)
Some of the changes are already implemented in Source Han as it affects cross-regional communication (e.g. U+5DD5 巕 in #169, 嬔/嬔 and 礡/礴 pair) or doesn't match the rest of the characters (e.g. 踴、謄、璽). Others however need to be corrected in accordance to the original [Regular script font sample (國字標準字體楷書母稿)](https://language.moe.gov.tw/001/Upload/files/SITE_CONTENT/M0001/mu/f5.html).
Also noted is a few of the glyph updates doesn't seem to change anything significant, such as 罕滘 (top 儿 lightly touch the roof 冖, separated in Sans)、承 (right side cross out)、汩 (made wider)、檶 (structure change)、迗 (stroke touching). The rest will need either glyph editing or remapping. A few glyphs can be removed completely while others are added. The full document can be viewed on the CNS site by searching for "11643" and click on the "補充增修及勘誤表"; the PDF is also attached below the image.


[CNS11643-20230420Corri.pdf](https://github.com/adobe-fonts/source-han-sans/files/12321975/CNS11643-20230420Corri.pdf)
I believe the TW glyph for 承 can be totally removed and map to CN in Sans and JP in Serif. HK standard does not specify this is a significant difference and an exception could be considered under this rule of insignificant differences in _Reference Glyphs for Chinese Computer Systems in Hong Kong_.


Also see #340 for 掰 (HK).
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.