From: Gionatan Danti <g.danti@assyoma.it>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@shaw.ca>
Subject: Re: Can not stat file with utf char U+F020
Date: Fri, 14 Apr 2023 22:21:40 +0200 [thread overview]
Message-ID: <dfbdeec869acd6ed1ad7b4ec803336f2@assyoma.it> (raw)
In-Reply-To: <f4d0bd30-731a-fb5e-43d2-a86d1af761b6@Shaw.ca>
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?
Regards.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2023-04-14 20:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 17:53 Gionatan Danti
2023-04-14 19:00 ` Corinna Vinschen
2023-04-14 19:54 ` Brian Inglis
2023-04-14 20:20 ` Corinna Vinschen
2023-04-14 20:21 ` Gionatan Danti [this message]
2023-04-14 20:25 ` Corinna Vinschen
2023-04-14 21:01 ` Gionatan Danti
2023-04-17 5:36 ` Gionatan Danti
2023-04-17 9:05 ` Corinna Vinschen
2023-04-17 10:58 ` Andrey Repin
2023-04-17 13:46 ` Gionatan Danti
2023-04-18 21:09 ` Gionatan Danti
2023-04-19 1:10 ` L A Walsh
2023-04-19 11:56 ` Gionatan Danti
2023-04-14 20:17 ` Gionatan Danti
2023-04-14 20:40 ` Corinna Vinschen
2023-04-14 20:51 ` Gionatan Danti
2023-04-15 5:10 ` Brian Inglis
2023-04-17 9:10 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfbdeec869acd6ed1ad7b4ec803336f2@assyoma.it \
--to=g.danti@assyoma.it \
--cc=Brian.Inglis@shaw.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).