X-Spam-Check-By: sourceware.org
Date: Thu, 30 Nov 2006 12:32:11 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Windows NTFS UCS2 characters
In-Reply-To: <456F0E89.28B2E427@dessent.net>
Message-ID: <Pine.GSO.4.63.0611301226090.10187@access1.cims.nyu.edu>
References: <C1946630.19DC4%eljay AT adobe DOT com> <456F0E89 DOT 28B2E427 AT dessent DOT net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Thu, 30 Nov 2006, Brian Dessent wrote:

> John Love-Jensen wrote:
>
> > I can always fallback to use scripts for CMD.EXE to manipulate these
> > files; but I'd rather be able to do it in my Bash shell scripts.
> >
> > Please don't suggest Interix, SFU or MKS alternatives.  Those are fine
> > products, I'm sure, but I'm not interested.
>
> I'm afraid you're probably just out of luck.  If I understand the
> problem Cygwin currently does not use wide characters internally for
> filenames/pathnames, nor does it support any locale other than "C"/posix
> (the latter due to newlib limitations.)

The former is true, the latter is half-true.  Cygwin works with the
default codepage when the Windows locale settings are set correctly.  You
cannot *switch* locales programmatically from within Cygwin, but it can
handle the full 8-bit charset just fine.

> So you're limited to ANSI filenames in the current codepage, I think.

Not sure what ANSI means in this context (if you meant ASCII, or 7-bit,
then the codepage reference makes no sense).  If the codepage is set
correctly, Cygwin will read those files.

> There is a site out there that maintains a UTF-8 modified Cygwin, and
> these changes have been submitted for inclusion, but the wrapper method
> used did not meet technical muster and so it will remain a third-party
> fork.  I am sure everyone would love to see a wchar-sporting Cygwin but
> to do it right will affect a lot of code paths and so it's no trivial
> undertaking.

Right.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

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