delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
Date: | Mon, 2 Nov 2009 12:42:07 +0100 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: SOLVED: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode |
Message-ID: | <20091102114207.GA7831@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
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> <416096c60910311333p3d26f997n1a11e7fdbc6a46a3 AT mail DOT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <416096c60910311333p3d26f997n1a11e7fdbc6a46a3@mail.gmail.com> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
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 |
On Oct 31 20:33, Andy Koppe wrote: > >> You must not use characters > >> in this range from U+f000 up to U+f0ff. There'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. I was contemplating this over the weekend. I just applied a patch to do this. I tested this with various filenames containing all sorts of characters, including f000, which would represent an ASCII NUL, if used wrongly. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |