X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D6045385771B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1681709852; bh=5U2alP+GstyQPFbIx9Fwus5Zw/EEPRZvh5Drtlb56cU=; h=Date:To:Cc:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=fWNSnvtlNXscZFYOHguWuFI6n1FjWmkCr4u81rAY6Qdxxbb240r2Aqxq7ziX6j5Ww 5FLkb6e2VpBzhVQG48op9RJzr4hTcLT0DAxGei/cyWO/+QHVI2MiRIN0TIPbxShwsh HKQ2nHaSNdOS2UqvHW1lMg2p9RwkczNZnWXGyjX4= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8B7603858CDB MIME-Version: 1.0 Date: Mon, 17 Apr 2023 07:36:52 +0200 To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Subject: Re: Can not stat file with utf char U+F020 In-Reply-To: <1274a3199d9bedab4f15d209694c6e1f@assyoma.it> References: <992b3c28d7f1cfc17f7c9bb47b53f770 AT assyoma DOT it> <1274a3199d9bedab4f15d209694c6e1f AT assyoma DOT it> Message-ID: X-Sender: g DOT danti AT assyoma DOT it X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_NUMSUBJECT, SPF_HELO_NONE, SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org 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: Gionatan Danti via Cygwin Reply-To: Gionatan Danti Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g DOT danti AT assyoma DOT it - info AT assyoma DOT it GPG public key ID: FF5F32A8 -- 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