Mail Archives: djgpp-workers/2001/01/21/12:34:21
Hello.
Eli Zaretskii wrote:
> It might be better to use @acronym for ANSI and POSIX. It's not a
> requirement, though; it's up to you. (Personally, I think @acronym
> looks much better in print.)
'@acronym' appeared in texinfo 4.0, according to the news file
(gnu/texinfo4.0/news). Do we require texinfo 4.0 to build DJGPP now?
> This cross-reference won't work. You need a 4-argument form of
> @pxref, not a 3-argument form. See the Texinfo manual, under @xref.
Thanks, I've fixed & tested those links now. There's a new diff below. OK
to commit now?
Thanks, bye, Rich =]
*** src/docs/kb/develop.txi.orig Sun Jan 21 15:25:48 2001
--- src/docs/kb/develop.txi Sun Jan 21 17:26:34 2001
***************
*** 96,101 ****
--- 96,127 ----
@end itemize
@item
+ Under the subheading @samp{Portability}, @samp{@@portability} should be
+ used to indicate whether a feature is specified in the ANSI C and POSIX
+ standards. For example:
+
+ @example
+ @@subheading Portability
+
+ @@portability !ansi, posix
+ @end example
+
+ Please note that @samp{@@portability} is not used to indicate whether
+ the DJGPP implementation complies with the standards listed. Instead,
+ @samp{@@port-note} may be used to describe implementation-specific
details:
+
+ @example
+ @@port-note ansi The buffer size limit is imposed by DJGPP.
+ @end example
+
+ @samp{@@portability} and @samp{@@port-note} are DJGPP-specific
extensions
+ of texinfo (@pxref{Top, , texinfo, texinfo}) that are expanded into
normal
+ texinfo by @code{mkdoc}. @code{mkdoc} is part of the DJGPP sources. It
is
+ used to build the C library documentation (@pxref{Top, , libc, libc}).
+ Therefore, @samp{@@portability} and @samp{@@port-note} should only be
used
+ in DJGPP's C library documentation.
+
+ @item
Finally, for some relevant texinfo technique, look at the source
of this page in the DJGPP sources--- AT file{src/docs/kb/contrib.txi}.
@end itemize
- Raw text -