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, 29 Oct 2009 20:20:00 -0000	[thread overview]
Message-ID: <416096c60910291320r4fb374ebhe5c7167dfe6fdce0@mail.gmail.com> (raw)
In-Reply-To: <4AE9E8DE.9010803@dronecode.org.uk>

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/


  reply	other threads:[~2009-10-29 20:20 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
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 [this message]
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=416096c60910291320r4fb374ebhe5c7167dfe6fdce0@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).