Mapping suggestion for 𧪄 (U+27A84) & 5 more characters for CN locale (updated 2025.2.21)

[S-Asakoto]

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, 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:

[S-Asakoto]

Similar issue for 𨸶 (U+28E36) as well. Probably more but it takes time to check for all candidates, possibly Ext-B characters that are in HKSCS and JIS X 0213 but out of scope for CN. and four more, shown in the next image. Characters in red are those differing significantly from CN conventions.

[NightFurySL2001]

Here is a quick filter where CN ≠ HK with problematics one listed. Action to take as follow.

CN remap to HK: 𠂊 𠘑 𠹭 𢹂 𣳾 𥧌 𦐂 𦥑 𧪄 𨥉 𨨩 𨸶 𪊲
Unknown: 𦉪𦍌𧄍慈
Unchanged: 𡌶𡐓𥻘 (㐄 in 𥻘 should be separated in CN usually)
Error: TW remap to CN: 𥕢

Some evidences from GB18030: