public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: X11R7.5 and C.UTF-8
Date: Thu, 03 Dec 2009 07:48:00 -0000	[thread overview]
Message-ID: <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> (raw)
In-Reply-To: <4B174C20.1040900@tlinx.org>

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=522776.

Cygwin 1.7 also supports "C.ISO-8859-1", "C.CP1252", ...


> Might want to try 'Console' nstead of using mintty.  Not perfect either, 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.html,
§7.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.<charset>' on Cygwin is intended to mean "the semantics of the
C locale, but with the specified charset".

However, since the 'C.<charset>' 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/


  parent reply	other threads:[~2009-12-03  7:48 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 [this message]
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=416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com \
    --to=andy.koppe@gmail.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: link
Be 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).