From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3678 invoked by alias); 28 Oct 2009 22:19:16 -0000 Received: (qmail 3653 invoked by uid 22791); 28 Oct 2009 22:19:15 -0000 X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SARE_SUB_ENC_UTF8,SPF_PASS X-Spam-Check-By: sourceware.org Received: from out4.smtp.messagingengine.com (HELO out4.smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 28 Oct 2009 22:19:10 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id C2861BDF0D for ; Wed, 28 Oct 2009 18:19:08 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 28 Oct 2009 18:19:09 -0400 Received: from [192.168.1.3] (user-0c6sbc4.cable.mindspring.com [24.110.45.132]) by mail.messagingengine.com (Postfix) with ESMTPSA id 5487549ADF7; Wed, 28 Oct 2009 18:19:08 -0400 (EDT) Message-ID: <4AE8C353.7080806@cwilson.fastmail.fm> Date: Wed, 28 Oct 2009 22:19:00 -0000 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: X11R7.5 and C.UTF-8 References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> In-Reply-To: <20091028172216.P60895@mail101.his.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2009-10/txt/msg00117.txt.bz2 Thomas Dickey wrote: > On Wed, 28 Oct 2009, Ken Brown wrote: > >> X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server > > technically speaking, there's "no such locale" as C.UTF-8, > so I'd not expect portable code to accept it ("C" and "UTF-8" are > mutually exclusive). No, actually they are not. The "C" or "POSIX" locale is defined entirely in terms of character values -- not hexidecimal equivalents. That is, "the set alpha shall contain 'a', 'b'..." etc. The standard actually doesn't require that an implementation specify the encoding in which those character values are represented at all. You can, if you want, use 'HEX_CHAR', 'OCTAL_CHAR', and 'DECIMAL_CHAR' representations -- which implicitly require a specific encoding -- but the standard defines the 'C' locale entirely in terms of CHAR and CHARSYMBOL, which are encoding-agnostic. http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html#tag_07_03 Personally, I think it's a hole in the standard that it doesn't actually talk about "the POSIX locale with encoding Y" -- but then, they don't want to show preference between ASCII and EBCDIC, so UTF-8 sneaks in there. -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/