+++ /dev/null
-<!DOCTYPE Article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
-
-<Article id="docbook-cheat-sheet">
-
-<ArtHeader>
-
-<Title>Using DocBook to write GHC documentation</Title>
-<Author><OtherName>The GHC Team</OtherName></Author>
-<Address><Email>glasgow-haskell-{users,bugs}@dcs.gla.ac.uk</Email></Address>
-<PubDate>January 2000</PubDate>
-
-</ArtHeader>
-
-
-<Sect1 id="sec-getting-docbook"><Title>Getting the DocBook tools</Title>
-
-<Para>
-See the installation guide.
-</Para>
-
-</Sect1>
-
-
-<Sect1 id="doc-layout"><Title>Document layout</Title>
-
-<Para>
-The GHC documentation is written using DocBook 3.1, so the DTD line should be:
-</Para>
-
-<Screen>
-<!DOCTYPE Article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
-</Screen>
-
-<Para> This guide is <Emphasis>not</Emphasis> meant to teach you how to
-write DocBook; read the <ULink URL="http://www.docbook.org/">DocBook
-book</ULink> for that. It is more of a reference than a tutorial, so see the
-<ULink URL="http://www.oasis-open.org/docbook/">DocBook home page</ULink>
-for other links. </Para>
-
-<Para> However, by popular demand, here are some useful points: </Para>
-
-<ItemizedList>
-<ListItem>
-<Para>Remember to use <SGMLTag class="StartTag">Para</SGMLTag> inside
-<SGMLTag class="StartTag">ListItem</SGMLTag>s.
-</Para>
-</ListItem>
-</ItemizedList>
-
-<Para> The rest of this section outlines the use of several tags which may
-not be obvious (DocBook is rather scholastic in style: it has tags for many
-things from C function prototypes to keyboard bindings; at the same time it
-has many omissions and oddities). The current scheme has many infelicities,
-partly because it was dreamt up in a hurry while the author was learning
-DocBook and converting the documentation thereto, and partly because DocBook
-is rather C-centric. </Para>
-
-<VariableList>
-
-<VarListEntry><Term>Comments</Term>
-<ListItem>
-<Para>
-Comments in SGML look like this: <SGMLTag class=SGMLComment>This is a
-comment</SGMLTag>.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">Command</SGMLTag></Term>
-<ListItem>
-<Para>
-Used for commands typed into interactive sessions (e.g. <Command>cp foo bar</Command> and the names of programs such as <Command>gmake</Command>.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">Constant</SGMLTag></Term>
-<ListItem>
-<Para>
-Used for system constants such as <Constant>U_MAXINT</Constant> and <Filename>Makefile</Filename> variables like <Constant>SRC_FILES</Constant> (because they are usually constant for a given run of <Command>make</Command>, and hence have a constant feel to them).
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">Email</SGMLTag></Term>
-<ListItem>
-<Para>
-For email addresses. This is a tag that's easy to overlook if you don't know it's there.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">Filename</SGMLTag></Term>
-<ListItem>
-<Para>
-Used for paths, filenames, file extensions.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">Function</SGMLTag></Term>
-<ListItem>
-<Para>
-Used for functions and constructors.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">IndexTerm</SGMLTag></Term>
-<ListItem>
-<Para>
-The normal way to mark up an index term is <Literal><IndexTerm><Primary>term</Primary></IndexTerm></Literal>.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">KeyCap</SGMLTag></Term><Term><SGMLTag class="StartTag">KeyCombo</SGMLTag></Term>
-<ListItem>
-<Para>
-Some more tags you may miss. Used for combinations such as <KeyCombo><KeyCap>Control</KeyCap><KeyCap>D</KeyCap></KeyCombo>.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">Literal</SGMLTag></Term>
-<ListItem>
-<Para>
-Used for everything that should appear in typewriter font that has no other obvious tag: types, monads, small snippets of program text that are formatted inline, and the like.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">Option</SGMLTag></Term>
-<ListItem>
-<Para>
-Used for compiler options and similar.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">ProgramListing</SGMLTag></Term>
-<ListItem>
-<Para>
-For displayed program listings (including shell scripts).
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">Screen</SGMLTag></Term>
-<ListItem>
-<Para>
-For displayed screen dumps, such as portions of shell interaction. It's easy to tell the difference between these and shell scripts: the latter lack a shell prompt.
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry><Term><SGMLTag class="StartTag">VarName</SGMLTag></Term>
-<ListItem>
-<Para>
-Used for variables, but not type variables.
-</Para>
-</ListItem>
-</VarListEntry>
-
-</VariableList>
-
-</Sect1>
-
-<Sect1 id="docbook-tables"><Title>Tables</Title>
-
-<Para>
-Tables are quite complicated to write in SGML (as in HTML, there are lots of fiddly tags), so here's an example you can cannibalise. In the spirit of the LaTeX short introduction I don't repeat all the markup verbatim; you have to look at the source for that.
-</Para>
-
-<Para>
-<InformalTable>
-<TGroup cols="3">
-<ColSpec Colname="one" Align="Left" Colsep="0">
-<ColSpec Colname="two" Align="Center" Colsep="0">
-<ColSpec Colname="three" Align="Right" Colsep="0">
-<TBody>
-
-<Row>
-<Entry>Here's</Entry>
-<Entry>a sample</Entry>
-<Entry>table</Entry>
-</Row>
-
-<Row>
-<Entry>With differently</Entry>
-<Entry>aligned</Entry>
-<Entry>cells</Entry>
-</Row>
-
-<Row>
-<Entry namest="one" nameend="three" morerows="1"><Para>
-There's not much else to it. Entries can span both extra rows and extra columns; just be careful when using block markup (such as <SGMLTag class="starttag">Para</SGMLTag>s) within an <SGMLTag class="starttag">Entry</SGMLTag> that there is no space between the open and close <SGMLTag class="starttag">Entry</SGMLTag> tags and the adjacent text, as otherwise you will suffer from <ULink URL="http://www.docbook.org/tdg/html/entry.html">Pernicious Mixed Content</ULink> (the parser will think you're using inline markup).</Para></Entry>
-</Row>
-
-</TBody>
-
-</TGroup>
-</InformalTable>
-</Para>
-
-</Sect1>
-
-</Article>
--- /dev/null
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+
+<article id="docbook-cheat-sheet">
+
+ <articleinfo>
+ <title>Using DocBook to write GHC documentation</title>
+ <author><othername>The GHC Team</othername></author>
+ <address><email>glasgow-haskell-{users,bugs}@dcs.gla.ac.uk</email></address>
+ <pubdate>January 2000</pubdate>
+ </articleinfo>
+
+ <sect1 id="sec-getting-docbook">
+ <title>Getting the DocBook tools</title>
+ <para>See the installation guide.</para>
+ </sect1>
+
+ <sect1 id="doc-layout">
+ <title>Document layout</title>
+
+ <para>The GHC documentation is written using DocBook XML V4.2, so
+ the first few lines should look like this:</para>
+
+<programlisting>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+</programlisting>
+
+ <para>The encoding can of course be chosen according to taste.</para>
+
+ <para> This guide is <emphasis>not</emphasis> meant to teach you
+ how to write DocBook; read the <ulink
+ url="http://www.docbook.org/">DocBook book</ulink> for that. It is
+ more of a reference than a tutorial, so see the <ulink
+ url="http://www.oasis-open.org/docbook/">DocBook home page</ulink>
+ for other links.</para>
+
+ <para>However, by popular demand, here are some useful points:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Remember to use <sgmltag class="starttag">para</sgmltag>
+ inside <sgmltag class="starttag">listitem</sgmltag>s.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>The rest of this section outlines the use of several tags
+ which may not be obvious (DocBook is rather scholastic in style:
+ it has tags for many things from C function prototypes to keyboard
+ bindings; at the same time it has many omissions and
+ oddities). The current scheme has many infelicities, partly
+ because it was dreamt up in a hurry while the author was learning
+ DocBook and converting the documentation thereto, and partly
+ because DocBook is rather C-centric.</para>
+
+ <variablelist>
+
+ <varlistentry>
+ <term>Comments</term>
+ <listitem>
+ <para>Comments in SGML look like this: <sgmltag
+ class="sgmlcomment">This is a comment</sgmltag>.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">command</sgmltag></term>
+ <listitem>
+ <para>Used for commands typed into interactive sessions
+ (e.g. <command>cp foo bar</command> and the names of
+ programs such as <command>gmake</command>.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">constant</sgmltag></term>
+ <listitem>
+ <para>Used for system constants such as
+ <constant>U_MAXINT</constant> and
+ <filename>Makefile</filename> variables like
+ <constant>SRC_FILES</constant> (because they are usually
+ constant for a given run of <command>make</command>, and
+ hence have a constant feel to them).</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">email</sgmltag></term>
+ <listitem>
+ <para>For email addresses. This is a tag that's easy to
+ overlook if you don't know it's there.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">filename</sgmltag></term>
+ <listitem>
+ <para>Used for paths, filenames, file extensions.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">function</sgmltag></term>
+ <listitem>
+ <para>Used for functions and constructors.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">indexterm</sgmltag></term>
+ <listitem>
+ <para>The normal way to mark up an index term is
+ <literal><indexterm><primary>term</primary></indexterm></literal>.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">keycap</sgmltag></term>
+ <term><sgmltag class="starttag">keycombo</sgmltag></term>
+ <listitem>
+ <para>Some more tags you may miss. Used for combinations
+ such as
+ <keycombo><keycap>Control</keycap><keycap>D</keycap></keycombo>.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">literal</sgmltag></term>
+ <listitem>
+ <para>Used for everything that should appear in typewriter
+ font that has no other obvious tag: types, monads, small
+ snippets of program text that are formatted inline, and the
+ like.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">option</sgmltag></term>
+ <listitem>
+ <para>Used for compiler options and similar.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">programlisting</sgmltag></term>
+ <listitem>
+ <para>For displayed program listings (including shell
+ scripts).</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">screen</sgmltag></term>
+ <listitem>
+ <para>For displayed screen dumps, such as portions of shell
+ interaction. It's easy to tell the difference between these
+ and shell scripts: the latter lack a shell prompt.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><sgmltag class="starttag">varname</sgmltag></term>
+ <listitem>
+ <para>Used for variables, but not type variables.</para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ </sect1>
+
+ <sect1 id="docbook-tables">
+ <title>Tables</title>
+
+ <para>Tables are quite complicated to write in SGML (as in HTML,
+ there are lots of fiddly tags), so here's an example you can
+ cannibalise. In the spirit of the LaTeX short introduction I don't
+ repeat all the markup verbatim; you have to look at the source for
+ that.</para>
+
+ <informaltable>
+ <tgroup cols="3">
+ <colspec colname="one" align="left" colsep="0"/>
+ <colspec colname="two" align="center" colsep="0"/>
+ <colspec colname="three" align="right" colsep="0"/>
+ <tbody>
+
+ <row>
+ <entry>Here's</entry>
+ <entry>a sample</entry>
+ <entry>table</entry>
+ </row>
+
+ <row>
+ <entry>With differently</entry>
+ <entry>aligned</entry>
+ <entry>cells</entry>
+ </row>
+
+ <row>
+ <entry namest="one" nameend="three" morerows="1">
+ <para> There's not much else to it. Entries can span
+ both extra rows and extra columns; just be careful when
+ using block markup (such as <sgmltag
+ class="starttag">para</sgmltag>s) within an <sgmltag
+ class="starttag">entry</sgmltag> that there is no space
+ between the open and close <sgmltag
+ class="starttag">entry</sgmltag> tags and the adjacent
+ text, as otherwise you will suffer from <ulink
+ url="http://www.docbook.org/tdg/html/entry.html">Pernicious
+ Mixed Content</ulink> (the parser will think you're
+ using inline markup).</para>
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </sect1>
+</article>
projects / ghc-hetmet.git / commitdiff