X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7D7173857729 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1681503506; bh=9Yx12ISxOlX2XhNr2nAyT+IBO/NwFPDepSnQywHm/To=; 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=KTS5jf1pBZaYadmDr8NcZM0nBCxcBFOJrg0Y3qbTdnL2aWn+fl8F6eqZ98lwbSkbX eKx1jgCpZ//Lk9gQiY+l1PwmVuQKks2AfgglvwVQKkz8993X6XtD+xtsk8AmX4USwT vw2WL/R62QMkI1hwUq3V3s2Ozm0VwUHW4aZjier4= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2F9C53858409 MIME-Version: 1.0 Date: Fri, 14 Apr 2023 22:17:44 +0200 To: Gionatan Danti Cc: cygwin AT cygwin DOT com Subject: Re: Can not stat file with utf char U+F020 In-Reply-To: References: <992b3c28d7f1cfc17f7c9bb47b53f770 AT assyoma DOT it> Message-ID: <8f4e63968f4cc73093f7ebbb32788286@assyoma.it> X-Sender: g DOT danti AT assyoma DOT it X-Spam-Status: No, score=0.5 required=5.0 tests=BAYES_40, 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 21:00 Corinna Vinschen ha scritto: > There's no (good) solution from inside Cygwin. > [snip] Yeah, I can only imagine how difficult is to be compatible with posix, win32 and the likes. > Any chance you can just rename the files? I renamed the files, in fact. However, it seems that users working with (older?) Office for MAC use U+F020 more frequently than I expected, maybe because of that [1]: "Microsoft's defunct Services For Macintosh feature used U+F001 through U+F029 as replacements for special characters allowed in HFS but forbidden in NTFS, and U+F02A for the Apple logo." Any chances to enable a "bypass" for these characters (excluding the one you reserved for compatibility as explained detailed in the "Forbidden characters in filenames")? Maybe hidden behind a configurable option (even disabled by default), so to not interfere with the current behavior? Thanks. [1] https://en.wikipedia.org/wiki/Private_Use_Areas#Vendor_use -- 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