This page is a compilation of formal public feedback received so far. See Feedback for further information on this issue, how to discuss it, and how to provide feedback.
Date/Time: Sun Sep 20 10:44:29 PT 2026
ReportID: ID20260920104429
Name: Ken Lunde
Report Type: PRI Feedback
Opt Subject: PRI 558 Feedback
Per the discussion record for IRG Working Set 2021 #00578 (aka UTC-03216), the kIRG_USource property value of U+2BAD5 should be changed from UTC-00561 to UTC-03216: https://hc.jsecs.org/irg/ws2021/app/index.php?id=00578 Its kTotalStrokes property value should also be changed from 13 to 14.
Date/Time: Thu Sep 24 04:57:59 PT 2026
ReportID: ID20260924045759
Name: Harriet Riddle
Report Type: PRI Feedback
Opt Subject: PRI 558
Some more candidates for potential kSpoofingVariant and/or kZVariant properties: U+5C22 ↔ U+21BC1 (especially their J-source glyphs) U+8A00 ↔ U+8A01; U+91D1 ↔ U+91D2 (trivial positional display forms from GB/T 12345, which includes them because GB/T 2312 includes nontrivial positional simplified forms). Note also that U+8A01's and U+91D2's `kCCCII` properties point to characters in a range of Kangxi radicals, with glyphs closer to U+8A00 (or U+2F94) and U+91D1 (or U+2FA6). U+98DF ↔ U+98E0 ↔ U+2967F (UCV #358). Also, the same consideration with U+98E0's`kCCCII` value as above. U+21E8F ↔ U+2DB4D U+25A3F ↔ U+32ABD U+9FBA ↔ U+2099D; U+470C ↔ U+9FBB (trivial positional forms from GBK 1.0, discussed in ISO 10646 Annex P) U+9FB9 ↔ U+20509 (UCV #26; also, mentioned in ISO 10646 Annex P along with the two pairs above) (Sidenote: it came to my attention while writing this up that U+9FB9 is rendered in "AR PL UMing CN", as provided e.g. by the Debian/Ubuntu package "fonts-arphic-uming", with a glyph closer to U+215D7, which it also includes with a very similar glyph; it doesn't include a glyph for U+20509. This is primarily a font issue (considering the closest UCV would be #188b, which isn't close), but may or may not impact pragmatic spoofing-variant considerations.) --- The table for `kIRG_GSource` still mentions Singapore in the paragraph before the list of prefixes, even though the only prefix related to Singapore is no longer included in that list due to the introduction of the separate `kIRG_SGSource` property. --- The description for the `kHangul` property could be expanded to cross-reference the `kKoreanEducationHanja` and `kKoreanName` properties as corresponding to its "E" and "N" source specifiers respectively (compare how the description for the `kCantonese` property names the Unihan properties corresponding to the sources which it cites). --- Section 2.1.1 mentions `kTotalStrokes` as one of the Unihan properties which `Equivalent_Unified_Ideograph` can be used to apply to non-CJKUI characters. However, for example, the total-stroke count for U+2ECF (i.e. 2 or 3) is very different from that of its `Equivalent_Unified_Ideograph` U+9091 (i.e. 7, as correctly reflected by its `kTotalStrokes` property value).