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

Consolidation of Character/Glyph Addition Suggestions #40

Open
kenlunde opened this issue Apr 11, 2017 · 14 comments
Open

Consolidation of Character/Glyph Addition Suggestions #40

kenlunde opened this issue Apr 11, 2017 · 14 comments
Assignees

Comments

@kenlunde
Copy link
Contributor

kenlunde commented Apr 11, 2017

This issue is meant for tracking and submitting suggestions for character/glyph additions, meaning characters that are within the scope of coverage that are not yet supported, or that a supported character lacks an appropriate glyph for a supported language or region.

Special Note: If a character falls outside of a supported standard, meaning GB 18030 for China, Big Five for Taiwan, JIS (X 0208, X 0213, and X 0212) for Japan, or KS (X 1001 or X 1002) for Korea, please refrain from making a suggestion at this time. We need to make sure that support for these standards is adequate before we start to expand the scope of character/glyph coverage.

Issues that were submitted before this consolidation issue was opened are referenced by issue number.

The following glyphs were added in Version 1.001:

  • Added CN glyphs for U+35EB 㗫, U+385C 㡜, U+5015 倕, U+618F 憏, U+63EF 揯, U+6456 摖, U+6660 晠, U+66A9 暩, U+68B1 梱, U+6F08 漈, U+78DC 磜, U+7A44 穄, U+92EE 鋮, U+969B 際, U+9BCE 鯎, and U+9C36 鰶, uni35EB-CN, uni385C-CN, uni5015-CN, uni618F-CN, uni63EF-CN, uni6456-CN, uni6660-CN, uni66A9-CN, uni68B1-CN, uni6F08-CN, uni78DC-CN, uni7A44-CN, uni92EE-CN, uni969B-CN, uni9BCE-CN, and uni9C36-CN, respectively, per Issue Consolidation of Glyph Correction Suggestions (See Issue #39) #27.
  • Added CN glyph for U+7808 砈, uni7808-CN, per Issue Consolidation of Glyph Redesign Suggestions #36.
  • Added TW glyphs for U+4FB9 侹, U+5EAD 庭, U+5EF7 廷, U+633A 挺, U+6883 梃, U+6D8F 涏, U+6DEB 淫, U+73FD 珽, U+7D8E 綎, U+7F54 罔, U+8713 蜓, U+8DA3 趣, U+92CC 鋌, U+95AE 閮, and U+9832 頲, uni4FB9-TW, uni5EAD-TW, uni5EF7-TW, uni633A-TW, uni6883-TW, uni6D8F-TW, uni6DEB-TW, uni73FD-TW, uni7D8E-TW, uni7F54-TW, uni8713-TW, uni8DA3-TW, uni92CC-TW, uni95AE-TW, and uni9832-TW, respectively, per Issue Consolidation of Glyph Correction Suggestions #39.
  • Added CN glyph for U+76E4 盤 and U+7A07 稇, uni76E4-CN and uni7A07-CN, respectively, per Issue Consolidation of Glyph Correction Suggestions #39.
  • Added CN glyphs for U+57F5 埵, U+7BA0 箠, U+83D9 菙, and U+9318 錘, uni57F5-CN, uni7BA0-CN, uni83D9-CN, and uni9318-CN, respectively.

Post Version 1.001 Additions:

Version 2.000 Additions:

@hfhchan
Copy link

hfhchan commented Apr 17, 2017

image
U+7BA0: The last stroke needs to be shorter than the stroke above it for CN.

@kenlunde
Copy link
Contributor Author

Noted as a new CN glyph for U+7BA0 箠, uni7BA0-CN.

@hfhchan
Copy link

hfhchan commented Apr 22, 2017

image

Add CN glyph for U+5015, the last stroke should be shorter.
Add CN glyph for U+57F5, the last stroke should be shorter.
Add CN glyph for U+83D9, the last stroke should be shorter.
Add CN glyph for U+9318, the last stroke should be shorter.

@kenlunde
Copy link
Contributor Author

@hfhchan: You reported the U+5015 倕 issue 12 days ago in Issue #27. Adding new CN glyphs for U+57F5 埵, U+83D9 菙, and U+9318 錘 has been noted above.

@kenlunde
Copy link
Contributor Author

The image below shows the glyphs for the CN and TW ideographs that we are adding:

shserif-added-28

@kenlunde
Copy link
Contributor Author

Not shown above are ten additional TW glyphs that were originally CN glyphs, and the original CN have been updated.

@extc
Copy link

extc commented Jul 6, 2018

Will the CJK Basic newly introduced in Unicode 11.0 be included in the Source Han Serif ver 2.0?
image

@kenlunde
Copy link
Contributor Author

kenlunde commented Jul 6, 2018

@extc Affirmative.

@CNMan
Copy link

CNMan commented Sep 23, 2018

关于对《信息技术 中文编码字符集》国家标准(征求意见稿)征求意见的函

1、信息技术 中文编码字符集(征求意见稿)

在四字节编码0x82358F33—0x82359636 部分增加了CJK 统一汉字增加的66 个汉字;

2、信息技术 中文编码字符集(征求意见稿)编制说明

九、标准性质的建议
本标准上一版是当前使用中最重要的中文编码字符集,是我国全社会汉字信息处理能力的基本保障,经2017年国家标准化管理委员会清理整顿强制性国家标准后仍然保持了强制性质。因此,建议本标准在本次修订后仍然作为条文强制性国家标准发布。对于一般具有文字处理功能的信息技术产品,强制范围与上一版一致,即单字节编码部分、双字节编码部分和从GB 13000(或ISO/IEC 10646)引入的“CJK统一汉字”及其扩充A。

据此,应增加U+9FD0~U+9FEF。

@eisoch
Copy link

eisoch commented Sep 23, 2018

@CNMan The new version of GB 18030 has not been released at final and China (CESI) had mentioned it for several times in IRG. U+9FD0 to U+9FEA have been included in the current version, and U+9FF0 to U+9FF6 will be included in Unicode, 13.0.0 or future, but there will be no chance to include them into the nearest new version of GB 18030. SHS should add them all the characters in URO+ to the future version.
CC @kenlunde

@kenlunde
Copy link
Contributor Author

@eisoch There is no need to explicitly CC me, as I receive all notifications as the owner of the _Source Han_repositories.

Source Han Sans Version 2.000 will include glyphs for URO ideographs up through U+9FEF. Source Han Serif Version 2.000 is not likely until early 2020 due to the scope of its work. As you stated, U+9FF0 through U+9FF6 are targeted for Unicode Version 13.0.

Anyway, I am hoping to get an update about GB 18030 from China during IRG51 next month. Once posted, their Activity Report (aka IRG N2317) should have the details.

@Marcus98T
Copy link

Marcus98T commented Jan 2, 2019

Should add CN glyph for 壓. Source Han Sans 2.000 has one where 厂 covers 土, like ⿸ rather than ⿱厭土.

screen shot 2019-01-02 at 18 44 01

@Marcus98T
Copy link

Marcus98T commented Apr 10, 2019

By the way, I hope you take my above comment under advisement. I have not seen any amendments to the post v1.001 or v2 notes regarding adding the CN version of 壓, since it is present in Source Han Sans SC v2, but not Serif SC which is now being pointed out below, along with the G-source found in Unicode CJK Ideographs PDF.
Screen Shot 2019-04-10 at 23 37 26
Screen Shot 2019-04-10 at 23 49 46

@ashprice
Copy link

Apologies if this is the wrong place to ask this, but are there any immediate plans to include the Unicode Block CJK Unified Ideographs Extension B, U+20000 - 2A6DF in upcoming versions? I am guessing not given my understanding of the standards given above, but my understanding of these things isn't very good (if you have some reading I can do, let me know).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants