discuss: How to create a HOWTO on Red Hat Linux 9?
Subject:
Re: How to create a HOWTO on Red Hat Linux 9?
From:
"Rodolfo J. Paiz" ####@####.####
Date:
21 Oct 2003 01:52:53 -0000
Message-Id: <6.0.0.22.0.20031020194216.024e9d40@mail.simpaticus.com>
This email sent to both the "discuss" and "docbook" lists deliberately.
-----------------
For the discuss list: kindly review and offer feedback or comments on the
brief document located at
http://apollo.simpaticus.com/linux/howto/html-single/Sendmail-SMTP-AUTH-HOWTO.html
-----------------
For the docbook list, I have a couple of questions:
1. Where I present something the user should type in, I have used
the COMPUTEROUTPUT tag to show the shell prompt so it's not displayed in
bold, and then the USERINPUT tag to show what the user actually types.
However, it is then showing the output on two separate lines; is there a
way I can tell it not to do this?
2. There is a space between a paragraph and the gray area which
represents a SCREEN tag, but there is no space between the gray and the
next paragraph. How should I tag this so the spacing is symmetrical, before
and after?
3. There is always two or three lines of blank gray-shaded space
in a SCREEN tag. It starts out with text right on the first line, but
leaves blank gray after. Can I avoid this?
4. If I try to create multiple HTML pages instead of just one, the
filenames are "t1.html" and "x76.html" which seems very odd to me. Is there
no way to suggest "howto-1.html" and "howto-2.html" names? I remember the
old sgml-tools used to name them this way, and it seemed a much more
intuitive method to me.
5. The "onsgmls" parser/validator complains about the ARTHEADER
tag and is quiet if I change it to HEADER. However, the jade tool complains
about the HEADER tag. What am I doing wrong?
Whew... I think I'm finally getting to the point where this is close to
being presentable. Thanks to all of you for patience and help in tons of
questions; I would not have come close to progressing this quickly without you.
--
Rodolfo J. Paiz
####@####.####