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: Fri Feb 28 12:49:10 CST 2025
ReportID: ID20250228124910
Name: Kenneth W Whistler
Report Type: Public Review Issue
Opt Subject: 520
This proposed draft suggests, among other things, that script-specific property names for Jurchen, Tangut, and Nushu be regularized, with the same kind of 4-character script prefix added to all of them, parallel to the way Unihan properties use a "CJK" prefix. In general, for completely new properties, as for Jurchen, this is fine. However, for the existing Tangut and Nushu data files, this is a very disruptive suggestion that would create discontinuities in the data and break tooling. In particular, the suggested changes for Tangut are very bad. The existing data uses kTGT_MergedSrc and kRSTUnicode. These are already unique identifiers, and despite the Tangut properties not yet formally being documented as UCD properties per se, they are already widely treated as extended UCD properties. Changing the identifiers would require the introduction of legacy aliases, create a discontinuity, and would break tooling in unicodetools, Unibook, and elsewhere. Less would break for the Nushu changes. But there is no need whatsoever to change kSrc_NushuDuben, which is already clearly identified and distinct. The only value deserving a potential change is kReading, which is too ambiguous. However, even for that one, given the fact that software exists that has already used that identifier, any new change would probably require keeping "kReading" around as a legacy alias, anyway, obviating the need for this change in the first place. I suggest all four of these Tangut and Nushu properties be simply reverted to what we have had in the files for years.
Feedback above this line has already been reviewed during UTC #183 in April, 2025.
Date/Time: Thur May 15 17:24:23 PDT 2025
ReportID: ID20250515172423
Name: Harriet Riddle
Report Type: Public Review Issue
Opt Subject: 520
WG2 N3297 (UTC L2/07-143) mentions a proposed UTR 43 "A User's Guide to the UniTangut Database" (this title is analogous to "A User's Guide to the Unihan Database" for PRI 97, which would become UAX 38). Although this appears never to have become a UTR or even a PRI, it is directly superseded by the proposed UAX 60 (UTC L2/25-109). Is the non-reüse of the number 43 for procedural reasons?