public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Thomas Dickey <dickey@his.com> To: cygwin-xfree@cygwin.com Subject: Re: X11R7.5 and C.UTF-8 Date: Fri, 04 Dec 2009 09:45:00 -0000 [thread overview] Message-ID: <20091204044346.M57150@mail101.his.com> (raw) In-Reply-To: <loom.20091203T231736-983@post.gmane.org> On Thu, 3 Dec 2009, Eric Blake wrote: > Thomas Dickey <dickey <at> his.com> writes: > >>> This means that characters 0..127 have to be treated as ASCII, but > > No, it means that portable characters and control characters must be < 128. > ASCII meets this characteristic, but so does EBCDIC, as well as UTF-8. The C > locale also implies that you can manipulate bytes >= 128 in the naive manner, > so long as you don't care about characters embedded in those bytes. And what > do you know - ASCII, EBCDIC, and UTF-8 all meet this property, too. > >>> 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. >> >> That's an interpretation that so far hasn't been blessed by the standards >> people. Any discussion of this topic should mention that, as a caveat. > > Actually, the standards people HAVE spoken - and they agreed with our > interpretation. POSIX was INTENTIONALLY written with the intent that a UTF-8 > encoding is valid for the C locale, for the same reason that it was written > that an EBCDIC encoding is valid for the C locale. These emails from the > Austin Group (the folks that write POSIX) are telling: > > https://www.opengroup.org/sophocles/show_mail.tpl? > CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=12982 This is basically your email on the matter. > https://www.opengroup.org/sophocles/show_mail.tpl? > CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=13012 > > But they also admitted that there is still more work needed in POSIX to make > this intent clearly codified (for example, that control characters must be > single bytes < 128). But they have not actually agreed with you yet. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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-04 9:45 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 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 [this message] 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=20091204044346.M57150@mail101.his.com \ --to=dickey@his.com \ --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).