[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs i18n
From: |
Jean-Christophe Helary |
Subject: |
Re: Emacs i18n |
Date: |
Fri, 8 Mar 2019 10:48:46 +0900 |
> On Mar 8, 2019, at 7:29, Juri Linkov <address@hidden> wrote:
>
> 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.
po4a is a commonly used perl utility that creates po files from a number of
documentation formats including texinfo. The msgid is indeed the paragraph
itself but nobody sees any "efficiency" issue in the process.
Since the emacs code is not a documentation format, there would be a need to
find a different way to extract the doc strings, but using each doc string
paragraph as a msgid is not a problem in itself.
Let's not forget that most if not all issues regarding formats and processes on
the l10n side have mostly been solved decades ago.
I think what really needs to be discussed is:
• which strings do we extract
• how to rewrite the mix of code and strings
• how to extract the resulting strings
• how to process the translations for display in emacs
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
- Re: Emacs i18n, (continued)
- Re: Emacs i18n, Juri Linkov, 2019/03/19
- 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, 2019/03/07
- Re: Emacs i18n,
Jean-Christophe Helary <=
- 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
- Re: Emacs i18n, Paul Eggert, 2019/03/09