mirror of
https://https.git.savannah.gnu.org/git/gettext.git
synced 2026-01-26 15:39:11 +00:00
6b40c1fa79
The common way to distribute information, nowadays, is through the web, not by including files in tarballs of packages. Also, the current contents of ABOUT-NLS is outdated. Reported by Samuel Thibault in <https://savannah.gnu.org/bugs/?54809>. * gettext-runtime/ABOUT-NLS: Replace text with a reference to the online documentation. * gettext-runtime/Makefile.am (MAKEINFO): Remove variable. (all-local, ABOUT-NLS): Remove rules. * gettext-tools/src/msginit.c (main): Point the user to the online documentation instead of the ABOUT-NLS file. * gettext-tools/doc/gettext.texi (Installing Localizations, Prerequisites, Makefile): Don't mention ABOUT-NLS any more. * gettext-tools/doc/gettextize.texi: Update description of ABOUT-NLS. * gettext-tools/doc/FAQ.html: Refer to the online documentation instead of the ABOUT-NLS file. * README: Don't mention ABOUT-NLS any more.
64 lines
2.2 KiB
Plaintext
64 lines
2.2 KiB
Plaintext
This is the GNU gettext package. It is interesting for authors or
|
|
maintainers of other packages or programs which they want to see
|
|
internationalized. As one step the handling of messages in different
|
|
languages should be implemented. For this task GNU gettext provides
|
|
the needed tools and library functions.
|
|
|
|
It is also interesting for translators, because GNU gettext provides
|
|
the 'msgmerge' program, which prepares a message catalog before a
|
|
translation update.
|
|
|
|
Users of GNU packages should also install GNU gettext because some
|
|
other GNU packages will use the gettext program included in this
|
|
package to internationalize the messages given by shell scripts.
|
|
|
|
|
|
The homepage of this package is at
|
|
|
|
https://www.gnu.org/software/gettext/
|
|
|
|
The primary FTP site for its distribution is
|
|
|
|
https://ftp.gnu.org/pub/gnu/gettext/
|
|
|
|
|
|
Send comments and bug reports to
|
|
bug-gnu-gettext@gnu.org
|
|
|
|
|
|
The configure script provides a non-standard option. It is also
|
|
available in other packages that use the functionality of GNU gettext.
|
|
Use
|
|
|
|
--disable-nls
|
|
|
|
if you absolutely don't want to have messages handling code. You will
|
|
always get the original messages (mostly English). You could consider
|
|
using NLS support even when you do not need other tongues. If you do
|
|
not install any messages catalogs or do not specify to use another but
|
|
the C locale you will not get translations.
|
|
|
|
The set of languages for which catalogs should be installed can also be
|
|
specified while configuring. Of course they must be available but the
|
|
intersection of these two sets are computed automatically. You could
|
|
once and for all define in your profile/cshrc the variable LINGUAS:
|
|
|
|
(Bourne Shell) LINGUAS="de fr nl"; export LINGUAS
|
|
|
|
(C Shell) setenv LINGUAS "de fr nl"
|
|
|
|
or specify it directly while configuring
|
|
|
|
env LINGUAS="de fr nl" ./configure
|
|
|
|
Consult the manual for more information on language names.
|
|
|
|
|
|
Other files you might look into:
|
|
|
|
COPYING - copying conditions
|
|
DEPENDENCIES - list of prerequisite packages, to be installed before this one
|
|
INSTALL - general compilation and installation rules
|
|
NEWS - major changes in the current version
|
|
THANKS - list of contributors
|