public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm> To: cygwin-xfree@cygwin.com Subject: Re: X11R7.5 and C.UTF-8 Date: Thu, 03 Dec 2009 07:37:00 -0000 [thread overview] Message-ID: <4B176AC7.4030405@cwilson.fastmail.fm> (raw) In-Reply-To: <4B174C20.1040900@tlinx.org> Linda Walsh wrote: > C.UTF_8 doesn't exist. You're wrong. Please read the whole of this thread -- and the last two months' worth of cygwin-developers. > mintty is broken. No, it isn't. It just doesn't work the way *you* expect it to. > Might want to try 'Console' nstead of using mintty. Not perfect either, > but fewer compatibility problems that I've noticed. > > Examples of valid LANG values: > C, ca_FR, en_US, fr_FR, it_IT, nl_NL, wa_BE@euro > > You can't have "C" and "UTF-8", because C means no encoding (default). No, it doesn't. "C" means "POSIX" and is defined here: http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html Note how all the glyphs are defined in terms of character NAMES, not hexadecimal values? That's because "C", all by itself, just doesn't SPECIFY any encoding. You're still allowed to HAVE one -- in fact, you ALWAYS have one. On most systems, that has historically been the plain ASCII 7-bit encoding; many others used the EBCDIC encoding and were not considered in violation of the POSIX "C" locale specification. Now, many systems are starting to use the UTF-8 encoding by default, even in the "C" locale. "C"/"POSIX" locale (without an additional .ENCODING suffix) is encoding-AGNOSTIC, that's all. So, you're allowed to add an .ENCODING suffix to force a specific encoding if you like, without violating POSIX. (And your system is also allowed, in that case, to IGNORE that .ENCODING suffix, and still be Posix-compliant IIUC, so it's rather a hole in the spec IMO). > UTF-8 IS an encoding, so they are mutually exclusive. I don't > know under what circumstances "C" might imply UTF-8. Whenever the platform decides to use UTF-8 as its default encoding, which is perfectly acceptable according to Posix. Cygwin-1.7 has decided to do that. So, on cygwin-1.7, "C" implies .UTF-8. X11R7.5 doesn't yet know that, without outside help (e.g. explicitly setting $LANG to "C.UTF-8" by default, so that XWin "knows" about the new default behavior). > If the definition > of "C" changes? It might be easier than changing "c" (as used in physics). > > My understanding of locale issues is also limited and subject to change or > re-education... Uhm, yeah. -- 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/
next prev parent reply other threads:[~2009-12-03 7:37 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-28 14:22 Ken Brown 2009-10-28 21:23 ` Thomas Dickey 2009-10-28 21:48 ` Ken Brown 2009-10-28 22:07 ` Andy Koppe 2009-11-28 12:22 ` Ken Brown 2009-11-28 13:35 ` Andy Koppe 2009-11-28 15:29 ` Ken Brown 2009-12-03 5:27 ` Linda Walsh 2009-12-03 7:37 ` Charles Wilson [this message] 2009-12-03 7:48 ` Andy Koppe 2009-12-03 9:09 ` Corinna Vinschen 2009-12-03 9:55 ` Thomas Dickey 2009-12-03 13:16 ` Andy Koppe 2009-12-03 13:48 ` Corinna Vinschen 2009-12-04 4:30 ` Eric Blake 2009-12-04 9:45 ` Thomas Dickey 2009-10-28 21:49 ` Andy Koppe 2009-10-28 23:51 ` Andy Koppe 2009-10-28 22:19 ` Charles Wilson 2009-10-28 23:52 ` Jon TURNEY 2009-10-29 0:07 ` Andy Koppe 2009-10-29 13:42 ` Jon TURNEY 2009-10-29 13:56 ` Corinna Vinschen 2009-10-29 14:54 ` Jon TURNEY 2009-10-29 14:37 ` Ken Brown 2009-10-29 15:01 ` Jon TURNEY 2009-10-29 19:11 ` Jon TURNEY 2009-10-29 20:20 ` Andy Koppe 2009-11-03 21:00 ` Jon TURNEY 2009-11-04 6:34 ` Andy Koppe
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4B176AC7.4030405@cwilson.fastmail.fm \ --to=cygwin@cwilson.fastmail.fm \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).