Bopomofo graphs looks bad, unlike others. and…

[MY1L]

Being poor at English）检查的文件：CJKSymbols-Regular.otf 2.000

Bopomofo

比较形似的ム和ㄊ：

甚至是折线？

〜

〾也是：

我索性重画了一个给你（文件见下）

Suzhou Numerals

苏州码子〸〹〺字体不一致：

我改为一致，还修改了了其它几个字（文件见下，〥取自我2021年做的源意明体）

（with all due respect, SourceHanSerif’s 〥 & Bopomofo look so ugly.）

字形依据：

〦二〥〩

位于长城附近永久保存的青龙桥车站的里程碑视频（央视九台纪录片频道《创新中国》第6集 6分25秒左右，于2018-01-28截屏）：

致谢 钛白(@TaicEart)
他经过考据认为微软雅黑〦〧〨〩等字写法有误，且〡〢〣相遇时应变换方向。得知微软雅黑将更替字形时，在2016年11月就（于 Renzhi Li @be5invis 的微信群）提供了苏州码子无级字重黑体“TiSu”用于更替字形，并想对ISO\统一码提案。但更替微软雅黑计划中断，均不了了之，于是在2017年10月26日将 TiSu 免费发布。

（图为 TiSu-SemiBold，其中〩为草书形式，支持〡〢〣相遇时变换方向的特性）
我与 @NightFurySL2001 关于〩的提案受到 TaicEart 启发。

〡〢〣〤〥〦〧〨

Symbols for Chinese folk religion

🉠🉡🉢🉣🉤🉥也有类似的问题，直线上不应该有锚点，显得弯弯曲曲的：

恰好这个问题可以解决，我几年前就画了🉤这些字形，

3次曲线，OFL1.1的，目前有新版：https://github.com/MY1L/Unicode/releases/tag/Hani9

Font

除了Bopomofo，以上所有修改（〡〢〣〤〥〦〧〨〩〸〹〺〾🉠🉡🉢🉣🉤🉥）打包为笔画分离的otf：CJKSymbols.patch.zip

[kenlunde]

Thank you. Because representative glyph changes are involved for some of characters, this issue will be discussed during the UTC #178 meeting in January as document L2/23-281. I will let you know of the outcome after the meeting.

[NightFurySL2001]

Please sign this CLA to allow the Unicode consortium to use your updated glyph data.

请签署下面的贡献者许可协议，同意 Unicode联盟使用您的更新数据。
https://cla-assistant.io/unicode-org/.github

[kenlunde]

@MY1L Please respond to the request above.

[MY1L]

（几天前已经签过忘记回复了 / a few days ago I signed the CLA）

有件尴尬的事，我才想起我已经在2021年就相关议题在思源宋那边 @kenlunde 过：Suzhou numerals glyphs are still not redesigned; and 々,乄 needs to be redesigned in CN Subset, etc. adobe-fonts/source-han-serif#131
(由于我正在修改思源宋源文件，就不在这边提了 / a issue merely about SourceHanSerif, not here.)

[kenlunde]

@MY1L Thank you for signing the CLA. I have asked one of the administrators to confirm.

About the Source Han / Noto CJK repositories, I have not been involved in them for approximately 4.5 years ago.

[kenlunde]

One of the administrators confirmed that you signed the CLA. 谢谢!

[MY1L]

Can I add/revise some glyphs?
⿼⿽(￫)⿾⿿㇯〢〤〥〦〧〨〩〸〹〺々(change from SourceHanSerifVF, arrows are also variable)

[kenlunde]

This is not a variable font, so I do not see any benefit in such changes.

[MY1L]

updated, sample text: ⿼⿽⿾⿿㇯㇒㇣〢〤〦〥〧〨〩〸〹〺々(𠚤)

CJKSymbolsPatch2.zip

CJKSymbolsPatch2glyphs-SrcHanSe-Regular.otf — intended to Source
CJKSymbolsPatch2.ttf — intended to PDF

[kenlunde]

I can incorporate all of these minor glyph tweaks except for that of U+3005 々 IDEOGRAPHIC ITERATION MARK whose proposed glyph change deviates too much from common usage.

[kenlunde]

Closing per Version 2.001 release.

[MY1L]

i see 9c0aa17
table name { nameid 0

@kenlunde may i ask if it is possible to include my id in the list of contributors(nameid 0)?

[kenlunde]

I already thought about that, but including something like MY1L is a bit cryptic. This is the reason why it was not done. We prefer something that resembles the name of an actual person. Still, such a change, which is to the metadata, is not a reason to bump the version number and to make a new release, but if you can provide something that resembles the name of an actual person, I can make sure that it is included in the next version.

[MY1L]

I understand, but MYIL is indeed my vendor ID — there are may thousands of people with the duplication name as me (pinyin, without tone), so can't even find myself online by name…

how about “Yi Hu 'MY1L'”(sounds not well in Chinese) or “HU 'MY1L' Yi” or “'MY1L' Hu”?

[kenlunde]

How about putting MY1L in parentheses? In case Yi Hu (MY1L), which would follow the pattern of other names in the same name.id=0 string, does not sound well, I would suggest HU Yi (MY1L) instead.

[MY1L]

Okay..（btw, “MY1L” already includes my personalname(1=一→Yi≈Y1,wordplay😓), so, can be deduplication as “MY1L Hu”）

Oh, one more question —

https://www.unicode.org/charts/PDF/Unicode-16.0/U160-3000.pdf
https://www.unicode.org/charts/PDF/Unicode-16.0/U160-31C0.pdf

[kenlunde]

So, which attribution do you prefer?

Also, while the CJK Symbols font was developed to be used for the code charts of the Unicode Standard, the code charts editor ultimately decides for which code points to use the CJK Symbols font. This is why you observed what you did in the Unicode Version 16.0 Alpha code charts.

[MY1L]

MY1L Hu may be better (if allowed)

[kenlunde]

This will work. I will append MY1L Hu to the name.ID=0 string the next time the font is updated.