Error in mapping for U+3D1D 㴝 and U+2A3ED 𪏭 in HK

[S-Asakoto]

It seems that the glyphs for U+3D1D 㴝 and U+2A3ED 𪏭 are kind of mixed up in HK locale, while in other locales the mapping is correct.

And for some reason when displaying in Chrome the mappings change again, having correct mapping for U+2A3ED but identical shape for U+3D1D

[tamcy]

First, the font's cmap of v2.004 shows that both U+3D1D 㴝 and U+2A3ED 𪏭 are mapped to u2A3ED-HK for HK for v2.004.

In my testing, the two codepoints appear as ⿱利𱥯 in both the CJK and subset configurations for HK. This aligns with the cmap, and no swapping has occurred. I suggest you to supply your version and configuration for a better investigation after confirming the HK glyph in your report is really a U+2A3ED.

Second, the background of U+3D1D and U+2A3ED in HKSCS is best explained in this document:

---

So it is very possible that both Source Han Sans and Serif decided to keep the original HK form of ⿱利𱥯 in U+3D1D in the HK version for backward compatibility.

[S-Asakoto]

Thanks for the info, will close the issue.