[v2.002] Some minor issues with the font
Marcus98T opened this issue · comments
Well @punchcutter is kindly asking me to keep all the issues organised into one place, so I'll just repost here. I was rushing to report issues when I simply do not understand how the development process and schedule between Noto CJK and Source Han is like.
At the time of writing these issues, Noto Serif CJK v2.002 was released a day before Source Han Serif, which was why I prematurely posted them there. Now that Source Han Serif v2.002 has been released, I should have just kept my issues here. I need to learn some patience and don't expect everything to go my way.
Anyway, here are the early issues I found with this font:
uni9FEE-JP (鿮) is using an inappropriate CN Song-style decoration in the top part of the 帯 component
Original closed issue: notofonts/noto-cjk#254
I have a design issue with uni9FEE-JP (鿮). This CN Song-style decoration as circled in red is inappropriate for Japanese traditional print orthography. I think Arphic designed this, when they are normally responsible for designing Chinese glyphs only, not Japanese. Anyway, please follow the reference of 帯 (U+5E2F, circled in green) and fix this glyph.
Also maybe fix the bottom part of 帯 by separating the 巾 component from the 冖 component.
[Release Notes Only] Duplicate mention of the TW/HK 全 mappings in the v2.002 release notes
Original closed issue: notofonts/noto-cjk#255
I have a minor issue in the release notes for Noto CJK Serif v2.002 regarding this line:
- Fixed TW/HK mappings for U+5168 全, U+6D24 洤, U+8DE7 跧, U+8F07 輇, and U+9293 銓 per Issue #109.
This was already fixed in v2.001, so there's no need to mention this line in v2.002. Probably it's here due to human error.
UPDATE: Also applies to the main branch.
Wrong HK mapping for 書 (U+66F8)
I mentioned this before, but anyway, I'll repost it here for organisational purposes.
I don't know what's going on here, but I think the HK glyph got remapped to the regular JP glyph of uni66F8-JP, not the JP variant glyph of uni66F8uE0101-JP as I requested. Please fix the mapping, but do not revert back to uni66F8-HK, as that glyph should be orphaned and removed in the next major version of Serif.
This project seems to not get the attention it deserves nowadays, without Ken Lunde, who again, was the only person to at least inform us of any changes and fixes beforehand. There are so many issues left unsolved.
At least if Adobe decides not to address them, they should say so and close them as not planned, not keep it open forever. After this release, they need to look through every single issue that's still open again. We need better communication regarding this.
Regarding uni9FEE-JP (鿮) there is another minor problem. While the glyph is interpolatable, there's a double node as circled (marked in red in the Glyphs app), which means there are two points on the exact same coordinates. Maybe in the next update, this double node needs to be resolved.
EDIT: I retract this statement.
@Marcus98T The component was designed this way to prevent overshoot for overlapped strokes during interpolation. All glyphs with the same component will exhibit the same behavior AFAIK.
I see. Well it's just hard for me to understand how Arphic (or other type foundries) designed the Chinese characters with their smart stroke technology in some proprietary font software, but anyway, it's not the point here.
Well if those strokes are designed that way as a just-in-case scenario, then there’s nothing we can do about it. I have struck out my previous comment if it means a waste of time “fixing” those duplicate points, but my initial comments about the inappropriate CN-style decorations will still stand.