public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Gionatan Danti <g.danti@assyoma.it>, cygwin@cygwin.com
Subject: Re: Can not stat file with utf char U+F020
Date: Mon, 17 Apr 2023 11:05:41 +0200	[thread overview]
Message-ID: <ZD0L5VoqmTHmHBT9@calimero.vinschen.de> (raw)
In-Reply-To: <de19dc1ecd891f748e5e4a317f347477@assyoma.it>

On Apr 17 07:36, Gionatan Danti via Cygwin wrote:
> Il 2023-04-14 23:01 Gionatan Danti via Cygwin ha scritto:
> > Il 2023-04-14 22:25 Corinna Vinschen via Cygwin ha scritto:
> > > 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
> > 
> > Ah, so spaces and dots are replaced respectively by U+F020 and U+F02E
> > even without the "dos" mount option?
> > Because I can not see it in my case of an NTFS filesystem with the
> > following mount options: binary,posix=0,user,noumount,auto
> 
> Hi all,
> it's not clear to me why even without the "dos" mount option both space and
> dot are replaced by U+F020 and U+F02E, preventing U+F020 passthrough.
> 
> Am I missing something?

It's actually not the "dos" mount option but specific filesystems
which trigger the conversion from U+0020 to U+F020.

However, the conversion back is handled in a piece of code which has
no information about the underlying filesystem, so the F0xx -> 00xx
conversion is done all the time.  Adding filesystem info in this
place is really tricky.


Corinna

  reply	other threads:[~2023-04-17  9:05 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 [this message]
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=ZD0L5VoqmTHmHBT9@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).