X-Spam-Check-By:	sourceware.org
Message-ID:	<454737C6.4040302@666.com>
Date:	Tue, 31 Oct 2006 05:47:18 -0600
From:	Ben Wing <ben AT 666 DOT com>
User-Agent:	Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version:	1.0
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	Any plans to incorporate UTF-8 support into Cygwin?
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

There's already a patch that purports to be fairly complete, which 
modifies Cygwin so that its paths are UTF-8:

http://www.okisoft.co.jp/esc/utf8-cygwin/

It's extremely annoying now that Cygwin cannot reliably work with file 
names containing non-ASCII non-Latin1 characters (and even with Latin-1  
chars it may be touch and go). NOTE: Such filenames come up a lot for 
me, even though I'm a native US speaker.  Stuff downloaded using P2P may 
often have foreign words in it or foreign notations in brackets, music 
tracks from foreign bands often have foreign characters in the 
filenames, etc.  If a directory has a foreign-named file anywhere in it, 
both cp -a and tar-cp will fail to copy the directory properly, mangling 
the filenames in the process.   Any plans to incorporate this fix into 
mainline Cygwin?  I'd rank it pretty high priority, and it shouldn't be 
too hard to do.

ben

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

- Raw text -