X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4AEC9A9F.6080201@monai.ca>
References: <4AE65A40 DOT 9070405 AT monai DOT ca> 	 <20091027091532 DOT GB2076 AT calimero DOT vinschen DOT de> 	 <4AE8A278 DOT 5060406 AT monai DOT ca> 	 <20091029110030 DOT GN28753 AT calimero DOT vinschen DOT de> 	 <4AE9F26B DOT 4030203 AT monai DOT ca> <4AEC9A9F DOT 6080201 AT monai DOT ca>
Date: Sat, 31 Oct 2009 20:33:53 +0000
Message-ID: <416096c60910311333p3d26f997n1a11e7fdbc6a46a3@mail.gmail.com>
Subject: Re: SOLVED: Removed 1.5.25 and installed 1.7.0, but still cannot  	access filenames containing Unicode
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

2009/10/31 Steven Monai:
>> That's the problem. =C2=A0The character in that file is *not* U+0323, but
>> U+f020, a character in the Unicode private use range, which is used in
>> Cygwin to map ASCII characters invalid in Windows filenames but valid
>> in POSIX filenames. =C2=A0It's also used to map multibyte characters > 0=
x80
>> which are invalid in the current charset.
>
> Thanks for diagnosing my problem. My assumption that the char was U+0323
> was based on scrolling through the Windows Character Map app for
> something that visually matched what I was seeing in the filename. Not
> having any other way to quantify the char, I jumped to an incorrect
> conclusion.

Any idea how that U+f020 character had got in there in the first place?

>> You must not use characters
>> in this range from U+f000 up to U+f0ff. =C2=A0There's no solution to this
>> except for "don't use these characters in filenames if they are not
>> explicitely written there by either Cygwin or Microsoft's SUA".

Actually there is a possible solution: when translating a U+F0xx
character, first check whether the xx byte really is illegal in the
target charset. If it's not, it won't roundtrip correctly, so encode
the U+F0xx as a ^X sequence instead. Doesn't seem worth the effort
though.

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple