unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: [reinersteib+gmane@imap.cc: language environment should not be derived from LC_CTYPE]
Date: Thu, 23 Nov 2006 15:20:56 -0500	[thread overview]
Message-ID: <87irh5q5hz.fsf@furball.mit.edu> (raw)
In-Reply-To: <E1Gn4h0-00057g-Uh@fencepost.gnu.org> (Richard Stallman's message of "Wed\, 22 Nov 2006 21\:52\:02 -0500")

> I have the following locale settings [1]:
>
> $ env|grep -e LC_ -e LANG
> LANG=en_US
> LC_COLLATE=POSIX
> LC_CTYPE=de_DE@euro
>
> $ emacs -Q
>
> `current-language-environment's value is "German" and I get the German
> tutorial.  I expected to see the English version and an English
> language environment:
>
> | `LC_CTYPE'
> |      This category applies to classification and conversion of
> |      characters, and to multibyte and wide characters
> |
> | `LANG'
> |      If this environment variable is defined, its value specifies the
> |      locale to use for all purposes except as overridden by the
> |      variables above.

>From lisp/international/mule-cmds.el:

(defun set-locale-environment (&optional locale-name)
  "Set up multi-lingual environment for using LOCALE-NAME.
This sets the language environment, the coding system priority,
the default input method and sometimes other things.
...
If LOCALE-NAME is nil, its value is taken from the environment
variables LC_ALL, LC_CTYPE and LANG (the first one that is set)."

Both `set-locale-environment' and the glib documentation say that LANG
only takes effect LC_CTYPE is undefined.  I think the only thing for
this situation is for the user to set the language environment in the
.emacs file.

  reply	other threads:[~2006-11-23 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  2:52 [reinersteib+gmane@imap.cc: language environment should not be derived from LC_CTYPE] Richard Stallman
2006-11-23 20:20 ` Chong Yidong [this message]
2006-11-25  9:13   ` Reiner Steib
2006-11-25 10:49     ` Jan Djärv
2006-11-25 10:57     ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87irh5q5hz.fsf@furball.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).