Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: Unicode in filenames support?
Date: Tue, 7 Jun 2005 14:17:02 -0400
Message-ID: <94BF3137C62D3E4CAED7E97F876585F09DA960@pauex2ku08.agere.com>
From: "Williams, Gerald S \(Jerry\)" <gsw@agere.com>
To: <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit

Corinna Vinschen wrote:
> Not that I know of.  We're discussing to convert Cygwin's path
> handling to use Unicode for a while now, but it will take time. 
> Don't expect this any time soon.

I've been off of the developer list for a while now, and
now the archives are subscriber only. :-(

How are you thinking about doing this? At one point, I
created a framework that supported this. Unicode support
was actually just a side-effect--my real goal was to let
you use two files whose names differ only by case or use
files with otherwise illegal names such as "aux". I even
went so far as to create a project on SourceForge so that
I could release it into the public domain.

However, it was NTFS-specific and Cygwin went a different
route (which has path length limitations, but I digress).
I did finally get my company's permission to release the
code, but there was little point by then. (I also had to
scramble to survive a reorg at that time and didn't have
any time at all for quite a while afterwards.)

If there is interest in my NTFS-specific solution, please
let me know. (Actually, it's not necessarily specific to
NTFS, though it probably is in practice. It definitely
doesn't support FATxx or Win9x.)

gsw


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