From: L A Walsh <cygwin@tlinx.org>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Can not stat file with utf char U+F020
Date: Tue, 18 Apr 2023 18:10:31 -0700 [thread overview]
Message-ID: <643F3F87.2050403@tlinx.org> (raw)
In-Reply-To: <1a7db5a68644e5b66634d5af9b402caf@assyoma.it>
I'm a bit confused as to what char you are trying to access/use, as
U+F020 is in the Private Use area (PUA)
Since it's in the PUA, it seems its meaning could differ by
application/OS/User, no?
I.e. have no set definition
I mean you can use it in Cygwin to represent some character not usually
permitted in
a DOS/Win filename (like :/\, etc.), but it wouldn't have the same
meaning then
in Windows though.? Isn't Private Use area application specific so an
application can
create and use its own symbol set -- even though it wouldn't be portable
to another application.
So if you create a character in Cygwin that maps to that area -- how
would you expect Windows to
know that the character is and how treat it?
I think characters in the PUA range are used to allow Cygwin filenames
to contain colon, slashes
and quotes -- so one wouldn't want Windows to understand the cygwin
intent or it would defeat
the purpose of using custom characters to represent filenames that are
legal under POSIX but not
under Windows.
next prev parent reply other threads:[~2023-04-19 1:11 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
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 [this message]
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=643F3F87.2050403@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=g.danti@assyoma.it \
/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).