X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E24303858C3A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1681505510;
	bh=ngxzfeNvhx/jOeTsQCl/2Li8bc03fZdA8qiT6C9V6PI=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=qtsVRcPKoo620cTT9v2FPwScJek2i8wuBqRjKkLjNS0cDMuW/p2J8aqyz3tLH9byV
	 TgRE4KX1QSBLRRwPCBxgNcA1URqsIIseo0BNP87EupD2SpLi/7azrxLPzoUt4SwmWm
	 xuyLBv8F9zC5pCOFyzaHRl/pd6ga8RvoMnLt4aKA=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 864C93857719
MIME-Version: 1.0
Date: Fri, 14 Apr 2023 22:51:11 +0200
To: Gionatan Danti <g DOT danti AT assyoma DOT it>, Brian Inglis
 <Brian DOT Inglis AT shaw DOT ca>,
        cygwin AT cygwin DOT com
Subject: Re: Can not stat file with utf char U+F020
In-Reply-To: <ZDm6IurD9ykLOoSv@calimero.vinschen.de>
References: <992b3c28d7f1cfc17f7c9bb47b53f770 AT assyoma DOT it>
 <ZDmiyYS+m0x4QZmh AT calimero DOT vinschen DOT de>
 <8f4e63968f4cc73093f7ebbb32788286 AT assyoma DOT it>
 <ZDm6IurD9ykLOoSv AT calimero DOT vinschen DOT de>
Message-ID: <ba57420fb8184222cbe2889e2617b4fe@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 <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: Gionatan Danti via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Gionatan Danti <g DOT danti AT assyoma DOT it>
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" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Il 2023-04-14 22:40 Corinna Vinschen ha scritto:
> This is really tricky.  A new mount point flag could be used to 
> override
> this behaviour on a per path basis.  One problem is, the unicode ->
> multibyte conversion when evaluating a symlink is done before it's 
> clear
> where the symlink target is.  Only the string is converted and it might
> be a relative path, so the code doesn't know where the target ends up.
> And that's probably not all.

To tell the truth, it is such a corner (and infortunate) case that I 
would not care if the workaround does not work for symlinks.

> Is it really worth to add code to support a long deprecated Windows
> service?

Yeah, I understand your point. I am not in the position to evaluate if 
it would be worth.
Maybe a special case for only U+F020 (the most common "strange" char I 
see) can be considered?

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