Mail Archives: djgpp-workers/2003/01/19/13:20:05
Hello.
Eli Zaretskii wrote:
>
> > Date: Sun, 19 Jan 2003 08:21:43 -0500
> > From: "cvs-richdawe AT delorie DOT com" <cvs AT delorie DOT com>
> >
> > + The original OpenBSD paper describing @code{strlcpy}
> > + and @code{strlcat} (@pxref{strlcat}) is available on the web:
> > + @url{http://www.openbsd.org/papers/strlcpy-paper.ps}.
>
> Please use @uref rather than @url. The former is much more useful in
> the HTML format, and doesn't lose anything in the other formats.
Thanks. I've fixed it now.
> (The Texinfo maintainer wants to deprecate @url anyway.)
How about the diff below, to add some info to the developers' section of the
Knowledge Base?
Thanks, bye, Rich =]
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
Index: develop.txi
===================================================================
RCS file: /cvs/djgpp/djgpp/src/docs/kb/develop.txi,v
retrieving revision 1.13
diff -p -u -3 -r1.13 develop.txi
--- develop.txi 27 Jan 2002 14:43:57 -0000 1.13
+++ develop.txi 19 Jan 2003 18:17:32 -0000
@@ -297,6 +297,11 @@ correctly:
@end itemize
@item
+Use @code{@@uref} to refer to a URL. texinfo also has @code{@@url}
+for inserting URLs, but @code{@@uref} is more useful when texinfo
+is formatted into HTML. @code{@@url} may also be deprecated soon.
+
+@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:
- Raw text -