X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Message-ID: <4AB77AC8.2010802@lapo.it>
Date: Mon, 21 Sep 2009 15:08:24 +0200
From: Lapo Luchini <lapo AT lapo DOT it>
User-Agent: Thunderbird 2.0.0.23 (X11/20090831)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: The C locale
References: <416096c60908300959i1e0084b1xc8f6e65e792b035d AT mail DOT gmail DOT com> <20090831005258 DOT GG2068 AT ednor DOT casa DOT cgf DOT cx> <416096c60909012329l2f25e735yc07145b8d6698cda AT mail DOT gmail DOT com> <3f0ad08d0909020656v7d9fce6ft4afea63ed363b9a9 AT mail DOT gmail DOT com> <416096c60909071308qc5ff057sbe9cb1dbc270554f AT mail DOT gmail DOT com> <20090908193456 DOT GC17515 AT calimero DOT vinschen DOT de> <416096c60909081449r1fe024dbm7b82a3719be05e9e AT mail DOT gmail DOT com> <20090921103758 DOT GE20981 AT calimero DOT vinschen DOT de>
In-Reply-To: <20090921103758.GE20981@calimero.vinschen.de>
OpenPGP: id=C8F252FB
Content-Type: multipart/signed; micalg=pgp-sha256;  protocol="application/pgp-signature";  boundary="------------enig1AF8B5B58D01E75EDA976ACC"
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

--------------enig1AF8B5B58D01E75EDA976ACC
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Corinna Vinschen wrote:
>> And if you try to create 'b\344h' in Cygwin 1.7, you actually get a file
>> called 'b', because the '\344' (0xE4) in ISO-8859-1 turns into an
>> encoding error when interpreted as UTF-8, and the name simply seems to
>> be truncated at that point.
>=20
> Yes, that *is* a problem.

Doesn't seems to be exactly that simple: it doesn't stop on the FIRST
non-UTF8 character, but just before the LAST one.
So I guess it's not because it's an encoding error (I doubt the
conversion is made from the end to the start?) but something more complex.

http://cygwin.com/ml/cygwin/2009-09/msg00329.html

> Personally I have no problem with the current approach.  I understand
> the potential problems, but, as usual, solving it one way results in
> problems in another scenario and vice versa.

FWIW I do like the current approach: for example I can transfer with
rsync and commit and checkout with monotone any filename including
Japanese characters...
(well, except the names of the aforementioned thread, but that's a bug
which can be solved, not something implied in the current approach)

--=20
Lapo Luchini - http://lapo.it/

=E2=80=9CC is quirky, flawed, and an enormous success.=E2=80=9D (Dennis M. =
Ritchie)


--------------enig1AF8B5B58D01E75EDA976ACC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJKt3rNAAoJELBiMTth2oCDYBQP/31i0r4S4OqDcpQZih+/Eyx0
gcJCYmJlhgHhgEYVqievZxxUxiPGFCivCDE0PSYoX2EfnVVRIV/8fZogJjOJMlwz
8d3eW+QaEVxop5htZEbqwDnpM29rl+8W7TLOTgBrjE8EzwaVfG7sEAq2IhgHkgGN
3KR21InVaq3fxevmwiioQt3zoqGtNlg/qeOh+G113fjNfbWyaZtO64FMt50Ys1CB
y3HqRR2JRV9mZAfBk9PLUN8njP+822gN9yLSnb2QHaNwizX9Kl7n5cCJzihwZWHx
xCLNYDLIvEIuK+xDZMltNd/eAe5f6+8cj5O19H1OYj11vTslM47/INTqdgsOeyDw
OV5R8jFx1vLmAuIwNvPkBEikEnjlsgH5ilsd1YfNW/fNzQwYNFHDv3OGTxAhPQ2p
2+ubtfmmT6Qw6NJg3XYXg8PMdMBA3Gin6Uqp4AY+DUWWEyCwMExSUuc+R/6dvYpA
dOj+Py2SbOoP7+PxWtNvGLBVCnbezOu4XAuo+USJKtnG62u8ywxmx5ZkkC6nEswP
AFwBSTwDM14VNMwLlI5uPgaGQe1nnmxZvXdrd9N2Rzrr8xRNOlhkPaJofVp9EkGB
aa9Ms+03HHCc5lnGWbK2cu5Tajw62aSSDz2oZQvkUIBX3AUN9TUGi9SjjoeJzuXN
uKfaYXEqkOIZKgUM5yRJ
=pQQt
-----END PGP SIGNATURE-----

--------------enig1AF8B5B58D01E75EDA976ACC--