From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17458 invoked by alias); 3 Dec 2009 07:48:56 -0000 Received: (qmail 17450 invoked by uid 22791); 3 Dec 2009 07:48:55 -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, 03 Dec 2009 07:48:51 +0000 Received: by qyk37 with SMTP id 37so436467qyk.18 for ; Wed, 02 Dec 2009 23:48:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.19.82 with SMTP id z18mr194061qca.9.1259826529020; Wed, 02 Dec 2009 23:48:49 -0800 (PST) In-Reply-To: <4B174C20.1040900@tlinx.org> References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> Date: Thu, 03 Dec 2009 07:48:00 -0000 Message-ID: <416096c60912022348i36504e14l726efc9fc9c360e6@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 Content-Transfer-Encoding: quoted-printable 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-12/txt/msg00014.txt.bz2 2009/12/3 Linda Walsh: > C.UTF_8 doesn't exist. Well, guess what: it does in Cygwin 1.7, and it's the default locale. And it's also in the next Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D522776. Cygwin 1.7 also supports "C.ISO-8859-1", "C.CP1252", ... > Might want to try 'Console' nstead of using mintty. =C2=A0Not perfect eit= her, but > fewer compatibility problems that I've noticed. Care to provide examples, so they can be fixed? Or are you just bitter about having to tick a box to switch backspace to ^H? 'Console' is better for native Windows programs, because, well, it's a console, whereas mintty is more suited for Unix programs, because it's an xterm-compatible tty. > You can't have "C" and "UTF-8", because C means no encoding (default). > UTF-8 IS an encoding, so they are mutually exclusive. >>From http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.htm= l, =C2=A77.2: "The tables in Locale Definition describe the characteristics and behavior of the POSIX locale for data consisting entirely of characters from the portable character set and the control character set. For other characters, the behavior is unspecified." This means that characters 0..127 have to be treated as ASCII, but beyond that an implementation can do what it wants. And on Cygwin 1.7, plain "C" actually does imply UTF-8, which happily is backward-compatible with ASCII. Not that that is much to do with "C.UTF-8", which is a separate locale in any case. The meaning of locale strings is up to the OS, e.g. with the Windows C runtime you get stuff like "English_United States.1252". And 'C.' on Cygwin is intended to mean "the semantics of the C locale, but with the specified charset". However, since the 'C.' format is unlikely to be recognised by remote systems, it's recommended to set a "real" locale such as 'en_US.UTF-8'. > I don't > know under what circumstances "C" might imply UTF-8. If the definition > of "C" changes? It might be easier than changing "c" (as used in physics= ). How droll. 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/