You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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, JIS X 0208, JIS X 0212, and JIS X 0213 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
On Chrome, 𧪄 (U+27A84) for CN locale (zh, zh-CN, zh-Hans) seems to be using the JP glyph.
Although 𧪄 is out of scope for CN, it is within the supported scope of HK (it is in HKSCS) and the HK glyph seems more consistent with CN conventions. As a result I suggest using HK glyph for CN locale as well.
Attached is 𧪄 shown in different locales, with 造 as a reference to prove that the correct locale is chosen.
Unicode reference:
The text was updated successfully, but these errors were encountered:
Prerequisites
Description
On Chrome, 𧪄 (U+27A84) for CN locale (zh, zh-CN, zh-Hans) seems to be using the JP glyph.
Although 𧪄 is out of scope for CN, it is within the supported scope of HK (it is in HKSCS) and the HK glyph seems more consistent with CN conventions. As a result I suggest using HK glyph for CN locale as well.
Attached is 𧪄 shown in different locales, with 造 as a reference to prove that the correct locale is chosen.
Unicode reference:
The text was updated successfully, but these errors were encountered: