Alfred M. Szmidt wrote:
   Perhaps, instead of rewriting the wheel (heh), there could be links
   to the already existing documents, and the guide can contain
   conventions/commands/extras/etc.

Please don't use links (as in URL's) in manuals unless it is _really_
important.  Just to be able to read the link you need to have an
internet connection, and this is sometimes hard to get, or plain
impossible.

Using info references is OK, since one can install the document in
question on the harddisk, and it can be bundled with the software.
Isn't it even better to include both? If we say, "More information is available via info gcc.", then the information is only available to users of GNU systems, which means we're preaching to the choir.

Also, many people have access to non-UNIXish computers via work or school (I know I do, I first learned about the Hurd using an NT box), so including a hyperlink can be quite helpful.

--
_______________________________________________
/ |
/ Tom Hart |
| [EMAIL PROTECTED] |
\ "rmTFM - Build consistent interfaces." |
\_______________________________________________|



_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd

Reply via email to