X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45,SARE_SUB_ENC_UTF8,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <Pine.NEB.4.64.1004021756090.12087@panix1.panix.com>
References: <Pine DOT NEB DOT 4 DOT 64 DOT 1004021704050 DOT 12087 AT panix1 DOT panix DOT com> 	 <4BB66FD6 DOT 5080402 AT redhat DOT com> 	 <Pine DOT NEB DOT 4 DOT 64 DOT 1004021756090 DOT 12087 AT panix1 DOT panix DOT com>
Date: Sat, 3 Apr 2010 07:13:06 +0100
Received: by 10.239.186.140 with SMTP id g12mr270639hbh.146.1270275186087;  	Fri, 02 Apr 2010 23:13:06 -0700 (PDT)
Message-ID: <z2g416096c61004022313qabab1b4cs749e07e6534f83ce@mail.gmail.com>
Subject: Re: UTF-8 versus utf8
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
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

Tim McDaniel:
> Eric Blake:
>>> Why does <http://cygwin.com/cygwin-ug-net/setup-locale.html> talk
>>> all about a charset of UTF-8, then "For a list of locales supported
>>> by your Windows machine, use the new locale -a command", which
>>> shows "utf8" (which matches my XP machine)?
>>
>> UTF-8 is the canonical name of the charset, but utf8 is an
>> acceptable synonym in most contexts, and is much easier to type.
>> So, when it comes to specifying your charset, the suffix ".utf8" is
>> used to request the UTF-8 charset.
>
> So why doesn't "locale -a" report the canonical name?

Because the same happens on Linux, and Cygwin aims for Linux
compatibility: LANG is usually set up as *.UTF-8, yet 'locale -a'
reports *.utf8. So why does Linx do things that way? No idea, sorry.

Both UTF-8 and utf8 are accepted in locale variable settings, as are
utf-8 and UTF8.

Btw, what did you mean by "utf8 (which matches my XP machine)"

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