[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs i18n
From: |
Bruno Haible |
Subject: |
Re: Emacs i18n |
Date: |
Thu, 21 Mar 2019 03:55:10 +0100 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-141-generic; KDE/5.18.0; x86_64; ; ) |
Hi Juri,
> Currently we have more urgent tasks after the first step of adding
> ‘ngettext’ like in CLISP, the development stalled on the problem of
> splitting messages into domains.
You are very welcome to ask for advice on bug-gettext. It's there that
you can find the experts. (I don't read emacs-devel usually.)
> But maybe CLISP already provides a good way to map packages to gettext
> domains? Does it require every package to have a separate domain or
> it collects translations from all packages into one domain?
What matters for the domains is what code gets distributed together.
* When you have two Lisp packages that are released by separate
groups of developers, of course they must use separate translation
domains. Otherwise you would have to co-ordinate the merging of their
POT files, which makes no sense since they make releases at different
times.
* On the other hand, when you have two Lisp packages that are always
released together, in the same tarball, it is more efficient for the
translators if they receive one notification about a new POT file
than two notifications about two POT files on the same day.
For Common Lisp code, the Common Lisp package name _may_ be used to
derive the domain name. But this is up to the developers.
For reference, i18n in CLISP is described here:
https://clisp.sourceforge.io/impnotes/i18n-mod.html
https://www.gnu.org/software/gettext/manual/html_node/Common-Lisp.html
and there is a sample and a test case in GNU gettext:
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=blob;f=gettext-tools/examples/hello-clisp/hello.lisp.in
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=blob;f=gettext-tools/tests/lang-clisp
Bruno