On Sun, Feb 9, 2025 at 6:04 PM John C Klensin <john-ietf@xxxxxxx> wrote:
I think a recommendation that it is ok to use
private code points must be accompanied by text that explains the
possible problems and risks.
I think the cited Unicode reference serves this task: Unicode D49 and thus 23.5 Private-Use Characters.
As for the accurate display of these characters, the draft does cover this issue. It's the IANA considerations (which is admittedly a little weird).
"Note that these profiles are oblivious to many of the issues that are considered in depth in [RFC8264], including case mapping, normalization, and directionality. As noted above, specifications for text fields that are designed for display to and interaction with humans would benefit from consideration of those issues."
I guess there's a grammar bug there as well: "display to and" isn't quite right.
thanks,
Rob
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
