Next: Other Programming Languages, Previous: The Maintainer’s View, Up: GNU gettext utilities [Contents][Index]
By default, packages fully using GNU gettext, internally,
are installed in such a way as to allow translation of
messages. At configuration time, those packages should
automatically detect whether the underlying host system already provides
the GNU gettext functions. If not,
the GNU gettext library should be automatically prepared
and used. Installers may use special options at configuration
time for changing this behavior. The command ‘./configure
--with-included-gettext’ bypasses system gettext to
use the included GNU gettext instead,
while ‘./configure --disable-nls’
produces programs totally unable to translate messages.
Internationalized packages have usually many ll.po or ll_CC.po files, where
Unless translations are disabled, all those available are installed together
with the package. However, the environment variable LINGUAS
may be set, prior to configuration, to limit the installed set.
LINGUAS should then contain a space separated list of locale names
(of the form ll or ll_CC),
stating which languages or language variants are allowed.
GNU gettext uses *.its and *.loc files (see Preparing Rules for XML Internationalization)
from other packages, provided they are installed in
prefix/share/gettext/its/,
where prefix is the value of the --prefix option
passed to gettext’s configure script.
So, this is the canonical location for installing *.its and *.loc files
from other packages.
Next: Other Programming Languages, Previous: The Maintainer’s View, Up: GNU gettext utilities [Contents][Index]