From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: jean.christophe.helary@gmail.com, emacs-devel@gnu.org
Subject: Re: i18n/l10n summary
Date: Sun, 28 May 2017 18:33:01 +0300 [thread overview]
Message-ID: <83a85xgfo2.fsf@gnu.org> (raw)
In-Reply-To: <0aca6c65-4610-44c2-99c4-6cbe7aa68c9a@default> (message from Drew Adams on Sun, 28 May 2017 07:27:10 -0700 (PDT))
> Date: Sun, 28 May 2017 07:27:10 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> Is the idea that something will be done so that, for example,
> `message' automatically uses a translation of the message to
> the user's currently preferred language? I.e., if that is
> what is planned, isn't it perhaps too systematic - all or
> nothing?
>
> If so, then perhaps there should be a way to easily, from
> Lisp, specify the target language explicitly - e.g. by an
> optional `message' argument or (better, because the scope
> is controllable without changing the `message' calls) by
> binding a variable.
(let ((current-language-environment "FOO"))
(message "FOOBAR"))
> And in that case, there should perhaps be a user option
> that overrides such a language choice by Lisp code.
M-x set-language-environment RET
next prev parent reply other threads:[~2017-05-28 15:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 5:29 i18n/l10n summary Jean-Christophe Helary
2017-05-28 14:27 ` Drew Adams
2017-05-28 14:36 ` Jean-Christophe Helary
2017-05-28 15:33 ` Eli Zaretskii [this message]
2017-06-05 12:55 ` Jean-Christophe Helary
2017-07-17 23:22 ` Jean-Christophe Helary
2017-07-22 12:48 ` Jean-Christophe Helary
2017-07-22 13:06 ` Eli Zaretskii
2017-07-22 13:45 ` Jean-Christophe Helary
2017-07-22 14:08 ` Eli Zaretskii
2017-07-22 23:54 ` Jean-Christophe Helary
2017-07-23 14:39 ` Eli Zaretskii
2017-07-23 23:29 ` Jean-Christophe Helary
2017-07-24 14:47 ` Eli Zaretskii
2017-07-24 15:34 ` Jean-Christophe Helary
2017-07-24 15:51 ` Eli Zaretskii
2017-07-24 16:08 ` Jean-Christophe Helary
2017-07-24 16:29 ` Eli Zaretskii
2017-07-24 16:48 ` Jean-Christophe Helary
2017-07-24 16:55 ` Eli Zaretskii
2017-05-31 22:18 ` Philipp Stephani
2017-05-31 22:29 ` Jean-Christophe Helary
2017-06-01 5:18 ` Paul Eggert
2017-06-01 8:17 ` Philipp Stephani
2017-06-01 23:20 ` Paul Eggert
2017-06-02 6:52 ` Philipp Stephani
2017-06-03 8:37 ` Paul Eggert
2017-06-03 9:12 ` Andreas Schwab
2017-06-03 9:34 ` Philipp Stephani
2017-06-04 15:54 ` Paul Eggert
2017-06-04 16:45 ` Eli Zaretskii
2017-06-04 18:37 ` Paul Eggert
2017-12-03 5:43 ` Paul Eggert
2017-06-01 14:21 ` Eli Zaretskii
2017-07-02 1:22 ` Jean-Christophe Helary
2017-07-02 2:34 ` Eli Zaretskii
2017-07-28 0:15 ` Byung-Hee HWANG (황병희, 黃炳熙)
2018-04-25 12:58 ` Jean-Christophe Helary
2018-09-21 4:18 ` Jean-Christophe Helary
[not found] <<AA86315D-1561-41EB-A349-63100C565E8D@gmail.com>
[not found] ` <<0aca6c65-4610-44c2-99c4-6cbe7aa68c9a@default>
[not found] ` <<83a85xgfo2.fsf@gnu.org>
2017-05-28 21:52 ` Drew Adams
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=83a85xgfo2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.