From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corinna@sourceware.org>
Received: by sourceware.org (Postfix, from userid 2155)
	id 56B4C385828D; Mon, 17 Apr 2023 09:10:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 56B4C385828D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1681722650;
	bh=GMUJnopnPinAs9TGnFTqvRr/LSua9KuHZYRzv7LkKz0=;
	h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From;
	b=ujeRITMatTYEY5mjah5N6d/NLsv75ixPxmW/AVvhIDgEtZIrFs2PX3krh/tjeAHi/
	 bG33raEQKcEoJA1iSzVnAZyipIrlv8vBjyxbk5zVET+EmAPK5pAa4wI/TsVoN+1ML/
	 bCbYb9X/SeM+3Y3tRMEUYUC0wQqf0S6NSI4Toqlk=
Received: by calimero.vinschen.de (Postfix, from userid 500)
	id 8A2C6A80B9C; Mon, 17 Apr 2023 11:10:48 +0200 (CEST)
Date: Mon, 17 Apr 2023 11:10:48 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@shaw.ca>,
	Gionatan Danti <g.danti@assyoma.it>
Subject: Re: Can not stat file with utf char U+F020
Message-ID: <ZD0NGIehlRNXBgiS@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com, Brian Inglis <Brian.Inglis@shaw.ca>,
	Gionatan Danti <g.danti@assyoma.it>
References: <992b3c28d7f1cfc17f7c9bb47b53f770@assyoma.it>
 <ZDmiyYS+m0x4QZmh@calimero.vinschen.de>
 <8f4e63968f4cc73093f7ebbb32788286@assyoma.it>
 <60ce2271-99e4-3fc9-5073-7a36ba202c20@Shaw.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <60ce2271-99e4-3fc9-5073-7a36ba202c20@Shaw.ca>
List-Id: <cygwin.cygwin.com>

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