[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs i18n
From: |
Juri Linkov |
Subject: |
Re: Emacs i18n |
Date: |
Fri, 08 Mar 2019 00:29:17 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) |
>> I think it would be most natural to handle doc strings through
>> a special mechanism.
>
> Up to a point, perhaps. We still should try to use .po files for
> them, if at all possible, and perhaps also the gettext code that
> supports looking up strings in .gmo catalogs generated from .po.
The PO format is best suited for translation of one-liners like
messages and menu items, but I doubt that the PO format would be
the most efficient implementation for multi-line doc strings since
gettext uses the whole text of the doc string as a key to translation.
Whereas more efficient would be to use a Lisp symbol (function or
variable name) as a translation key.
- Re: Emacs i18n, (continued)
- Re: Emacs i18n, Jean-Christophe Helary, 2019/03/11
- Re: Emacs i18n, Michael Albinus, 2019/03/12
- 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, 2019/03/06
- Re: Emacs i18n, Richard Stallman, 2019/03/06
- Re: Emacs i18n, Eli Zaretskii, 2019/03/07
- Re: Emacs i18n,
Juri Linkov <=
- Re: Emacs i18n, Jean-Christophe Helary, 2019/03/07
- Re: Emacs i18n, Eli Zaretskii, 2019/03/08
- Re: Emacs i18n, Jean-Christophe Helary, 2019/03/08
- Re: Emacs i18n, Eli Zaretskii, 2019/03/08
- Re: Emacs i18n, Jean-Christophe Helary, 2019/03/08
- Re: Emacs i18n, Eli Zaretskii, 2019/03/09
- Re: Emacs i18n, Michael Albinus, 2019/03/09
- Re: Emacs i18n, Eli Zaretskii, 2019/03/09
- Re: Emacs i18n, Michael Albinus, 2019/03/09
- Re: Emacs i18n, Eli Zaretskii, 2019/03/09