X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Sun, 25 Nov 2007 02:46:35 -0800
From:	Mariusz Wodzicki <wodzicki AT Math DOT Berkeley DOT EDU>
Message-Id:	<200711251046.lAPAkZbO015926@cba1.math.Berkeley.EDU>
To:	cygwin AT cygwin DOT com
Subject:	utf-8 and cygwin
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

I would like to reopen the discussion about utf-8 support in cygwin.

SIXTEEN months passed since there were some exchanges about it
on the cygwin mail list.

The lack of support for filenames with non-Latin1 characters is
currently the MOST SEVERE LIMITATION of cygwin in my opinion.

Due to the international nature of internet more and more of us
are getting all sorts of files with utf-8 filenames.

In presence of such files in our file systems, all the basic
commands are broken (ls, cp, mv, diff, rsync, et cetera).

This becomes more and more annoying with every passing day.

What is the current situation? When can we expect that
this problem gets resolved?

By the way, is there a cygwin command that is equivalent
to DOS `dir /x' (which shows 'short' filenames)?

Mariusz Wodzicki

--
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 -