Consolidation of Glyph Correction Suggestions #39
Comments
|
|
|
|
|
|
|
|
|
U+76E4 盤 will be handled by adding a new CN glyph, uni76E4-CN (see Issue #40). |
|
U+7A07 稇: Second last stroke should be a dot instead of 捺. |
|
Add CN glyph for U+7A07 稇, uni7A07-CN (see Issue #40). |
|
|
|
Nice catch. Thanks. Noted. Although this particular glyph is a candidate for removal for Version 2.000, we'll go ahead and fix it for the Version 1.000 dot-release. |
|
For the whole lot of characters containing 廷, Source Han Serif has unified the shapes of the CN and TW in error. Excerpt: According to Tongyong Guifan Hanzi Biao, the second horizontal stroke should be the longest, while for MOE Standard Song, the second horizontal stroke should be the shortest. The length of the second stroke was a point of contention as it was inconsistently printed as the shortest stroke in various standards preceding Tongyong Guifan Hanzi Biao. Affected characters include at least U+5EF7, U+4FB9, U+5A17, U+5EAD, U+633A, U+6883, U+6D8F, U+70F6, U+73FD, U+7B73, U+7D8E, U+8121, U+8247, U+839B, U+8713, U+8A94, U+92CC, U+94E4, U+95AE, U+9706, U+9832, U+988B, U+9F2E, U+3E76, U+414D, U+4A60, U+4BD5 and U+4C53. (As a side note, the Code Charts should probably be updated to use the fonts for Tongyong Guifan Hanzi Biao instead.) |
|
For U+63EF, the second stroke of the right-most component of the CN, TW and KR glyph should be a slanted 豎, not 撇. |
|
|
|
@hfhchan: U+63EF 揯 will be handled by adding a new CN glyph, uni63EF-CN (and its JP glyph, uni63EF-JP, is targeted for removal), and the TW glyph for U+83E1 菡, uni83E1-TW, will be adjusted. |
|
@hfhchan: I am going through the CN and TW glyphs for the characters that include the shared 廷 component, and the current CN and TW glyphs for three of the 28 that you referenced above—U+7B73 筳, U+839B 莛, and U+9706 霆—appear to be okay as-is:
|
|
@kenlunde Yes, these three examples are fine. I must have copied the wrong string. |
|
With regard to the other 25 characters, I finished my analysis and action plan. The CN glyphs for the following 22 characters will be adjusted: U+3E76 㹶, U+414D 䅍, U+4A60 䩠, U+4BD5 䯕, U+4C53 䱓, U+5A17 娗, U+5EAD 庭, U+5EF7 廷, U+633A 挺, U+6883 梃, U+6D8F 涏, U+70F6 烶, U+73FD 珽, U+7D8E 綎, U+8121 脡, U+8247 艇, U+8713 蜓, U+8A94 誔, U+92CC 鋌, U+94E4 铤, U+95AE 閮, and U+9F2E 鼮. New TW glyphs for the following two characters will be added: U+4FB9 侹 and U+9832 頲. New TW glyphs for the following 10 characters will be added by using the current (Version 1.000) CN glyphs as-is: U+5EAD 庭, U+5EF7 廷, U+633A 挺, U+6883 梃, U+6D8F 涏, U+73FD 珽, U+7D8E 綎, U+8713 蜓, U+92CC 鋌, and U+95AE 閮. The CN glyph for U+988B 颋, which is specific to CN, looks okay as-is. |
|
The strokes of 刀 component in 癩 U+7669 of JP/KR version (CID 28287) aren't aligned properly in Heavy weight.
|
|
@tamcy: Thank you for finding and reporting this. To clarify, this is an Adobe-designed JP glyph that corresponds to Adobe-Japan1-6 CID+5777, and the affected weights are SemiBold through Heavy. |
|
|
wow, yes! i try that on【Noto Serif CJK JP/KR】, they are perfect! i notice that【Microsoft YaHei UI】had already fix this issues from 【微软雅黑】,
in Chinese, double quotes are used 99%, and single quotes only 1%. even when we start a paper work, an A4 paper work, in the end, we use a Latin font (like Times New Roman) to "flash" the whole words to make the punctuation marks tight close to 汉字(Chinese character) and match the same style with numbers. so, what i want to say is that don't worry about the single qutoes, and even the whole Punctuation marks, caz we don't use them at all (thanks to microsoft) on papers. but we had to read them on screen, and that we can't edit. |
|
@opumps |
|
@kenlunde |
|
While I prefer to stop the discussion about the smart/curly quotes in this issue, please see L2/17-056, which is my preliminary proposal to use SVSes to handle these and similar characters. If you have any meaningful or constructive feedback, please send it to me offline (aka via email). |
|
There is a bug in the heaviest master of the JP/KR glyph of U+5D1E（崞）. Intermediate weights are affected. |
|
Noted, and thank you. I also noted that this particular glyph, uni5D1E-JP, is slated for removal in Version 2.000 in order to make room for HK glyphs. |
In Simplified Chinese, U+00B7 usually has a full-width form in practice; however, in theory it should be half-width according to GB/T 15834-2011, see the following figure. (Ironically, U+00B7 in GB/T 15834-2011 itself is NOT half-width.) Fortunately, GB/T 15834-2011 is NOT a compulsory standard ("GB/T" means that this is a recommendatory standard, T = 推荐 (Tuījiàn)).
|
|
@Man-Ting-Fang: I have been thinking about U+00B7 recently, in my attempt to revise L2/17-056 by splitting it into two separate (and revised) proposals, and I think that the best way to address this issue for both the Simplified Chinese and Traditional Chinese fonts is to map U+00B7 to the glyph for U+30FB ・, uni30FB, which functions in a similar way, and I see no reason why the glyphs cannot be shared for the Source Han families. |
|
The JP/KR glyph of 魢(U+9B62, ⿰魚己) is ⿰魚巳, which is the exact composition of U+29D57 𩵗. U+29D57 isn't covered by SHS, while U+9B62 doesn't have a JP/KR source in the code chart. Not sure if this is an issue, I'm reporting it here anyway. |
|
@tamcy: The good news is that the JP glyph for U+9B62 魢, uni9B62-JP, is slated for removal as part of the Version 2.000 update in order to make room for a large number of incoming HK glyphs, which means that this is likely to become a non-issue. |
|
I'd like to comment about the uni9FE6-TW. The version 1.001 is like this: [英微] It should be 一ル instead of 一几 for Taiwan/Hong Kong writing convention. The last stroke [英微] should be like this: Please take reference the design of 兀 in the 微 of the above image, thank you. |
|
GB/T 22321.1-2018 信息技术 中文编码字符集 汉字48点阵字型 第1部分：宋体 应该是中国大陆第一个包含CJK-C/D/E字符的字形标准 |
|
@CNMan I suspect that the Extension C, D, and E additions are to support 通用规范汉字表, which includes 44 Extension C characters, eight Extension D characters, and 108 Extension E characters. The Source Han typefaces already support 通用规范汉字表 in its entirety. |
|
I recommend against relying on that standard, because the standard was published before the new GB18030 checking efforts were finalized, and so do not incorporate proper normalization of the C/D/E glyphs, nor corrections to existing URO/AB glyphs. |
|
卩 (U+5369) should be center-aligned (the glyph is inclined to the right, same for for Source Han Sans 1.x). |
|
@tamcy Don't hold your breath for this one, particularly for Source Han Sans Version 2.000. Fixing it in Source Han Serif is now on the radar. |
|
@tamcy To clarify, the glyph for U+5369 卩 should basically be identical to that of U+536A 卪, but without the center dot, right? |
|
Yes, this is what I meant, at least for HK. But after some digging I'm not very sure about the CN form. Here're some more information for your reference: 卩 U+5369 is a CJK Unified Ideograph. Source Han Sans/Serif supports it as an HK and probably a CN character (not 100% sure about the latter). Here's what the Unicode chart shows:
And here's what the HKSCS document shows:
So I have confidence that it should be center aligned, or its form should look like 卪 without the dot as you have said. This makes sense as 卪 and 卩 are essentially the ancient form of 節, so there's no reason for 卩 as a word to not align to the center. Also "⼙" as a radical is encoded differently (U+2F19, but it's also appear center-aligned in the chart). But for the CN glyph, I do found the "right-aligned" form on the Unihan website and some other websites:
I suppose the latest Unicode chart is more authoritive? |
|
@CNMan I don't trust any one standard, and given that most standards, including older GB ones (a good example is GB/T 12345-1990), center the representative glyph for U+5369 卩, doing so makes the most sense. And, given that this glyph serves double-duty as a Kangxi Radical (U+2F19 ⼙), it makes for it to be centered in the em-box. |
|
@extc With regard to the Traditional Chinese (TW and HK) glyph for U+9FE6 鿦, uni9FE6-HK, it will be good in Source Han Sans Version 2.000. I made a note to fix the Source Han Serif glyph in the next update, which is likely to be Version 2.000. |
|
I think the JP/KR glyph for 这 would look better, and more consistent with other characters if it utilized a 長點 instead of a 捺 for the last stroke of 文. (Rough mockup at the bottom)
|
|
@lapomme This may or may not be good news, but this issue is likely to become a no-op, because the JP glyph for U+8FD9 这, uni8FD9-JP, is flagged for removal in Version 2.000, in order to make room for a large number of new HK glyphs. |
|
|
|
|
|
@tamcy @stone-zeng I’m shocked too for these problems, they looks just like how Rolls-Royce products the oil pipe to make engine explosion on Quantas Flight 32. |
This issue is meant for tracking and submitting suggestions for glyph corrections. Issues that were submitted before this consolidation issue was opened are referenced by issue number.
The following changes were made in Version 1.001:
Post Version 1.001 Fixes:
The text was updated successfully, but these errors were encountered: