NameDateSize

..Today15

aclocal.m4H A D29-Apr-200519.4 KiB

AUTHORSH A D29-Apr-2005575

autoconf-lib-link/H12-Oct-201517

autogen.shH A D29-Apr-20051.6 KiB

build-aux/H12-Oct-201519

ChangeLogH A D29-Apr-200513.3 KiB

ChangeLog.0H A D29-Apr-200550.9 KiB

configureH A D29-Apr-200599 KiB

configure.acH A D29-Apr-20052.2 KiB

COPYINGH A D29-Apr-200517.6 KiB

djgpp/H12-Oct-201520

gettext-runtime/H12-Oct-201533

gettext-tools/H12-Oct-201534

gettext2netbsdH A D30-Apr-20082.1 KiB

INSTALLH A D29-Apr-200510.4 KiB

m4/H12-Oct-20155

Makefile.amH A D29-Apr-20052.1 KiB

Makefile.inH A D15-May-200518.6 KiB

Makefile.msvcH A D29-Apr-20053.6 KiB

Makefile.vmsH A D29-Apr-20052.2 KiB

NEWSH A D29-Apr-200519.7 KiB

os2/H12-Oct-20157

PACKAGINGH A D29-Apr-20056.3 KiB

READMEH A D29-Apr-20055.1 KiB

README.mingwH A D29-Apr-2005392

README.vmsH A D29-Apr-2005139

README.woe32H A D29-Apr-20052.8 KiB

THANKSH A D29-Apr-20059 KiB

version.shH A D29-Apr-2005115

vms/H12-Oct-20156

README

1This is the GNU gettext package.  It is interesting for authors or
2maintainers of other packages or programs which they want to see
3internationalized.  As one step the handling of messages in different
4languages should be implemented.  For this task GNU gettext provides
5the needed tools and library functions.
6
7Users of GNU packages should also install GNU gettext because some
8other GNU packages will use the gettext program included in this
9package to internationalize the messages given by shell scripts.
10
11Another good reason to install GNU gettext is to make sure the
12here included functions compile ok.  This helps to prevent errors
13when installing other packages which use this library.  The message
14handling functions are not yet part of POSIX and ISO/IEC standards
15and therefore it is not possible to rely on facts about their
16implementation in the local C library.  For this reason, GNU gettext
17tries using the system's functionality only if it is a GNU gettext
18implementation (possibly a different version); otherwise, compatibility
19problems would occur.
20
21We felt that the Uniforum proposals has the much more flexible interface
22and, what is more important, does not burden the programmers as much as
23the other possibility does.
24
25
26Please share your results with us.  If this package compiles ok for
27you future GNU release will likely also not fail, at least for reasons
28found in message handling.  Send comments and bug reports to
29		bug-gnu-gettext@gnu.org
30
31
32The goal of this library was to give a unique interface to message
33handling functions.  At least the same level of importance was to give
34the programmer/maintainer the needed tools to maintain the message
35catalogs.  The interface is designed after the proposals of the
36Uniforum group.
37
38
39The homepage of this package is at
40
41           http://www.gnu.org/software/gettext/
42
43The primary FTP site for its distribution is
44
45           ftp://ftp.gnu.org/pub/gnu/gettext/
46
47
48The configure script provides two non-standard options.  These will
49also be available in other packages if they use the functionality of
50GNU gettext.  Use
51
52	--disable-nls
53
54if you absolutely don't want to have messages handling code.  You will
55always get the original messages (mostly English).  You could consider
56using NLS support even when you do not need other tongues.  If you do
57not install any messages catalogs or do not specify to use another but
58the C locale you will not get translations.
59
60The set of languages for which catalogs should be installed can also be
61specified while configuring.  Of course they must be available but the
62intersection of these two sets are computed automatically.  You could
63once and for all define in your profile/cshrc the variable LINGUAS:
64
65(Bourne Shell)		LINGUAS="de fr nl"; export LINGUAS
66
67(C Shell)		setenv LINGUAS "de fr nl"
68
69or specify it directly while configuring
70
71	env LINGUAS="de fr nl" ./configure
72
73Consult the manual for more information on language names.
74
75The second configure option is
76
77	--with-included-gettext
78
79This forces to use the GNU implementation of the message handling library
80regardless what the local C library provides.  This possibility is
81useful if the local C library is a glibc 2.1.x or older, which didn't
82have all the features the included libintl has.
83
84
85Other files you might look into:
86
87`ABOUT-NLS' -	current state of the GNU internationalization effort
88`COPYING' -	copying conditions
89`INSTALL' -	general compilation and installation rules
90`NEWS' -	major changes in the current version
91`THANKS' -	list of contributors
92
93
94Some points you might be interested in before installing the package:
95
961.  If your system's C library already provides the gettext interface
97    and its associated tools don't come from this package, it might be
98    a good idea to configure the package with
99    --program-transform-name='s/^gettext$/g&/;s/^msgfmt$/g&/;s/^xgettext$/g&/'
100
101    Systems affected by this are:
102        Solaris 2.x
103
1042.  Some system have a very dumb^H^H^H^Hstrange version of msgfmt, the
105    one which comes with xview.  This one is *not* usable.  It's best
106    you delete^H^H^H^H^H^Hrename it or install this package as in the
107    point above with
108    --program-transform-name='s/^gettext$/g&/;s/^msgfmt$/g&/;s/^xgettext$/g&/'
109
1103.  The locale name alias scheme implemented here is in a similar form
111    implemented in the X Window System.  Especially the alias data base
112    file can be shared.  Normally this file is found at something like
113
114	/usr/lib/X11/locale/locale.alias
115
116    If you have the X Window System installed try to find this file and
117    specify the path at the make run:
118
119    make aliaspath='/usr/lib/X11/locale:/usr/local/lib/locale'
120
121    (or whatever is appropriate for you).  The file name is always
122    locale.alias.
123    In the misc/ subdirectory you find an example for an alias database file.
124
1254.  The msgmerge program performs fuzzy search in the message sets.  It
126    might run a long time on slow systems.  I saw this problem when running
127    it on my old i386DX25.  The time can really be several minutes,
128    especially if you have long messages and/or a great number of
129    them.
130       If you have a faster implementation of the fstrcmp() function and
131    want to share it with the rest of us, please contact me.
132

README.mingw

1Installation on Mingw32:
2
3See file INSTALL.
4
5When configuring with the default options, the build will attempt to create
6shared libraries and fail because libtool 1.4.3 does not support shared
7libraries on Mingw32.  To remedy:
8  - Either configure with option --disable-shared, to create non-shared
9    libraries only.
10  - Or update this package with the libtool CVS, and configure normally.
11

README.vms

1Installation on VMS:
2
3- Build instructions:
4
5  $ mms /description=Makefile.vms
6
7- Installation:
8
9  $ mms /description=Makefile.vms install
10

README.woe32

1Installation on Woe32 (WinNT/2000/XP, Win95/98/ME):
2
3- Requires MS Visual C/C++ 4.0 or 5.0 or 6.0 or 7.0.
4
5  Note that binaries created with MSVC 7.0 should not be distributed: They
6  depend on a closed-source library 'msvcr70.dll' which is not normally part
7  of a Woe32 installation. You cannot distribute 'msvcr70.dll' with the
8  binaries - this would be a violation of the GPL and of the Microsoft EULA.
9  You can distribute the binaries without including 'msvcr70.dll', but this
10  will cause problems for users that don't have this library on their system.
11  Therefore it is not recommended. This problem does not occur with MSVC 6.0
12  and earlier.
13
14- Cannot build in a separate directory.
15
16- Build instructions:
17
18   Make sure that the MSVC4.0 or MSVC5.0 or MSVC6.0 or MSVC7.0 utilities
19   ("cl" etc.) are found in PATH. In a typical MSVC6.0 installation, this
20   can be achieved by running
21        C:\Program Files\Microsoft Visual Studio\VC98\bin\vcvars32.bat
22   In a typical MSVC7.0 installation, it can be achieved by running
23        C:\Program Files\Microsoft Visual Studio .NET\Common7\Tools\vsvars32.bat
24
25   Decide which compilation model you will use:
26     MFLAGS=-ML (the default)  Single-threaded, statically linked - libc.lib
27     MFLAGS=-MT                Multi-threaded, statically linked  - libcmt.lib
28     MFLAGS=-MD                Multi-threaded, dynamically linked - msvcrt.lib
29
30   You need GNU libiconv (version 1.9 or newer) installed under c:\usr. If
31   you haven't yet, build and install GNU libiconv (version 1.9 or newer)
32   using the same MFLAGS. Then come back to here, to build GNU gettext.
33
34   For shared library (DLL):
35
36        nmake -f Makefile.msvc DLL=1 MFLAGS=-MD
37
38   For static library:
39
40        nmake -f Makefile.msvc MFLAGS=-MD
41
42   If you want to build both the shared and static library, you have to
43   unpack the gettext sources twice in different directories. Don't mix
44   the two formats; you cannot use the libintl.h generated for the static
45   library together with the shared library or vice versa.
46
47   Install it:
48
49         nmake -f Makefile.msvc DLL=1 MFLAGS=-MD install
50   or
51         nmake -f Makefile.msvc MFLAGS=-MD install
52
53- Installation:
54
55   Complete and automatic installation:
56
57         nmake -f Makefile.msvc DLL=1 MFLAGS=-MD install PREFIX=InstallBaseDirectory
58      or
59         nmake -f Makefile.msvc MFLAGS=-MD install PREFIX=InstallBaseDirectory
60
61      By default, the compiled package is installed under c:\usr. You can
62      specify a different directory by giving the installation base directory
63      in a PREFIX=... option in the install step. (DON'T give the PREFIX
64      already in the build step! This won't work.) You can also omit the
65      PREFIX=... option, thus installing everything under c:\usr, and then
66      move the installed package as a whole from c:\usr to a different
67      location.
68