X-Recipient: archive-cygwin@delorie.com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A727E3857BB2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1681866738; bh=q7OqeYr4avdpFTNY7WmnHm+/iEGWxPecL/h4RbWEoww=; h=Date:To:CC:Subject:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=Q03GrCE4mZlhD9nvpoGCAwUoE3EiOSPFC35LN4ROQDdnp/ry5Ty7EzK9KvJE0QtFi mQkO9YIs9d+t3kg+cfJRCk1QtAhFs+LJxmP59an1Kbaly8J15Mnkst3R2sSSQzl6fN xdOC73HfDrUZxyUzyfz0BFD6N4EBQSPVj5obC5Mc= X-Original-To: cygwin@cygwin.com Delivered-To: cygwin@cygwin.com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 46C13385843E Message-ID: <643F3F87.2050403@tlinx.org> Date: Tue, 18 Apr 2023 18:10:31 -0700 User-Agent: Thunderbird MIME-Version: 1.0 To: Gionatan Danti CC: "cygwin@cygwin.com" Subject: Re: Can not stat file with utf char U+F020 References: <992b3c28d7f1cfc17f7c9bb47b53f770@assyoma.it> <1274a3199d9bedab4f15d209694c6e1f@assyoma.it> <1a7db5a68644e5b66634d5af9b402caf@assyoma.it> In-Reply-To: <1a7db5a68644e5b66634d5af9b402caf@assyoma.it> X-Spam-Status: No, score=-19.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_NUMSUBJECT, KHOP_HELO_FCRDNS, SPF_HELO_NONE, TXREP, T_SCC_BODY_TEXT_LINE, T_SPF_PERMERROR 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@cygwin.com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: L A Walsh via Cygwin Reply-To: L A Walsh Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "Cygwin" I'm a bit confused as to what char you are trying to access/use, as U+F020 is in the Private Use area (PUA) Since it's in the PUA, it seems its meaning could differ by application/OS/User, no? I.e. have no set definition I mean you can use it in Cygwin to represent some character not usually permitted in a DOS/Win filename (like :/\, etc.), but it wouldn't have the same meaning then in Windows though.? Isn't Private Use area application specific so an application can create and use its own symbol set -- even though it wouldn't be portable to another application. So if you create a character in Cygwin that maps to that area -- how would you expect Windows to know that the character is and how treat it? I think characters in the PUA range are used to allow Cygwin filenames to contain colon, slashes and quotes -- so one wouldn't want Windows to understand the cygwin intent or it would defeat the purpose of using custom characters to represent filenames that are legal under POSIX but not under Windows. -- 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