From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9476 invoked by alias); 14 Feb 2014 14:05:35 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 9466 invoked by uid 89); 14 Feb 2014 14:05:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.0 required=5.0 tests=AWL,BAYES_20 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 14 Feb 2014 14:05:34 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 6037F5209FF; Fri, 14 Feb 2014 15:05:32 +0100 (CET) Date: Fri, 14 Feb 2014 14:13:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: New passwd/group handling in Cygwin - test results and observations Message-ID: <20140214140532.GD2246@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20140213143849.GH2246@calimero.vinschen.de> <1717869165.20140214021113@mtu-net.ru> <20140214102044.GX2246@calimero.vinschen.de> <1078913914.20140214155631@mtu-net.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1GFpsN+DA+8qGtn4" Content-Disposition: inline In-Reply-To: <1078913914.20140214155631@mtu-net.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-02/txt/msg00362.txt.bz2 --1GFpsN+DA+8qGtn4 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1539 On Feb 14 15:56, Andrey Repin wrote: > > But this is a problem not different from Linux. If you have a username > > with non-ASCII chars, it will use *some* encoding in the passwd DB, > > usually UTF-8 these days. If you then change the codeset in your > > application, you will still get your username in UTF-8. It won't be > > changed on the fly, just because your application calls setlocale. >=20 > I understand it (mostly), but there's actually two issues, not one. > One issue is the display part, where names are output for user consumptio= n. > Another can be observed in, i.e., rsync, and file access in general (reme= mber > the discussion about accessing long directory names in unicode). > Changing LANG variable DO matter for the latter, and you may only hope th= at > whatever is output in the former case is actually printable (thank God, m= ost > of the time it actually is, in case of UTF-8). > It is getting even more complicated, when you consider the fact, that in > Windows you have 2 different single-byte encodings, so-called ANSI (for G= UI > applications) and OEM (for console). And alot of stuff making assumptions > without consulting with current status of things. > As convoluted the problem is, I think, we need some sort of solution, or = at > the very least - documentation. Sorry, I can't provide an easy solution, and afaik this is documented. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --1GFpsN+DA+8qGtn4 Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJS/iKsAAoJEPU2Bp2uRE+gfDEP/2Ipbh3lSq8FkUcvnlVO0oJ4 42osUWJXe8i6+0kmgrPuPOHioln8dx1UEcSqX0sw+OLks4RKHwHD4Y4ah+LRaQ2U W7RvbreOMVynVL2qgBw81MYEjDQ+96SGYIYSXKyzXRQ1Wo7fCBCTc9RmxxhNV+rk CSJYAyeFoj/KdEp6bCEQFyrvDO1aPxEeJIxntUGb7qUfkD5/LI0/70HXnZQHTsMM ciCCA+vajQEruiN/RFFgKALLAnkIdIoXl+kx7uCGAmk3hAUmhzPMmclDiz8Xeadn ZHgs231fiP6fgv6tmJHT0PfIoN0YNjSlr3NjYfINc1pTgRnHo7nUwKk50lrNw9Il 5VHc//c4Nmhy6/ivhFGfZPFEYUObTD2P5fk5Jkr5RXLRClnJHgEI+htrxQKESRiF k7ETz3aO2cv+S3e3d0G+ligIfELkGSQRugJ2lcutv9FPJQFkgF7t1SuJr/yqsQDL +9tVHQ1yTop6IDVzBrKv9KRJFuvFAq2Fu9whaZIZWzyagCsN6rWWgH3q/4IlgUyw S8BeJ5s9Al0cTJWqreIBzol+40Roqw4zWAVEN+fRO5gOc3FlPyPQ3IAu3xHxv71C 18OCo0NCcY9xA1lHkw1Gkgtwd2fRtAJdGPkE3UF7zBCIdNLPgdR+eyqM03DJGdUi oRGJOVjLZEK/JR+V288l =vtSr -----END PGP SIGNATURE----- --1GFpsN+DA+8qGtn4--