On Apr 14 22:21, Gionatan Danti via Cygwin wrote: > Il 2023-04-14 21:54 Brian Inglis ha scritto: > > UCSUR Under-ConScript Unicode Registry and its predecessor ConScript > > Unicode Registry CSUR > > > > https://www.kreativekorp.com/ucsur/ > > > > http://www.evertype.com/standards/csur/ > > > > unofficially register Unicode PUA glyphs for academic, artificial, > > constructed, historical, invented, and minority language scripts, some > > of which have made it into Unicode e.g. > > > > Script CSUR Unicode > > PHAISTOS DISC U+E6D0-U+E6FF U+101D0-U+101DF > > SHAVIAN U+E700-U+E72F U+10450-U+1047F > > DESERET U+E830-U+E88F U+10400-U+1044F > > > > and maintain their own Unidata e.g. > > > > https://www.kreativekorp.com/ucsur/UNIDATA/Blocks.txt > > > > and some Unicode fonts have -CSUR addition files (like -Italic etc.) > > that support BMP and SMP PUA glyphs. > > So they are actively using PUA? I did not know that, thanks. > > > For Cygwin purposes: > > > > F000−F7FF unassigned Reserved for hacks and corporate use > > > > so Cygwin's special Windows file name characters mappings are clear: > > > > F022 " > > F02A * > > F03A : > > F03C < > > F03E > > > F03F ? > > F07C | > > Would it be possible to "bypass" the chars in the range F000−F7FF that are > not used/reserved by cygwin?
We do that. You're just stumbling over tha fact that U+F020 is also used as outlined in https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars and https://cygwin.com/pipermail/cygwin/2023-April/253478.html Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
