Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Mon, 14 Jun 2004 14:02:48 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Unable to open files including Korean names
Message-ID:	<20040614120248.GF1365@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20040612183000 DOT GA1628 AT sab DOT mazic DOT org> <20040612183000 DOT GA1628 AT sab DOT mazic DOT org> <3 DOT 0 DOT 5 DOT 32 DOT 20040613145523 DOT 00805ce0 AT incoming DOT verizon DOT net> <20040614111257 DOT GA3736 AT sab DOT mazic DOT org>
Mime-Version:	1.0
In-Reply-To:	<20040614111257.GA3736@sab.mazic.org>
User-Agent:	Mutt/1.4.2i

On Jun 14 20:12, Jaeho Shin wrote:
> On Sun, Jun 13, 2004 at 02:55:23PM -0400, Pierre A. Humblet (XXXXXX DOT XXXXXXX AT XXXX DOT XXX) wrote:

Please don't quote raw email addresses in a reply!

http://cygwin.com/acronyms/index.html#PCYMTNQREAIYR

> > Your original mail stated
> > "I did some test and found out that ``every file whose path includes
> > Korean characters weren't openable.''  Still, I could move arround those
> > paths from my shell, and get the file/directory listings with "ls"
> > normally. I could still create directories with Korean names. "
> > 
> > That would indicate that it's not the path handling code, but the use
> > of NtCreateFile in 1.5.10. 
> > Can you "ls -l" those paths?
> 
> Sorry about my complaints against you.  I misunderstood ``path
> handling'' as everything done when openning files with paths in Cygwin.
> Yes, I can "ls -l" them, so the problem is really in the file openning
> part, not the path handling. :)

I'm under the impression, the important difference is that Cygwin does the
MultiByte to WideChar conversion instead of Windows itself.

Could you please add "codepage:oem" to your CYGWIN environment variable
and try again?  Does that change the behaviour?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader          mailto: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/

- Raw text -