Marcus98T

Results 102 issues of Marcus98T

源樣黑體 v1.500 ![Annotation 2020-04-11 184520](https://user-images.githubusercontent.com/10541683/79042231-613ac900-7c28-11ea-9919-2a4ce792681e.png) 思源黑體 v2.001 ![Annotation 2020-04-11 184608](https://user-images.githubusercontent.com/10541683/79042232-61d35f80-7c28-11ea-8f06-affa4cfe287c.png) 上面的十字bug也包括源石黑體和源泉黑體。

question

䏕 > 改成思源宋體TW, 不是 JP (源樣黑體已經有TW字形) 諲 > 改成源ノ明朝JP v1.001, 不是 KR/TW

The two parts in the 吳 component seem to have minor gaps as circled in the picture. Please fix.

fixed-for-next-release

The 辶 radical looks weird and off-balanced. Please adjust to match TW/HK/JP/KR proportions, which are fine.

This is the Serif counterpart to these two issues on Sans, [one for TW/HK](https://github.com/adobe-fonts/source-han-sans/issues/313) and [one for JP](https://github.com/adobe-fonts/source-han-sans/issues/432). Yes, Source Han Serif fulfils the GB 18030 character set (and once...

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...

睷 (U+7777) and 綎 (U+7D8E) should be redesigned to include that axe detail in the last stroke of 廴. 羫 (U+7FAB) should be redesigned to follow the standard JP form...

**UPDATE:** Please see [this post](https://github.com/adobe-fonts/source-han-serif/issues/174#issuecomment-1527504953) for the definite list of restoring CN/TW glyphs. JP and KR posts will remain here for the time being. --- While checking the Japanese JIS...

I checked through the removed JP glyphs and a good amount of them are part of Adobe-Japan1-6. There were [some](https://github.com/adobe-fonts/source-han-serif/issues/169) [issues](https://github.com/adobe-fonts/source-han-serif/issues/158) reported before, and [I’ve reported some of them](https://github.com/adobe-fonts/source-han-serif/issues/174) as...

Applies to both Sans and Serif. I don't know why they made one extra similar glyph for HK when there is already a JP variant glyph that should suit HK....

fixed-for-next-release