Lines Matching refs:GNU
10 assume that the distributed package does use GNU `gettext' internally,
11 itself available at your nearest GNU archive site. But you do _not_
12 need to install GNU `gettext' prior to configuring, installing or using
36 the `gettext' implementation in the GNU C library version 2 provides as
40 of a `catgets' implementation. Future versions of GNU `gettext' will
42 to change to GNU `gettext' as soon as possible.
44 So you need _not_ provide this option if you are using GNU libc 2 or
45 you have installed a recent copy of the GNU gettext package with the
53 packages use GNU `gettext'. Other packages have their own ways to
54 internationalization, predating GNU `gettext'.
58 provides the GNU `gettext' functions. If not, the GNU `gettext' own
61 the GNU `gettext' package is _not_ required. Installers may use
72 When you already have GNU `gettext' installed on your system and run
76 should use the more recent version of the GNU `gettext' library. I.e.
87 extensions of the GNU `gettext' library.
118 on GNU libc. On other systems, some variations of this scheme are
127 `LANGUAGE'. GNU `gettext' gives preference to `LANGUAGE' over `LANG'
746 this `ABOUT-NLS' file on most GNU archive sites. The most up-to-date
754 internationalize it you are welcome to use GNU `gettext' in your
755 package. Of course you have to respect the GNU Library General Public
756 License which covers the use of the GNU `gettext' library. This means
764 developed inside the GNU project. Therefore the information given above