87 lines
2.9 KiB
HTML
87 lines
2.9 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 Reference: Introduction</TITLE>
|
|
<LINK HREF="Linuxdoc-Reference-3.html" REL=next>
|
|
<LINK HREF="Linuxdoc-Reference-1.html" REL=previous>
|
|
<LINK HREF="Linuxdoc-Reference.html#toc2" REL=contents>
|
|
</HEAD>
|
|
<BODY>
|
|
<A HREF="Linuxdoc-Reference-3.html">Next</A>
|
|
<A HREF="Linuxdoc-Reference-1.html">Previous</A>
|
|
<A HREF="Linuxdoc-Reference.html#toc2">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s2">2. Introduction</A></H2>
|
|
|
|
<P>
|
|
<!--
|
|
principles
|
|
-->
|
|
|
|
<!--
|
|
sgml
|
|
-->
|
|
|
|
The principle of any sgml'ed document (linuxdoc, docbook, html) is
|
|
more or less the same:
|
|
<P>Don't write how it should <EM>look like</EM>, but write what it <EM>is</EM>.
|
|
<P>This is a different approach than the standard
|
|
"wysiwyg"
|
|
<BLOCKQUOTE>What you see is what you (should) get
|
|
(if you are a very lucky one and your computer wins the war against
|
|
buggy software)</BLOCKQUOTE>
|
|
one
|
|
<BLOCKQUOTE>You might want to call it
|
|
<CODE>wysiwym</CODE>, i.e. "What you see is what you mean"</BLOCKQUOTE>
|
|
.
|
|
You do not tell the program that this line should be in a bigger font,
|
|
<B>to look like</B> a headline.
|
|
What you do is telling that this line <B>is</B> a headline.
|
|
You do not try to make your document <B>look like</B> a
|
|
report, but you tag it <B>to be</B> a report.
|
|
So you <EM>tag</EM> the text with the appropriate <tag>.
|
|
<P>
|
|
<P>The big advantages of this approache are:
|
|
<OL>
|
|
<LI>You do not need to mess around with fontsetting, line gaps or
|
|
anything directly connected to the layout.</LI>
|
|
<LI>
|
|
<!--
|
|
portability
|
|
-->
|
|
|
|
You describe your document in a more abstract way so it's more
|
|
reusable and can be mapped to different media types.
|
|
<BLOCKQUOTE>If you ever tried the reuse a document written in a
|
|
specialized wysiwy layout for html then you know what I'm
|
|
talking about.</BLOCKQUOTE>
|
|
</LI>
|
|
</OL>
|
|
<P>In addition in all sgml-style documents you will find named symbols
|
|
This is a concept to expand the charset of the document and to avoid
|
|
inconsitences in decision of the parser, how to interpret or map some
|
|
special characters.
|
|
<P>How should the parser know weather a <CODE><</CODE> character is
|
|
starting a tag or should be printed directly.
|
|
This is solved by the named character <EM>lt</EM>.
|
|
If you write <CODE>&lt;</CODE> this one will result to <CODE><</CODE> in your
|
|
text.
|
|
For a list of the named symbols see
|
|
<A HREF="Linuxdoc-Reference-14.html#namedsymbols">Named Symbols</A>.
|
|
<P>
|
|
<DL>
|
|
<DT><B>Hint for the new user</B><DD><P>It might be a good idea, to download this document not only as a dvi or
|
|
ps document, but also to download the sgml source.
|
|
This offers you the chance to look into the sources, if you find something
|
|
within this article, wich might fit your needs.
|
|
</DL>
|
|
<P>
|
|
<P>
|
|
<HR>
|
|
<A HREF="Linuxdoc-Reference-3.html">Next</A>
|
|
<A HREF="Linuxdoc-Reference-1.html">Previous</A>
|
|
<A HREF="Linuxdoc-Reference.html#toc2">Contents</A>
|
|
</BODY>
|
|
</HTML>
|