X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 14 May 2009 10:12:46 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [1.7] Proposal: the filename encoding in C locale uses UTF-8 	instead of SO/UTF-8
Message-ID: <20090514081246.GA11778@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3f0ad08d0905121029j119c8a7ep41d3a261d8bea338 AT mail DOT gmail DOT com> <20090512173741 DOT GZ21324 AT calimero DOT vinschen DOT de> <20090513142953 DOT GI21324 AT calimero DOT vinschen DOT de> <op DOT utvhnyxl1e62zd AT balu> <416096c60905130754s3ffaae9dl8d6df4c4184b95e6 AT mail DOT gmail DOT com> <20090513151753 DOT GJ21324 AT calimero DOT vinschen DOT de> <op DOT utv1lfsu1e62zd AT merlin DOT emma DOT line DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <op.utv1lfsu1e62zd@merlin.emma.line.org>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On May 13 23:49, Matthias Andree wrote:
> Am 13.05.2009, 17:17 Uhr, schrieb Corinna Vinschen  
> <corinna-cygwin AT cygwin DOT com>:
>
>> I followed the suggestion to use UTF-8 for internal conversions when the
>> locale is set to "C".  This will also be used as default conversion when
>> converting the Windows environment from UTF-16 to multibyte, unless the
>> environment contains a valid LC_ALL/LC_CTYPE/LANG setting.  The current
>> working directory was also potentially unusable, if an application
>> switched the locale.  Now the CWD is re-evaluated after a setlocale call.
>
> Is Unicode normalization an issue here?

Not really, I guess.  Either a character is available or it isn't.
We don't have composition or decomposition capabilities for most
multibyte character sets anyway.  If at all, we could only do that
for SJIS, EUCJP, and GBK.  None of them would profit a lot of that.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/