Update.

	* iconvdata/Makefile (modules): Add GBBIG5.
	(distribute): Add gbbig5.c.
	* iconvdata/gbbig5.c: New file.
	* iconvdata/gconv-modules: Add entries for GBBIG5 module.

2001-02-13  Philip Blundell  <pb@futuretv.com>

	* manual/crypt.texi: Remove outdated references to crypt add-on.

	* manual/creature.texi: Improve wording slightly.

2001-02-13  Ulrich Drepper  <drepper@redhat.com>

2 files changed, 13 insertions, 23 deletions

diff --git a/manual/creature.texi b/manual/creature.texi
index 5247d7192d..c825edd5ae 100644
--- a/manual/creature.texi
+++ b/manual/creature.texi
@@ -131,7 +131,7 @@ Single Unix Specification, @w{version 2}.
 @comment X/Open
 @defvr Macro _LARGEFILE_SOURCE
 If this macro is defined some extra functions are available which
-rectify a few shortcomings in all previous standards.  More concrete
+rectify a few shortcomings in all previous standards.  Specifically,
 the functions @code{fseeko} and @code{ftello} are available.  Without
 these functions the difference between the @w{ISO C} interface
 (@code{fseek}, @code{ftell}) and the low-level POSIX interface
@@ -156,16 +156,16 @@ contain @code{64} to indicate the intention, e.g., @code{off_t}
 vs. @code{off64_t} and @code{fseeko} vs. @code{fseeko64}.
 
 This macro was introduced as part of the Large File Support extension
-(LFS).  It is a transition interface for the time @w{64 bit} offsets are
-not generally used (see @code{_FILE_OFFSET_BITS}).
+(LFS).  It is a transition interface for the period when @w{64 bit}
+offsets are not generally used (see @code{_FILE_OFFSET_BITS}).
 @end defvr
 
 @comment (NONE)
 @comment X/Open
 @defvr Macro _FILE_OFFSET_BITS
 This macro determines which file system interface shall be used, one
-replacing the other.  While @code{_LARGEFILE64_SOURCE} makes the @w{64
-bit} interface available as an additional interface
+replacing the other.  Whereas @code{_LARGEFILE64_SOURCE} makes the @w{64
+bit} interface available as an additional interface,
 @code{_FILE_OFFSET_BITS} allows the @w{64 bit} interface to
 replace the old interface.
 
@@ -176,9 +176,9 @@ systems.
 
 If the macro is defined to the value @code{64}, the large file interface
 replaces the old interface.  I.e., the functions are not made available
-under different names as @code{_LARGEFILE64_SOURCE} does.  Instead the
-old function names now reference the new functions, e.g., a call to
-@code{fseeko} now indeed calls @code{fseeko64}.
+under different names (as they are with @code{_LARGEFILE64_SOURCE}).
+Instead the old function names now reference the new functions, e.g., a
+call to @code{fseeko} now indeed calls @code{fseeko64}.
 
 This macro should only be selected if the system provides mechanisms for
 handling large files.  On @w{64 bit} systems this macro has no effect
diff --git a/manual/crypt.texi b/manual/crypt.texi
index 2e08abe753..68ae6dd651 100644
--- a/manual/crypt.texi
+++ b/manual/crypt.texi
@@ -152,14 +152,11 @@ For the DES-based algorithm, the @var{salt} should consist of two
 characters from the alphabet @code{./0-9A-Za-z}, and the result of
 @code{crypt} will be those two characters followed by 11 more from the
 same alphabet, 13 in total.  Only the first 8 characters in the
-@var{key} are significant.  If the @code{crypt} add-on is not installed,
-trying to use the DES-based algorithm will return an empty string and
-set @code{errno} to @code{EOPNOTSUPP}.
+@var{key} are significant.
 
-The MD5-based algorithm is available in the GNU C library even if the
-@code{crypt} add-on is not installed.  It also has no limit on the
-useful length of the password used, and is slightly more secure.  It is
-therefore preferred over the DES-based algorithm.
+The MD5-based algorithm has no limit on the useful length of the
+password used, and is slightly more secure.  It is therefore preferred
+over the DES-based algorithm.
 
 When the user enters their password for the first time, the @var{salt}
 should be set to a new string which is reasonably random.  To verify a
@@ -271,11 +268,6 @@ The @code{setkey_r} and @code{encrypt_r} functions are GNU extensions.
 @code{setkey}, @code{encrypt}, @code{setkey_r}, and @code{encrypt_r} are
 defined in @file{crypt.h}.
 
-If the @code{crypt} add-on is not used to build the library, programs
-that use these four functions will crash when the functions are called.
-If this is a problem, the @code{ecb_crypt} function described below is
-recommended instead.
-
 @comment rpc/des_crypt.h
 @comment SUNRPC
 @deftypefun int ecb_crypt (char *@var{key}, char *@var{blocks}, unsigned @var{len}, unsigned @var{mode})
@@ -340,9 +332,7 @@ The encryption succeeded, but there was no hardware device available.
 @comment rpc/des_crypt.h
 @comment SUNRPC
 @item DESERR_HWERROR
-The encryption failed because of a hardware problem.  In the GNU
-library, this error code is also returned if the @code{crypt} add-on was
-not used to build the library.
+The encryption failed because of a hardware problem.
 
 @comment rpc/des_crypt.h
 @comment SUNRPC