X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 67FC9385770A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1681498862;
	bh=UyMuN1cZ7kR9iPBjbmxtXmhJTvvaLXRhfbWVIlgZSCc=;
	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=HxMqQUmuRJyP0/aklG262RRrzjgUTl9T2lnHNlf/2kSH3fSNmOXSTNZsbukVTWvWH
	 iny/RKzUh4Z4LhIyKaAxRzka0d+DbfJHDuE0rO7yiiGDe2iQKzvqt5t2poAxUg+kCc
	 Oro7Rh4WNAuKFX3pVZJgqI18mR4W00SpVQvIbtLY=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8153D3858D20
Date: Fri, 14 Apr 2023 21:00:25 +0200
To: Gionatan Danti <g DOT danti AT assyoma DOT it>
Subject: Re: Can not stat file with utf char U+F020
Message-ID: <ZDmiyYS+m0x4QZmh@calimero.vinschen.de>
Mail-Followup-To: Gionatan Danti <g DOT danti AT assyoma DOT it>, cygwin AT cygwin DOT com
References: <992b3c28d7f1cfc17f7c9bb47b53f770 AT assyoma DOT it>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <992b3c28d7f1cfc17f7c9bb47b53f770@assyoma.it>
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>, cygwin AT cygwin DOT com
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" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Apr 14 19:53, Gionatan Danti via Cygwin wrote:
> Dear list,
> I have an issue with unreadable files with contain utf char U+F020 (which
> appear as "middle dot with some space after") in their name.
> 
> stat on such a file results in "no such file or directory"
> 
> From here [1] it seems that a patch was contemplated many years ago, but I
> don't know its status now.
> 
> Any ideas or workaround?

There's no (good) solution from inside Cygwin.

Keep in mind that the Unicode area from U+E000 up to U+F8FF is called
"Private Use Area".  So none of the chars are mapped into any
singlebyte, doublebyte, or multibyte charset.  Typically we don't expect
that filenames contain any of these chars, and we're only using a very
small subset of them for our own, dubious purposes anyway:

https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars

> [1] https://sourceware.org/legacy-ml/cygwin/2009-11/msg00043.html

While this patch would have fixed your problem, a later followup patch
broke your usage of U+F020 (space replacement) and, FWIW, of U+F02E
(dot replacement) again:

https://cygwin.com/cgit/newlib-cygwin/commit/?id=8802178fddfd

This was done to accomodate filesystems implementing the idiotic
approach to support only DOS filenames, i. e., not allowing leading or
trailing spaces and not allowing trailing dots.  These are Netapp and
Novell Netware filesystems.  See the last paragraph of

https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars

Any chance you can just rename the files?


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