From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2155) id AF9A83858C5E; Fri, 14 Apr 2023 20:25:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AF9A83858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1681503954; bh=SYWJT/K3CghepgaDgaCxlf+F/USGRH7pDyzJu89FkxY=; h=Date:From:To:Subject:Reply-To:References:In-Reply-To:From; b=eK25szjjzxeiBasnbWXe4/myuW1Pik7ukhmz7VYVLQrq/1OU2Nm1UaZcN0/rKa4dZ RcH/6Y+Sa/1f8H6YGitOVfePA3XoKg3CKxb4KbeVUdIODnI+E8gH1Zr8Z8t2fHb4e0 O/2VGT7uIa3rFF2tFIZ+NUztT82wpyxt9YJFONlY= Received: by calimero.vinschen.de (Postfix, from userid 500) id 11003A81B29; Fri, 14 Apr 2023 22:25:53 +0200 (CEST) Date: Fri, 14 Apr 2023 22:25:53 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Can not stat file with utf char U+F020 Message-ID: Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <992b3c28d7f1cfc17f7c9bb47b53f770@assyoma.it> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: On Apr 14 22:21, Gionatan Danti via Cygwin wrote: > Il 2023-04-14 21:54 Brian Inglis ha scritto: > > 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. > > So they are actively using PUA? I did not know that, thanks. > > > 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 | > > Would it be possible to "bypass" the chars in the range F000−F7FF that are > not used/reserved by cygwin? We do that. You're just stumbling over tha fact that U+F020 is also used as outlined in https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars and https://cygwin.com/pipermail/cygwin/2023-April/253478.html Corinna