X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7767D3857718 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1681722664; bh=1HHR126vSzftcgx9durLcXUmqkX9/0Xdh4EKTwQqh/Q=; 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=mhsXUjGM7e5xzjz9Q+WrUoBlhBAKvvbOhJmI9m8AEA6zCgmvur5IupIl5byR9tdhq lKTURVuPt9gWFHHbJFEBgVetzOUcocjxUElnYoOgfX6SwkPBLRv2KCYZIl314xaMSp W3lGl48pMeIvPQOpLQn04WitmzgZLuVZEs5CoYHo= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 56B4C385828D Date: Mon, 17 Apr 2023 11:10:48 +0200 To: cygwin AT cygwin DOT com Subject: Re: Can not stat file with utf char U+F020 Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com, Brian Inglis , Gionatan Danti References: <992b3c28d7f1cfc17f7c9bb47b53f770 AT assyoma DOT it> <8f4e63968f4cc73093f7ebbb32788286 AT assyoma DOT it> <60ce2271-99e4-3fc9-5073-7a36ba202c20 AT Shaw DOT ca> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <60ce2271-99e4-3fc9-5073-7a36ba202c20@Shaw.ca> 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 , Brian Inglis , Gionatan Danti 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 14 23:10, Brian Inglis via Cygwin wrote: > On 2023-04-14 14:17, Gionatan Danti via Cygwin wrote: > > Il 2023-04-14 21:00 Corinna Vinschen ha scritto: > > > There's no (good) solution from inside Cygwin. > > > 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? > > > [1] https://en.wikipedia.org/wiki/Private_Use_Areas#Vendor_use > > Now if MS SfM and Cygwin had both registered with U/CSUR, they would not be > fighting over Unicode code points, although it looks like there is a lot of > competition for the code points! ;^> > > Would it make more sense to add custom file name character filters into some > utility, such as unix2dos/mac2unix, cygpath, or some other, and add > (Cyg)win, or create such a utility, so those could be added to processes? Adding this to some utility would make more sense than adding another complication into the Cygwin codebase to support really old stuff. 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