From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24797 invoked by alias); 29 Oct 2009 20:20:44 -0000 Received: (qmail 24789 invoked by uid 22791); 29 Oct 2009 20:20:42 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SARE_SUB_ENC_UTF8,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-qy0-f199.google.com (HELO mail-qy0-f199.google.com) (209.85.221.199) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Oct 2009 20:20:38 +0000 Received: by qyk37 with SMTP id 37so1266355qyk.18 for ; Thu, 29 Oct 2009 13:20:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.31.211 with SMTP id z19mr75193qcc.24.1256847637061; Thu, 29 Oct 2009 13:20:37 -0700 (PDT) In-Reply-To: <4AE9E8DE.9010803@dronecode.org.uk> References: <4AE8539E.9080004@cornell.edu> <4AE8D942.8020806@dronecode.org.uk> <416096c60910281707t3249dfb7tc6d0caf0e57ba626@mail.gmail.com> <4AE99BAD.6060303@dronecode.org.uk> <4AE9A8AD.2030702@cornell.edu> <4AE9AE57.8010405@dronecode.org.uk> <4AE9E8DE.9010803@dronecode.org.uk> Date: Thu, 29 Oct 2009 20:20:00 -0000 Message-ID: <416096c60910291320r4fb374ebhe5c7167dfe6fdce0@mail.gmail.com> Subject: Re: X11R7.5 and C.UTF-8 From: Andy Koppe To: cygwin-xfree@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes 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/msg00138.txt.bz2 2009/10/29 Jon TURNEY: > I've put a patch in bugzilla [1] which can be applied to > /usr/share/X11/locale to temporarily repair this problem. > > This needs to be looked at more deeply, though, as I'm not sure I've fully > understood what that locale data is being used for, or specified C.UTF-8 > correctly. > > [1] http://sourceware.org/bugzilla/show_bug.cgi?id=10870 I think the patch makes plenty of sense in mapping C.UTF-8 to en_US.UTF-8, because most other UTF-8 locales are also mapped to en_US.UTF-8, i.e. from X's perspective they're not actually language-specific. More generally, there's the issue that Cygwin allows any combination of language and charset, whereas X has a fixed list of permitted combinations. Cygwin also supports many charsets that aren't supported by X (and vice versa). In particular, X only supports a few of the Windows/DOS codepages. But I guess unsupported locales will just have to be a case of "don't do that"? Andy -- 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/