MIME-Version: 1.0
In-Reply-To: <19155.26084.13747.22184@parhasard.net>
References: <20a807210910071714t45136fd7hc36108c990377bc4@mail.gmail.com> 	 <87pr8yqmdt.fsf@uwakimon.sk.tsukuba.ac.jp> 	 <20a807210910080843k50c4cbddtb06ad474b3195a03@mail.gmail.com> 	 <87ws35pwbg.fsf@uwakimon.sk.tsukuba.ac.jp> 	 <20a807210910081950v80a4da9ga5ed1265dfca07ef@mail.gmail.com> 	 <416096c60910082244k388e8861v84ec7846ecbf9e0a@mail.gmail.com> 	 <19155.26084.13747.22184@parhasard.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.koppe@gmail.com>
To: cygwin@cygwin.com, XEmacs developers <xemacs-beta@xemacs.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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