79 lines
3.5 KiB
HTML
79 lines
3.5 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|
<TITLE>LinuxDoc+Emacs+Ispell-HOWTO: Introduction</TITLE>
|
|
<LINK HREF="LinuxDoc+Emacs+Ispell-HOWTO-3.html" REL=next>
|
|
<LINK HREF="LinuxDoc+Emacs+Ispell-HOWTO-1.html" REL=previous>
|
|
<LINK HREF="LinuxDoc+Emacs+Ispell-HOWTO.html#toc2" REL=contents>
|
|
</HEAD>
|
|
<BODY>
|
|
<A HREF="LinuxDoc+Emacs+Ispell-HOWTO-3.html">Next</A>
|
|
<A HREF="LinuxDoc+Emacs+Ispell-HOWTO-1.html">Previous</A>
|
|
<A HREF="LinuxDoc+Emacs+Ispell-HOWTO.html#toc2">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s2">2. Introduction</A> </H2>
|
|
|
|
<H2><A NAME="ss2.1">2.1 SGML</A>
|
|
</H2>
|
|
|
|
<P><I>Standard Generalised Mark-up Language</I>, or
|
|
<B>SGML</B>, is a language to define document types.
|
|
<P>For instance, one may define the document type <I>recipe</I>, with a
|
|
first part presenting the ingredients, a second part introducing the
|
|
accessories, a third part giving step by step instructions for baking
|
|
the cake, and a nice final picture to show the outcome of it all.
|
|
<P>
|
|
This is called a <I>Document Type Definition</I>.
|
|
It does not define what the final product will look like, it only defines
|
|
what it may contain.
|
|
<P>
|
|
To use the same example again, I'm sure that upon reading my idea
|
|
of a recipe, you recognised yours, or your favourite cook's. Nevertheless,
|
|
they actually look different: mine have a picture in the upper left corner of
|
|
the bathroom cupboard, and the ingredients list can be found in the back
|
|
garden, between the swimming pool and the barbecue. Yours?
|
|
<P>
|
|
Thanks to this standard definition, one can write a document,
|
|
without taking into account what it will look like in the end to
|
|
the reader.
|
|
<P>
|
|
<H2><A NAME="ss2.2">2.2 The <CODE>LinuxDoc</CODE> Type Definition</A>
|
|
</H2>
|
|
|
|
<P>This type is used to write, as you might have guessed,
|
|
documents related to Linux.
|
|
<P>Such documents are generally built as follows: they start with a title
|
|
followed by the name of the author, and the version number and
|
|
date. Then comes the abstract (so you don't have to browse through it
|
|
before realizing it isn't what you were looking for after all),
|
|
then the contents which show the
|
|
structure so that those in a rush can go directly to the part they
|
|
want to read.
|
|
<P>Then comes a list of chapters, sections, paragraphs. Among these, one
|
|
can insert bits of programs, change the font to emphasise a word or a
|
|
sentence, insert lists, refer to another part of the document, etc.
|
|
<P>To write such a document, you just need to specify at the right time
|
|
the title, the author, the date, and the document version, the chapters
|
|
and sections, say when a list is to be inserted, what its elements are
|
|
etc.
|
|
<P>
|
|
<H2><A NAME="ss2.3">2.3 <CODE>SGML-Tools</CODE></A>
|
|
</H2>
|
|
|
|
<P><B>SGML-Tools</B> will turn the specification of a document into
|
|
the final result in the form you prefer. If you want it in your personal
|
|
library, you will choose <I>PostScript</I>. If you want to share it with
|
|
the world through the Web, it will be <I>HTML</I>. If you can't help it
|
|
and must read it under Windows, you can turn it into <I>RTF</I> to be
|
|
able to read it with any word processor. Or maybe use all three formats
|
|
to accommodate your changing moods.
|
|
<P>SGML-Tools are available via anonymous FTP at
|
|
<A HREF="ftp://ftp.lip6.fr/pub/sgml-tools/">ftp://ftp.lip6.fr/pub/sgml-tools/</A><P>
|
|
<HR>
|
|
<A HREF="LinuxDoc+Emacs+Ispell-HOWTO-3.html">Next</A>
|
|
<A HREF="LinuxDoc+Emacs+Ispell-HOWTO-1.html">Previous</A>
|
|
<A HREF="LinuxDoc+Emacs+Ispell-HOWTO.html#toc2">Contents</A>
|
|
</BODY>
|
|
</HTML>
|