summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorBruno Haible <bruno@clisp.org>2001-01-18 16:51:39 +0000
committerBruno Haible <bruno@clisp.org>2001-01-18 16:51:39 +0000
commit82eef2caf35fb2fb965e36ee431f4042c2b3bcec (patch)
tree7fab29e9abab66b2cfee14a7ad0d610d46867b4b /README
parenta7a991ef5dcd4db939e5a90957a431544d1864d8 (diff)
downloadexternal_gettext-82eef2caf35fb2fb965e36ee431f4042c2b3bcec.zip
external_gettext-82eef2caf35fb2fb965e36ee431f4042c2b3bcec.tar.gz
external_gettext-82eef2caf35fb2fb965e36ee431f4042c2b3bcec.tar.bz2
Remove catgets fallback code.
Diffstat (limited to 'README')
-rw-r--r--README55
1 files changed, 14 insertions, 41 deletions
diff --git a/README b/README
index 66c49ed..08d1836 100644
--- a/README
+++ b/README
@@ -13,9 +13,10 @@ here included functions compile ok. This helps to prevent errors
when installing other packages which use this library. The message
handling functions are not yet part of POSIX and ISO/IEC standards
and therefore it is not possible to rely on facts about their
-implementation in the local C library. If the installer selects
-it, GNU gettext tries using the systems functionality; in that
-case, compatibility problems might occur.
+implementation in the local C library. For this reason, GNU gettext
+tries using the system's functionality only if it is a GNU gettext
+implementation (possibly a different version); otherwise, compatibility
+problems would occur.
We felt that the Uniforum proposals has the much more flexible interface
and, what is more important, does not burden the programmers as much as
@@ -32,15 +33,9 @@ The goal of this library was to give a unique interface to message
handling functions. At least the same level of importance was to give
the programmer/maintainer the needed tools to maintain the message
catalogs. The interface is designed after the proposals of the
-Uniforum group. So systems having this interface implemented in their
-C library don't need the library provided here (and it will
-automatically not be included). If your systems C library implements
-the second widely available approach (X/Opens catgets) the library
-can use this and only some stubs will be compiled to provide the
-needed interface. If neither is locally available a full
-implementation of the library will be compiled.
-
-The configure script provides three non-standard options. These will
+Uniforum group.
+
+The configure script provides two non-standard options. These will
also be available in other packages if they use the functionality of
GNU gettext. Use
@@ -71,27 +66,10 @@ The second configure option is
--with-included-gettext
-This forces to use the GNU implementing the message handling library
+This forces to use the GNU implementation of the message handling library
regardless what the local C library provides. This possibility is
-much less error prone because possible unreliable effects of the local
-message handling system are avoided. And perhaps more important: many
-useful features can only be exploited with this library. The reason
-is obvious: we cannot dig in the internals of other implementations.
-It is likely that the discrepancy between the GNU implementation and
-others will get bigger in the time coming. So better change now!
-
-The third option is:
-
- --with-catgets
-
-The X/Open catgets functions which might be found in the local C
-library are not used by default. The reason is already described
-above: the GNU gettext library provides many useful extension which
-cannot be emulated with catgets(). Beside this the utility programs
-for generating the catalog used by catgets() vary heavily between
-different systems. You should select this feature only if you really
-don't want to use the GNU gettext library and do not want to extended
-functionality (but I do not see any good reason for such a choice).
+useful if the local C library is a glibc 2.1.x or older, which didn't
+have all the features the included libintl has.
Other files you might look into:
@@ -119,16 +97,12 @@ Some points you might be interested in before installing the package:
will recognize GNU message catalog files (.mo files).
3. If your system's C library already provides the gettext interface
- it might be a good idea to configure the package with
+ and its associated tools don't come from this package, it might be
+ a good idea to configure the package with
--program-prefix=g
Systems affected by this are:
- Solaris 2.x, future GNU and GNU/Linux systems
-
- One point to mention here is that at least Solaris 2.3 does not have
- all function of the Uniforum proposal implement. More specific, the
- dcgettext() function is missing. For programmers/maintainers it
- is therefore nowaday better to avoid using this function.
+ Solaris 2.x
4. Some system have a very dumb^H^H^H^Hstrange version of msgfmt, the
one which comes with xview. This one is *not* usable. It's best
@@ -140,8 +114,7 @@ Some points you might be interested in before installing the package:
Sparcs like strings aligned to 8 byte boundaries). If you want to
have the output of msgfmt aligned you can use the -a option. But you
also could change the default value to be different from 1. Take
- a look at the config.h file, built by configure.
- (If you change the default value the test of msgfmt will fail!)
+ a look at the --alignment option of msgfmt.
6. The locale name alias scheme implemented here is in a similar form
implemented in the X Window System. Especially the alias data base