Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing U+82B1 "花" in the 2.000R CN Subset #147

Closed
3 tasks done
YommasCarreueul opened this issue Jan 8, 2022 · 2 comments
Closed
3 tasks done

Missing U+82B1 "花" in the 2.000R CN Subset #147

YommasCarreueul opened this issue Jan 8, 2022 · 2 comments

Comments

@YommasCarreueul
Copy link

YommasCarreueul commented Jan 8, 2022

Prerequisites

  • If you are reporting an issue that affects glyphs for characters for a particular region or regions, did you verify that the characters are within the supported scope of the region or regions? This generally means GB 18030 or Tōngyòng Guīfàn Hànzìbiǎo (通用规范汉字表) for China, Big Five or CNS 11643 Planes 1 & 2 for Taiwan, HKSCS-2016 for Hong Kong, the JIS standards for Japan, and KS X 1001 and KS X 1002 for Korea.
  • Did you thoroughly search the open and closed issues to avoid reporting a duplicate issue?
  • Did you go through the official font readme file to better understand the scope of the project, to include the Known Issues section at the very end?

Description

[Please provide here a thorough description of the issue, being sure to specify at least a Unicode code point if it affects a character or a particular glyph for a character. Including the character itself after the Unicode code point also helps, for visual reasons. Images with annotations that pinpoint the issue also help. If you are referencing standards, please keep in mind that they may have known or unknown errors. It is not necessary to provide CIDs.]

@YommasCarreueul YommasCarreueul changed the title Missing U+82B1 "花" Missing U+82B1 "花" in the 2.000R CN Subset Jan 8, 2022
@punchcutter
Copy link
Member

Same issue as #145 and #106 which has already been fixed for the next update.

@punchcutter
Copy link
Member

Fixed in 2.001

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants