><P
> If you are not familiar with SGML, it is a markup language similar to HTML.
Actually, not a mark up language per se, but a language used to define
><P
> If you are not familiar with SGML, it is a markup language similar to HTML.
Actually, not a mark up language per se, but a language used to define
>. They are also case-insensitive, but we
strongly suggest using all lower case. This keeps compatibility with
[Docbook] <SPAN
>. They are also case-insensitive, but we
strongly suggest using all lower case. This keeps compatibility with
[Docbook] <SPAN
>. There is a limit of five section
levels in Docbook, but generally three should be sufficient for our
purposes.</P
>. There is a limit of five section
levels in Docbook, but generally three should be sufficient for our
purposes.</P
><screen></screen></I
></SPAN
>, screen output, implies
><screen></screen></I
></SPAN
>, screen output, implies
><P
> It will be easier if everyone follows a similar writing style. This
just makes it easier to read what someone else has written if it
><P
> It will be easier if everyone follows a similar writing style. This
just makes it easier to read what someone else has written if it
>"internal entities"</SPAN
>. These are like variables in
programming. Well, sort of. For instance, we have the
>"internal entities"</SPAN
>. These are like variables in
programming. Well, sort of. For instance, we have the
>supported.sgml</TT
> is available for inclusion anywhere
in the doc. To make this happen, just reference the now defined
>supported.sgml</TT
> is available for inclusion anywhere
in the doc. To make this happen, just reference the now defined
> (starts with an ampersand
and ends with a semi-colon), and the contents will be dumped into
the finished doc at that point.
> (starts with an ampersand
and ends with a semi-colon), and the contents will be dumped into
the finished doc at that point.