+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.
+
1999-10-04 Ulrich Drepper <drepper@cygnus.com>
* malloc/memprof.sh: Various small cleanups. Add short options.
@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.
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},
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