[Last-Call] Re: Last Call: <draft-bray-unichars-10.txt> (Unicode Character Repertoire Subsets) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Martin's email contains an interesting detail:

RFC 3987: Internationalized Resource Identifiers (IRIs) allows private-use characters in the query string, so you have to allow them in order to transmit valid IRIs. This document is about the character repertoire, so it doesn't matter if they are escaped on the wire. 

thanks,
Rob

On Thu, Feb 13, 2025 at 1:00 PM Rob Sayre <sayrer@xxxxxxxxx> wrote:
On Thu, Feb 13, 2025 at 12:46 PM Tim Bray <tbray@xxxxxxxxxxxxxx> wrote:

  1. Private Use areas

I searched the correspondence and couldn't find the discussion behind this one. My recollection is that someone argued strongly that Unicode says these code points are considered to be assigned (I checked, and indeed it does say that) and that there might well be scenarios where they are used as intended as part of the protocol definition, so they shouldn’t be seen as problematic. 

Once again, this is not a hill I would die on; if consensus is that PUA code points should be classified as “problematic”, OK.

This one comes from distinguishing PUA code points from "unassigned" code points here.


I don't think they are any more "problematic" than unassigned code points, fwiw. There will always be the possibility of getting a code point you don't understand or don't have a glyph for. It can even just be the new emoji they put out every year.

thanks,
Rob

-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux