X-Spam-Check-By: sourceware.org
Date: Mon, 5 Dec 2005 11:30:43 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: open() giving ENOENT when trying to create files with control chars
Message-ID: <20051205103043.GN2999@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <120220052038 DOT 3878 DOT 4390B0AC000B476600000F2622007601800A050E040D0C079D0A AT comcast DOT net> <20051202220905 DOT GA2999 AT calimero DOT vinschen DOT de> <20051204172940 DOT GB3276 AT efn DOT org> <20051204194350 DOT GG2999 AT calimero DOT vinschen DOT de> <loom DOT 20051205T110754-387 AT post DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <loom.20051205T110754-387@post.gmane.org>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Dec  5 10:11, Bill Hughes wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> 
> > 
> > On Dec  4 09:29, Yitzchak Scott-Thoennes wrote:
> ..snip..
> > > 
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;117258
> > > is interesting...
> > 
> > This is certainly interesting.  Using this in Cygwin would require to
> > change the path handling to using UNICODE, though, which is a major
> > undertaking since the path handling throughout Cygwin is plain ASCII
> > right now.
> 
> Uh, don't forget this is the NTFS API and not the Windows API.
> If you want to go down this route you may as well add case sensitive file names
> too...

That's not quite right.  Case-sensitivity is a flag which can be
switched on and off at will.  It's a property of the driver, not the
underlying file system.  The underlying file system is obviously capable
of storing case-sensitive filenames, the driver just handles characters
only differing by case as equal in the default Windows case.  The above
is converting invalid characters to valid characters.  These new
characters are still valid characters even when you're working in a
plain ASCII (or ISO-8859) environment, since NTFS stores the filenames
in UNICODE anyway.

I'm not sure until I tried it, of course, but I don't think this will
result in problems with Windows, just because your standard font can't
display the characters.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

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