>DO NOT edit these directly</I
></SPAN
>. Edit the SGML source, or
>DO NOT edit these directly</I
></SPAN
>. Edit the SGML source, or
</P
><P
> Packagers are encouraged to include this documentation. For those without
the ability to build the docs locally, text versions of each are kept in
</P
><P
> Packagers are encouraged to include this documentation. For those without
the ability to build the docs locally, text versions of each are kept in
>. 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
- are just plain text, TML, and PDF, but others are always a
+ are just plain text, HTML, and PDF, but others are always a
>"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.