Notes on the GNU Translation Project
************************************

   A few GNU packages provide native language translation for their
messages.  This chapter gives the installer some useful hints.  It
explains how users should proceed for getting the programs to use the
available translations.  It tells how people wanting to contribute and
work at translations should contact the appropriate team.

INSTALL matters
===============

   Some GNU packages are "localizable" when properly installed; the
programs they contain can be made to speak your own native language.
Most such packages use GNU `gettext'.  Some other packages have their
own ways to internationalization, predating GNU `gettext'.

   If you found this `NLS' file inside a GNU distribution, you may
assume that this distribution does use GNU `gettext', itself available
at your nearest GNU archive site.  By default, this package will be
installed to allow translation of messages.  It will automatically
detect whether the system provides usable `catgets' or `gettext'
functions.  If neither is present, the GNU `gettext' library will be
used.  Installers may use special options at configuration time for
changing this behaviour.  The commands:

     ./configure --with-gnu-gettext
     ./configure --disable-nls

will respectively bypass system `catgets' or `gettext' to use GNU
`gettext', or else, totally disable translation of messages.

   Internationalized packages have usually many `XX.po' files, where XX
gives an ISO 639 two-letter code identifying the language.  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 two-letter codes, stating
which languages are allowed.

   As a user, if your language has been installed for this package, you
only have to set the `LANG' environment variable to the appropriate
`XX' prior to using the programs in the package.  For example, let's
suppose that you speak German.  At the shell prompt, merely execute
`setenv LANG de' (in `csh') or `export LANG; LANG=de' (in `sh').  This
can be done from your `.login' or `.profile' file.

Translating teams
=================

   GNU is going international!  The GNU Translation Project is a way to
get maintainers, translators and users all together, so GNU will
gradually become able to speak many native languages.

   The GNU `gettext' tool set contains *everything* maintainers need
for internationalizing their packages for messages.  It also contains
quite useful tools for helping translators at localizing messages to
their native language, once a package has already been
internationalized.

   To achieve the GNU Translation Project, we need many interested
people who like their own language and write it well, and who are also
able to synergize with other translators speaking the same language.
If you'd like to volunteer to *work* at translating messages, please
send mail to your translating team.

   Each team has its own mailing list, courtesy of Linux International.
You may reach your translating team at the address `XX@li.org',
replacing XX by the two-letter ISO 639 code for your language.
Language codes are *not* the same as country codes given in ISO 3166.
The following translating teams exist, as of June 1995:

     Chinese (zh), Czech (cs), Danish (da), Dutch (nl), Esperanto (eo),
     Finnish (fi), French (fr), Irish (ga), German (de), Greek (el),
     Italian (it), Japanese (ja), Indonesian (in), Norwegian (no),
     Polish (pl), Portuguese (pt), Russian (ru), Spanish (es), Swedish
     (sv) and Turkish (tr).

For example, you may reach the Chinese translating team by writing to
`zh@li.org'.  When you become a member of the translating team for your
own language, you may subscribe to its list.  For example, Swedish
people can send a message to `sv-request@li.org', having this message
body:

     subscribe

   Keep in mind that team members should be interested in *working* at
translations, or at solving translational difficulties, rather than
merely lurking around.  If your team does not exist yet and you want to
start one, please write to `gnu-translation@prep.ai.mit.edu'; you will
then reach the GNU coordinator for all translator teams.

Available packages
==================

   Languages are not equally supported in all GNU packages.  The
following matrix shows the current state of GNU internationalization,
as of June 1995.  Listed are: internationalized packages, and languages
for which work is in progress, or about to start.

          See note    cs de es fi fr it ja nl pt sv
                \   .-------------------------------.
     chess      (4) |    *                       *  |
     clisp      (3) |    *        *                 |
     diffutils  (2) |    .        -                 |
     fileutils      |    -                          |
     flex       (1) |    .        -                 |
     m4         (2) |    +        +  +  -        +  |
     gettext        |    *        *                 |
     ptx        (2) |    +        +              +  |
     recode     (2) |    +  .     +        +  +     |
     sharutils  (2) |    +        +        +  +  +  |
     shellutils     |    -                          |
     tar            |    *     .  *     .     *  *  |
     wdiff      (2) | +  +        +  +              |
                    `-------------------------------'
                      cs de es fi fr it ja nl pt sv

   The interpretation legend is:

`.'
     interest shown, or invitation made

`-'
     being undertaken, or work in progress

`+'
     submitted, and now ready for pretest

`*'
     distributed through an official release

   Notes:

(1)
     This package has its translatable strings marked, but does not use
     GNU `gettext'.  A convenience patch may be available separately.

(2)
     This package is planned to switch to GNU `gettext'.  For the time
     being, it uses temporary means for internationalization.

(3)
     This package is translated to specific languages by methods
     predating GNU `gettext'.  Translations are kept in the sources and
     memory, rather than installed in external message catalogs.

(4)
     This package is translated to specific languages by methods
     predating GNU `gettext'.  Translations are all kept on disk files,
     and sources contain numbers where one normally expects strings.

   If June 1995 seems to be old, you may fetch a more recent copy of
this `NLS' file on most GNU archive sites.

