Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: 	Wed, 3 Jul 2002 01:03:35 +0300
From: Ville Herva <vherva AT niksula DOT hut DOT fi>
To: cygwin AT cygwin DOT com
Subject: Re: Accessing filenames with different charsets
Message-ID: <20020702220335.GG9092@niksula.cs.hut.fi>
References: <20020701085851 DOT GD9092 AT niksula DOT cs DOT hut DOT fi> <20020702213825 DOT GF9092 AT niksula DOT cs DOT hut DOT fi> <01f801c22212$7d0cecf0$0100a8c0 AT advent02>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01f801c22212$7d0cecf0$0100a8c0@advent02>
User-Agent: Mutt/1.3.25i

On Tue, Jul 02, 2002 at 10:50:31PM +0100, you [Chris January] wrote:
> Qt (from Trolltech) encodes Unicode filenames before they are used. In
> Cygwin we could do the reverse, i.e. use Find*FileW and then encode the
> Unicode as a local ANSI string. If we do the encoding manually in Cygwin,
> rather than let Windows do it for us, this would overcome the problem. I
> will try to put together a patch for this that you can test. One possibility
> is to encode Unicode strings as UTF-8.

It sounds complicated, but if you are really willing to make a patch, I will
certainly test it.

This might be a good chance to take care of the over 255 char long filenames
that ISTR are only accessible via Find*FileW and the (ugly) \\.\ hack. I
recall once having tried to access such a beast via cygwin, but it failed
(most propably for the same reason as the differing charset ones.)


-- v --

v AT iki DOT fi

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/