[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs i18n
From: |
Eli Zaretskii |
Subject: |
Re: Emacs i18n |
Date: |
Thu, 07 Mar 2019 05:30:19 +0200 |
> Cc: address@hidden, address@hidden, address@hidden
> From: Paul Eggert <address@hidden>
> Date: Wed, 6 Mar 2019 17:33:26 -0800
>
> On 3/6/19 11:49 AM, Eli Zaretskii wrote:
> > We are miscommunicating: I meant strings passed to 'message' and its
> > ilk, not just any kind of strings.
>
> In that case, the solution that Richard proposed should suffice for most
> cases. That is, in most cases we shouldn't need to change the Elisp
> source code; all we need is for xgettext (or its equivalent) to consider
> the first argument of 'message' to be a translatable string. This is a
> standard feature of xgettext (see its --keyword argument).
This will solve the string extraction part. But how will the actual
translation happen? As I wrote elsewhere, I don't see how relying on
the function to perform the extraction will work with non-fixed
strings.
- Re: Emacs i18n, (continued)
- Re: Emacs i18n, Richard Stallman, 2019/03/07
- Re: Emacs i18n, Richard Stallman, 2019/03/07
- Re: Emacs i18n, Eli Zaretskii, 2019/03/06
- Re: Emacs i18n, Eli Zaretskii, 2019/03/06
- Re: Emacs i18n, Paul Eggert, 2019/03/06
- Re: Emacs i18n, Eli Zaretskii, 2019/03/06
- Re: Emacs i18n, Paul Eggert, 2019/03/06
- Re: Emacs i18n,
Eli Zaretskii <=
- Re: Emacs i18n, Paul Eggert, 2019/03/07
- Re: Emacs i18n, Jean-Christophe Helary, 2019/03/06
- Re: Emacs i18n, Paul Eggert, 2019/03/07
- Re: Emacs i18n, Richard Stallman, 2019/03/07
- Re: Emacs i18n, Juri Linkov, 2019/03/11
- Re: Emacs i18n, Paul Eggert, 2019/03/11
- Re: Emacs i18n, Juri Linkov, 2019/03/12
- Re: Emacs i18n, Juri Linkov, 2019/03/17
- Re: Emacs i18n, Juri Linkov, 2019/03/18
- Re: Emacs i18n, Paul Eggert, 2019/03/18