X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 675D23858C39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1681502125; bh=4ipcbhMmhGnZ+nQ+wv6Dh2kC9STGOWcLUFzyjqBrcPw=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=elP3TpInu8L+NZRHYyZCrFcdxIRQnd39EjVU7XxlIWJzN4nfm5FcHZfcNf1FhnA16 lVFzQ2OUdjfoSO1br3MefxXmzulHPycNVxt47NTWtwCoLEwLDlAp42ccy3PdiBFDcf Rj6lpkK9iTS8e0qvRm9xCiIGNmRHFID01HhQp8eg= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0E52A3858C54 X-Authority-Analysis: v=2.4 cv=XZqaca15 c=1 sm=1 tr=0 ts=6439af88 a=DxHlV3/gbUaP7LOF0QAmaA==:117 a=DxHlV3/gbUaP7LOF0QAmaA==:17 a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=CCpqsmhAAAAA:8 a=-ASX7PQZAAAA:8 a=aGu4qCp4AAAA:8 a=_76rHcExO6kzltpOXLQA:9 a=QEXdDO2ut3YA:10 a=zvuQ_vupYScA:10 a=ON2IeW3fjaEA:10 a=sRI3_1zDfAgwuvI8zelB:22 a=ul9cdbp4aOFLsgKbc677:22 a=30rGu5QBbLmXMKHcn8Nk:22 a=OgNdeCq1iSRX4M99ZXWK:22 Message-ID: Date: Fri, 14 Apr 2023 13:54:47 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Can not stat file with utf char U+F020 Content-Language: en-CA To: cygwin AT cygwin DOT com References: <992b3c28d7f1cfc17f7c9bb47b53f770 AT assyoma DOT it> Organization: Inglis In-Reply-To: X-CMAE-Envelope: MS4xfNX+or3qpL9JMdnEFE+M1R9mC1dNoUyb/DAMUpMQujTm6hEgLKg1FEGkj4qiVfB7sIPV74olhEze6dYQuZNExXKf3YU5VPGpmHSbHKql/uTc5bs3QHkx m3Ke34hteSpIk5IGopyGaiZKx7hZVKP7YSvSxGKdmI9c1KgEN7UEn1cd7Zw0Tvv5rNxwICO40kuvFql7TXiOlKBAUVf6OUaXv+0= X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Brian Inglis via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Brian Inglis , Gionatan Danti Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 33EJtowR026712 On 2023-04-14 13:00, Corinna Vinschen via Cygwin wrote: > On Apr 14 19:53, Gionatan Danti via Cygwin wrote: >> 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? UCSUR Under-ConScript Unicode Registry and its predecessor ConScript Unicode Registry CSUR https://www.kreativekorp.com/ucsur/ http://www.evertype.com/standards/csur/ unofficially register Unicode PUA glyphs for academic, artificial, constructed, historical, invented, and minority language scripts, some of which have made it into Unicode e.g. Script CSUR Unicode PHAISTOS DISC U+E6D0-U+E6FF U+101D0-U+101DF SHAVIAN U+E700-U+E72F U+10450-U+1047F DESERET U+E830-U+E88F U+10400-U+1044F and maintain their own Unidata e.g. https://www.kreativekorp.com/ucsur/UNIDATA/Blocks.txt and some Unicode fonts have -CSUR addition files (like -Italic etc.) that support BMP and SMP PUA glyphs. For Cygwin purposes: F000−F7FF unassigned Reserved for hacks and corporate use so Cygwin's special Windows file name characters mappings are clear: F022 " F02A * F03A : F03C < F03E > F03F ? F07C | -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry -- 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