From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: wilde@sha-bang.de, thomas@intevation.de, emacs-devel@gnu.org
Subject: Re: Better language detection for tutorial
Date: Thu, 26 Jul 2007 11:29:48 +0900 [thread overview]
Message-ID: <E1IDt6q-0000HA-0w@etlken.m17n.org> (raw)
In-Reply-To: <ubqe0ffsb.fsf@gnu.org> (message from Eli Zaretskii on Wed, 25 Jul 2007 22:24:04 +0300)
In article <ubqe0ffsb.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > From: Kenichi Handa <handa@m17n.org>
> > CC: wilde@sha-bang.de, thomas@intevation.de, emacs-devel@gnu.org
> > Date: Wed, 25 Jul 2007 13:48:14 +0900
> >
> > In article <usl7dmaxm.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > Examining the environment variables in different order and with
> > > different logic, to determine the language environment.
> >
> > Impossible. Emacs doesn't have a language environment that
> > matches with his request.
> Which is what? I thought it was simply English.
No. His locale settings are this:
LANG=en_US
LC_CTYPE=de_DE@euro
LC_MESSAGES="en_US"
So, coding-system must be latin-9 (iso-8859-15), but
messages (i.e. tutorial) must be English.
For this case, "Latin-9" language environment may be an
alternative one that will work, but it's just by chance (and
not easy to find it from the above setting). For instance,
we don't have any alternative lang. env. for this:
LC_CTYPE=ja_JP
LC_MESSAGES="en_US"
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2007-07-26 2:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 10:14 set-locale-environement: strange default detection Sascha Wilde
2007-07-18 10:19 ` David Kastrup
2007-07-18 10:40 ` Sascha Wilde
2007-07-18 10:50 ` David Kastrup
2007-07-18 11:04 ` Jan Djärv
2007-07-18 12:28 ` Sascha Wilde
2007-07-18 18:54 ` Reiner Steib
2007-07-18 21:24 ` David Kastrup
2007-07-19 8:21 ` Sascha Wilde
2007-07-19 9:16 ` David Kastrup
2007-07-22 14:59 ` Better language detection for tutorial (was: set-locale-environement: strange default detection) Sascha Wilde
2007-07-22 15:41 ` Andreas Schwab
2007-07-22 15:44 ` Better language detection for tutorial David Kastrup
2007-07-22 23:16 ` Andreas Schwab
2007-07-22 20:20 ` Sascha Wilde
2007-07-23 3:11 ` Eli Zaretskii
2007-07-23 9:25 ` Sascha Wilde
2007-07-23 19:29 ` Eli Zaretskii
2007-07-23 20:29 ` Sascha Wilde
2007-07-23 20:38 ` David Kastrup
2007-07-24 6:18 ` Eli Zaretskii
2007-07-24 7:17 ` Kenichi Handa
2007-07-24 7:36 ` Eli Zaretskii
2007-07-24 7:53 ` Kenichi Handa
2007-07-24 18:45 ` Eli Zaretskii
2007-07-25 1:01 ` Kenichi Handa
2007-07-25 3:14 ` Eli Zaretskii
2007-07-25 4:48 ` Kenichi Handa
2007-07-25 19:24 ` Eli Zaretskii
2007-07-26 2:29 ` Kenichi Handa [this message]
2007-07-26 11:40 ` Eli Zaretskii
2007-07-26 12:19 ` Kenichi Handa
2007-07-26 12:25 ` Eli Zaretskii
2007-07-26 12:54 ` Kenichi Handa
2007-07-20 17:42 ` set-locale-environement: strange default detection Reiner Steib
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=E1IDt6q-0000HA-0w@etlken.m17n.org \
--to=handa@m17n.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=thomas@intevation.de \
--cc=wilde@sha-bang.de \
/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).