From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Gionatan Danti <g.danti@assyoma.it>
Subject: Re: Can not stat file with utf char U+F020
Date: Fri, 14 Apr 2023 13:54:47 -0600 [thread overview]
Message-ID: <f4d0bd30-731a-fb5e-43d2-a86d1af761b6@Shaw.ca> (raw)
In-Reply-To: <ZDmiyYS+m0x4QZmh@calimero.vinschen.de>
On 2023-04-14 13:00, Corinna Vinschen via Cygwin wrote:
> On Apr 14 19:53, Gionatan Danti via Cygwin wrote:
>> I have an issue with unreadable files with contain utf char U+F020 (which
>> appear as "middle dot with some space after") in their name.
>> stat on such a file results in "no such file or directory"
>> From here [1] it seems that a patch was contemplated many years ago, but I
>> don't know its status now.
>> Any ideas or workaround?
> There's no (good) solution from inside Cygwin.
> Keep in mind that the Unicode area from U+E000 up to U+F8FF is called
> "Private Use Area". So none of the chars are mapped into any
> singlebyte, doublebyte, or multibyte charset. Typically we don't expect
> that filenames contain any of these chars, and we're only using a very
> small subset of them for our own, dubious purposes anyway:
> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars
>> [1] https://sourceware.org/legacy-ml/cygwin/2009-11/msg00043.html
> While this patch would have fixed your problem, a later followup patch
> broke your usage of U+F020 (space replacement) and, FWIW, of U+F02E
> (dot replacement) again:
> https://cygwin.com/cgit/newlib-cygwin/commit/?id=8802178fddfd
> This was done to accomodate filesystems implementing the idiotic
> approach to support only DOS filenames, i.e. not allowing leading or
> trailing spaces and not allowing trailing dots. These are Netapp and
> Novell Netware filesystems. See the last paragraph of
> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars
> Any chance you can just rename the files?
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.
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 |
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-04-14 19:54 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 [this message]
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
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=f4d0bd30-731a-fb5e-43d2-a86d1af761b6@Shaw.ca \
--to=brian.inglis@shaw.ca \
--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).