From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corinna@sourceware.org>
Received: by sourceware.org (Postfix, from userid 2155)
	id AE4DB3858C50; Mon, 17 Apr 2023 09:05:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE4DB3858C50
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1681722343;
	bh=7Mqrn2UMX6ZPr7kLb0bDHiW8z6WUOCZ/ByDXzTLhVWM=;
	h=Date:From:To:Subject:Reply-To:References:In-Reply-To:From;
	b=gdaV2bq5tiw/zGBNvv9vYKMIVk2/vmdeHRPI+W6sQs/ODmEt0m9HnzGMap9VSSYQO
	 +7lNNRIeT4dZD8W2cp42OaSGn5K+DonvTv9ErrgAree8pGsPedNDJheeIie028VcPJ
	 NavKudbCJqCw9K7BTUl+bHEtWfUSHqeViVY7e3r0=
Received: by calimero.vinschen.de (Postfix, from userid 500)
	id 2737CA80B9C; Mon, 17 Apr 2023 11:05:41 +0200 (CEST)
Date: Mon, 17 Apr 2023 11:05:41 +0200
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
Message-ID: <ZD0L5VoqmTHmHBT9@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: Gionatan Danti <g.danti@assyoma.it>, cygwin@cygwin.com
References: <992b3c28d7f1cfc17f7c9bb47b53f770@assyoma.it>
 <ZDmiyYS+m0x4QZmh@calimero.vinschen.de>
 <f4d0bd30-731a-fb5e-43d2-a86d1af761b6@Shaw.ca>
 <dfbdeec869acd6ed1ad7b4ec803336f2@assyoma.it>
 <ZDm20Rug7TswU4KI@calimero.vinschen.de>
 <1274a3199d9bedab4f15d209694c6e1f@assyoma.it>
 <de19dc1ecd891f748e5e4a317f347477@assyoma.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <de19dc1ecd891f748e5e4a317f347477@assyoma.it>
List-Id: <cygwin.cygwin.com>

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