X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C2B5A385770B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1681722356; bh=ymD5dAss1434stBz5ou9QBygnW0Ok9nsMvraxKnPfs4=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=BuFVhiqEi82GMxdQGyAl8dIXdSz0qIk5zQ0uQSYYwpZ1XibDNDD2/ck3ClY/zOMl3 I++FhJGJvRLS99+87PEG2F9xEJWsSdCtFny+tx2+XSIvlnyPa3GHg2c0oW454I8/Fp hZFurWah0j9eR0/AYxMDtkIxWY0EJXeeNxjUV/VI= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE4DB3858C50 Date: Mon, 17 Apr 2023 11:05:41 +0200 To: Gionatan Danti , cygwin AT cygwin DOT com Subject: Re: Can not stat file with utf char U+F020 Message-ID: Mail-Followup-To: Gionatan Danti , cygwin AT cygwin DOT com References: <992b3c28d7f1cfc17f7c9bb47b53f770 AT assyoma DOT it> <1274a3199d9bedab4f15d209694c6e1f AT assyoma DOT it> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple