X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<19155.26084.13747.22184@parhasard.net>
References:	<20a807210910071714t45136fd7hc36108c990377bc4 AT mail DOT gmail DOT com> <87pr8yqmdt DOT fsf AT uwakimon DOT sk DOT tsukuba DOT ac DOT jp> <20a807210910080843k50c4cbddtb06ad474b3195a03 AT mail DOT gmail DOT com> <87ws35pwbg DOT fsf AT uwakimon DOT sk DOT tsukuba DOT ac DOT jp> <20a807210910081950v80a4da9ga5ed1265dfca07ef AT mail DOT gmail DOT com> <416096c60910082244k388e8861v84ec7846ecbf9e0a AT mail DOT gmail DOT com> <19155 DOT 26084 DOT 13747 DOT 22184 AT parhasard DOT net>
Date:	Mon, 12 Oct 2009 19:07:08 +0100
Message-ID:	<416096c60910121107r408947e6i4774b0b8adb02338@mail.gmail.com>
Subject:	Re: Segfault under cygwin 1.7.62
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com, XEmacs developers <xemacs-beta AT xemacs DOT org>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

2009/10/12 Aidan Kehoe:
>  > and how does it change unexpectedly in terms of POSIX/Cygwin operation=
s?
>  > And, importantly, what's the locale setting?
>
> We=E2=80=99re testing our handling of the file name encoding; we want to =
make sure
> we can create a file with this name when we force the file name encoding =
to
> ISO-8859-2.
>
> We probably shouldn=E2=80=99t be converting to Unicode at all for file na=
me encoding
> on Cygwin, we should use file-name-coding-system as determined by the loc=
ale
> like on every other Unix.

Yep, for Cygwin 1.7 at least, that'd definitely be the right thing to
do. Cygwin will automatically and transparently convert between the
charset specified in the locale and Windows' UTF-16 filenames.

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -