aboutsummaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-10-05 15:26:17 +0000
committerUlrich Drepper <drepper@redhat.com>1999-10-05 15:26:17 +0000
commita2d63612259fb70828b95b982ba21f1d01abe802 (patch)
treeebb126208f2eabd907e14ccfe62bfc08d81f3d91 /manual
parent479620b96e2815b9f77079b44fe4a46f688d33ca (diff)
downloadglibc-a2d63612259fb70828b95b982ba21f1d01abe802.tar
glibc-a2d63612259fb70828b95b982ba21f1d01abe802.tar.gz
glibc-a2d63612259fb70828b95b982ba21f1d01abe802.tar.bz2
glibc-a2d63612259fb70828b95b982ba21f1d01abe802.zip
Update.
1999-10-05 Andreas Jaeger <aj@suse.de> * manual/message.texi (The message catalog files): Fix description to match gencat implementation and Unix98: Message fields are separated by a single blank space. 1999-10-05 Andreas Jaeger <aj@suse.de> * manual/string.texi (Search Functions): Add missing end for memrchr description.
Diffstat (limited to 'manual')
-rw-r--r--manual/message.texi6
-rw-r--r--manual/string.texi1
2 files changed, 2 insertions, 5 deletions
diff --git a/manual/message.texi b/manual/message.texi
index 8e12dc8f56..294b9f0a77 100644
--- a/manual/message.texi
+++ b/manual/message.texi
@@ -374,7 +374,7 @@ be escaped using the backslash (i.e., @code{\"} must be written).
@item
Any other line must start with a number or an alphanumeric identifier
(with the underscore character included). The following characters
-(starting at the first non-whitespace character) will form the string
+(starting after the first whitespace character) will form the string
which gets associated with the currently selected set and the message
number represented by the number and identifier respectively.
@@ -390,10 +390,6 @@ identifiers will be explained below (@pxref{Common Usage}). There is
one limitation with the identifier: it must not be @code{Set}. The
reason will be explained below.
-Please note that you must use a quoting character if a message contains
-leading whitespace. Since one cannot guarantee this never happens it is
-probably a good idea to always use quoting.
-
The text of the messages can contain escape characters. The usual bunch
of characters known from the @w{ISO C} language are recognized
(@code{\n}, @code{\t}, @code{\v}, @code{\b}, @code{\r}, @code{\f},
diff --git a/manual/string.texi b/manual/string.texi
index 2d28dd2e47..8d2a33ea1a 100644
--- a/manual/string.texi
+++ b/manual/string.texi
@@ -1068,6 +1068,7 @@ located byte, or a null pointer if no match was found.
The function @code{memrchr} is like @code{memchr}, except that it searches
backwards from the end of the block defined by @var{block} and @var{size}
(instead of forwards from the front).
+@end deftypefun
@comment string.h
@comment ISO