punchcutter
commented
2 years ago Yes, we are still planning to address issues that were marked for post 1.001 and didn't get addressed yet. If any issues fixed in v1.001 got reverted then that wasn't intentional, but with the large number of files and a completely redesigned build workflow it's not too surprising if some things slipped through. Please open issue for any of those so I can check where things went wrong.
I would very much like to get away from the long consolidated issues, but when addressing common factors it makes sense. I plan to update the templates to hopefully make it a little easier to start an issue specifically addressing mapping, glyph correction, glyph addition, etc.
tamcy
First off, I want to thank you guys for the release of Source Han Serif 2.0. With the inlcusion of HKSCS codepoints the font is much more usable in Hong Kong.
As v2.000 is a big update, I would like to know if you are still in the middle of handling the opening issues original planned for v2.000 because I spot some unfixed issues originally targeted for post-v1.001, and some issues fixed in v1.001 got reverted. If yes I won't bother raising them again.
And would you like us to report glyph mapping/design issues separately (one issue per codepoint or codepoints with common factors, like this issue contains bugs about characters with a 倉 component), or consolidate them in a single thread (until they are closed by your side)?
Going back to the topic, the third stroke of the component 倉 for should be a horizontal line for JP, KR, TW and HK. This is different from CN which is a dot. Follow screenshot shows a correct example:
But the following 13 characters are incorrectly mapped to the CN glyph:
I mainly check for issues against the new HK region, but this issue also affects TW. Here is the proposed fix: