LDP
/
old-www
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
old-www/HOWTO/Linuxdoc-Reference-7.html

743 lines
21 KiB
HTML
Raw Blame History

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Linuxdoc Reference: Paragraphs</TITLE>
<LINK HREF="Linuxdoc-Reference-8.html" REL=next>
<LINK HREF="Linuxdoc-Reference-6.html" REL=previous>
<LINK HREF="Linuxdoc-Reference.html#toc7" REL=contents>
</HEAD>
<BODY>
<A HREF="Linuxdoc-Reference-8.html">Next</A>
<A HREF="Linuxdoc-Reference-6.html">Previous</A>
<A HREF="Linuxdoc-Reference.html#toc7">Contents</A>
<HR>
<H2><A NAME="paragraph"></A> <A NAME="s7">7. Paragraphs</A></H2>
<P>
<HR>
<PRE>
&lt;!entity % sectpar
" %par; | figure | tabular | table | %mathpar; |
%thrm; | %litprog; ">
&lt;!entity % par
" %list; | comment | lq | quote | tscreen " >
&lt;!entity % litprog " code | verb " >
</PRE>
<HR>
<P>Each of the here described tags form a paragraph.
<P>For obvious reason a paragraph is normally
<BLOCKQUOTE>The behaviour of the
exceptions <CODE>figure</CODE> and <CODE>tabular</CODE> are explained there.</BLOCKQUOTE>
starting and
ending with a new line.
<BLOCKQUOTE>How else you would notice it's a paragraph ?</BLOCKQUOTE>
<P>There are some tags, wich always form a paragraph, and one way to form a
paragraph implicitly.
There are various types of paragraphs, because not every type of paragraph
is allowed to appear in every document class in every place.
<P>The different types of paragraphs are explained in the next sections.
For more details about <CODE>%litprog;</CODE> see
<A HREF="Linuxdoc-Reference-12.html#litprog">Literate Programming</A>.
<P>
<P>
<H2><A NAME="par"></A> <A NAME="ss7.1">7.1 Normal Paragraph</A>
</H2>
<P>Normal paragraphs can be formed in two ways:
<P>
<H3><A NAME="p"></A> Paragraph tag</H3>
<P>The <CODE>&lt;p&gt;</CODE> tag is starting a new <EM>paragraph</EM>.
This tag is mandatory if you want to finish a section header without
explicitly closing the <CODE>sect</CODE> tag.
In this case <CODE>&lt;p&gt;</CODE> tag then closes the <CODE>&lt;sect&gt;</CODE> tag
automatically.
<P>
<H3><A NAME="nn"></A> Empty Newline</H3>
<P>A empty line between two paragraph is implicitly starting a new
<EM>paragraph</EM>.
Take care within <CODE>descriptive</CODE> lists. There a empty <CODE>&lt;tag&gt;</CODE>
tag will not be paragraphed by an empty line.
<P>
<H2><A NAME="listlike"></A> <A NAME="ss7.2">7.2 List-like Paragraphs</A>
</H2>
<P>
<HR>
<PRE>
&lt;!entity % list
" list | itemize | enum | descrip " >
</PRE>
<HR>
This four tags indicate the starting of a list-like paragraph.
Within each of the lists the single items are separated by an
<EM>item tag</EM>.
<HR>
<PRE>
&lt;!element item o o ((%inline; | %sectpar;)*, p*) >
</PRE>
<HR>
As you can see, a item may again contain paragraphs (and therefore
also may contain other lists - even of a different type).
<P>
<H3><A NAME="list"></A> List Tag</H3>
<P>
<HR>
<PRE>
&lt;!element list - - (item+)>
</PRE>
<HR>
<P>The <EM>list tag</EM> will be mapped to a nacked list without bullets, numers or
anything else.
<P>To see it, I place a small example:
<HR>
<PRE>
&lt;list>
&lt;item>A point
&lt;item>Another one
&lt;item>Last
&lt;/list>
</PRE>
<HR>
<P>Will look (depending on the mapping) like:
<P>
<LI>A point</LI>
<LI>Another one</LI>
<LI>Last</LI>
<P>
<H3><A NAME="itemize"></A> Itemize Tag</H3>
<P>
<HR>
<PRE>
&lt;!element itemize - - (item+)>
</PRE>
<HR>
<P>The <EM>itemize tag</EM> will be mapped to a list with bullets,
wich is usually place for lists where the order of the items is not
important.
<P>A small example:
<HR>
<PRE>
&lt;itemize>
&lt;item>A point
&lt;item>Another one
&lt;item>Last
&lt;/itemize>
</PRE>
<HR>
<P>Will look (depending on the mapping) like:
<P>
<UL>
<LI>A point</LI>
<LI>Another one</LI>
<LI>Last</LI>
</UL>
<P>
<P>
<H3><A NAME="enum"></A> Enum Tag</H3>
<P>
<HR>
<PRE>
&lt;!element enum - - (item+)>
</PRE>
<HR>
<P>The <EM>enum tag</EM> will be mapped to a list with numbers.
<P>A small example:
<HR>
<PRE>
&lt;enum>
&lt;item>A point
&lt;item>Another one
&lt;item>Last
&lt;/enum>
</PRE>
<HR>
<P>Will look (depending on the mapping) like:
<P>
<OL>
<LI>A point</LI>
<LI>Another one</LI>
<LI>Last</LI>
</OL>
<P>
<P>
<H3><A NAME="descrip"></A> Descrip Tag</H3>
<P>
<!--
descrip
-->
<!--
tag!descrip
-->
<HR>
<PRE>
&lt;!element descrip - - (tag?, p+)+ >
</PRE>
<HR>
<P>The <EM>descrip tag</EM> will be mapped to a descriptive list.
The concept here is a little bit different than with the other types of lists
mentioned above.
<P>Here you place a <EM>tag</EM> (this time the tag's name is really litteraly
<CODE>tag</CODE>) wich is described later on.
<P>
<P>
<!--
example!descrip
-->
A small example:
<HR>
<PRE>
&lt;descrip>
&lt;tag/sgml/structured general markup language.
&lt;tag/html - hypertext markup language/
A sgml implementation.
It contains some concepts about linking information together in a very
convenient way.
This made it to be so successful and to become the standard for documents
published by the internet.
&lt;tag/internet/A worldwide connected internet (internet here as a
technical term)
&lt;/descrip>
</PRE>
<HR>
<P>Will look (depending on the mapping) like:
<P>
<DL>
<DT><B>sgml</B><DD><P>structured general markup language.
<DT><B>html - hypertext markup language</B><DD><P>A sgml implementation. It contains some concepts about linking information together
in a very covenient way. This made it to be so successfull and to become the standard for
documents published by the internet.
<DT><B>internet</B><DD><P>A worldwide connected internet (internet here as a technical term)
</DL>
<P>
<P>
<H2><A NAME="figtab"></A> <A NAME="ss7.3">7.3 Figures and Tables</A>
</H2>
<P>The <CODE>&lt;figure&gt;</CODE> and the <CODE>&lt;table&gt;</CODE> tags form very special
paragraphs.
Not always they stay within the normal textflow.
Both of the tags can hold a <CODE>loc</CODE> (<EM>loction</EM>) attribute wich is telling
how to handle the flow of this special paragraph.
<P>The value of the <CODE>loc</CODE> attribute is a string of up to four letters, where
each letter declares a location at which the figure or table <B>may</B> appear,
as described in table
<A HREF="#tlocations">Table Locations</A>.
<P>
<CENTER><TABLE BORDER><TR><TD>
<BR>
h</TD><TD>here</TD><TD>At the same location as in the SGML file</TD></TR><TR><TD>
t</TD><TD>top</TD><TD>At the top of a page</TD></TR><TR><TD>
b</TD><TD>bottom</TD><TD>At the bottom of a page</TD></TR><TR><TD>
p</TD><TD>page</TD><TD>On a separate page only with figures and tables
<CAPTION>Table Locations
<A NAME="tlocations"></A> </CAPTION>
</TD></TR></TABLE></CENTER>
<P>The default value of the loc attribute is <CODE>top</CODE>.
<P>
<P>
<H3><A NAME="table"></A> Table Tag</H3>
<P>
<!--
table
-->
<!--
tag!table
-->
<HR>
<PRE>
&lt;!element table - - (tabular, caption?) >
</PRE>
<HR>
<P>As you can see a <EM>table</EM> consists of the <CODE>&lt;table&gt;</CODE> tag itself,
including a <CODE>&lt;tabular&gt;</CODE> tag and a optional <CODE>&lt;caption&gt;</CODE> tag.
<P>The <CODE>&lt;tabular&gt;</CODE> tag may also be placed without a <CODE>&lt;table&gt;</CODE>
tag so it is described in detail in it's own section
(see
<A HREF="#tabular">Tabular Tag</A>).
<P>The <EM>caption</EM> is used also to place the entry for the
<EM>list of tables</EM> if you stated one
(see
<A HREF="Linuxdoc-Reference-4.html#lot">The List Of Tables Tag</A>).
<P>A short example will show how it's working together.
<P>
<!--
example!table
-->
<PRE>
&lt;table loc="ht">
&lt;tabular ca="lcr">
Look|this|table@
Isn't|it|nice@
1.234|mixed|columns
&lt;/tabular>
&lt;caption>A sample table
&lt;/table>
</PRE>
<P>
<CENTER><TABLE BORDER><TR><TD>
<BR>
Look</TD><TD>this</TD><TD>table</TD></TR><TR><TD>
Isn't</TD><TD>it</TD><TD>nice</TD></TR><TR><TD>
1.234</TD><TD>mixed</TD><TD>columns
<CAPTION>A sample table</CAPTION>
</TD></TR></TABLE></CENTER>
<P>The <EM>caption</EM> "A sample table" would be the name in the <EM>list of
tables</EM>.
<P>
<H3><A NAME="figure"></A> Figure Tag</H3>
<P>
<!--
figure
-->
<!--
tag!figure
-->
<HR>
<PRE>
&lt;!element figure - - ((eps | ph ), img*, caption?)>
</PRE>
<HR>
The usage of the <CODE>&lt;figure&gt;</CODE> tag is equivalent to the
<CODE>&lt;table&gt;</CODE> tag.
Instead of the <CODE>&lt;tabular&gt;</CODE> tag you place either a <CODE>&lt;eps&gt;</CODE>
or a <CODE>&lt;ph&gt;</CODE> tag.
<P>
<H3><A NAME="eps"></A> Encapsulated Postscript&trade; Tag</H3>
<P>
<!--
figure!eps
-->
<!--
tag!figure!eps
-->
<HR>
<PRE>
&lt;!attlist eps
file cdata #required
height cdata "5cm"
angle cdata "0">
</PRE>
<HR>
The <CODE>&lt;eps&gt;</CODE> tag is intended for including a external file in
<EM>encapsulated postscript&trade;</EM> format into the document.
<P>The attributes of the <CODE>&lt;eps&gt;</CODE> tag are:
<P>
<DL>
<P>
<DT><B>file</B><DD><P>The <CODE>file</CODE> attribute needs the <EM>file name</EM> of a encapsulated
postscript&trade; file ending with a <CODE>.ps</CODE> suffix.
The mandatory <CODE>.ps</CODE> suffix must not be written.
<P>
<DT><B>height</B><DD><P>The <EM>height</EM> of the space the file is zoomed to.
If you don't specify it defaults to 5cm.
Take care that there's no spcae between the number and the length unit
(<CODE>i</CODE>, <CODE>cm</CODE>).
<P>
<DT><B>angle</B><DD><P>The <EM>angle</EM> is given in normal degrees (0-360) and as the number is
increasing the file is rotated counter clockwise.
<P>
</DL>
<P>A example:
<P>
<!--
example!figure!eps
-->
<PRE>
&lt;figure loc="here">
&lt;eps file="logo" height="4cm" angle="15">
&lt;img src="logo.gif">
&lt;caption>A included encapsulated postscript&amp;trade;
&lt;/figure>
</PRE>
<P>The <EM>img</EM> tag is ignored by LaTeX-mapping and useful for
html, 'cause most browsers don't know about eps.
<P>
<P>
<FIGURE>
<EPS FILE="logo">
<IMG SRC="logo.gif">
<CAPTION>A included encapsulated postscript&trade; file.</CAPTION>
</FIGURE>
<P>The <EM>caption</EM> here would go to the <EM>list of figures</EM> as decribed in
section
<A HREF="Linuxdoc-Reference-4.html#lof">The List Of Figures Tag</A>.
<P>
<P>
<H3><A NAME="ph"></A> Placeholder Tag</H3>
<P>
<!--
figure!ph
-->
<!--
tag!figure!ph
-->
<HR>
<PRE>
&lt;!attlist ph
vspace cdata #required>
</PRE>
<HR>
This tag doesn't place anything but keeps a clean space for good old
manual picture pasting.
The space kept free is destined by the <CODE>vspace</CODE> attribte.
<B>Caveat:</B> The numerical argument for the <CODE>vspace</CODE> attribte needs a
unit directly behind the number. Don't leave a space there
(same as for the <CODE>height</CODE> attribute in
<A HREF="#eps">Encapsulated Postscript&trade; Tag</A>.
<P>
<!--
example!figure!ph
-->
<PRE>
&lt;figure loc="ht">
&lt;ph vspace="5cm">
&lt;caption>A blank space.
&lt;/figure>
</PRE>
<P>Results to:
<P>
<FIGURE>
<PH VSPACE="5cm">
<CAPTION>A blank space for gluing a photo</CAPTION>
</FIGURE>
<P>At this point you might want to look for your scissors and the glue.
<P>
<P>
<H2><A NAME="tabular"></A> <A NAME="ss7.4">7.4 Tabular Tag</A>
</H2>
<P>
<HR>
<PRE>
&lt;!element tabular - -
(hline?, %tabrow, (rowsep, hline?, %tabrow)*, caption?) >
</PRE>
<HR>
The <CODE>&lt;tabular&gt;</CODE> tag is interpreted as an own paragraph, if it is
written standalone.
Together with a <CODE>&lt;table&gt;</CODE> tag it gets part of the paragraph of the
<CODE>&lt;table&gt;</CODE> tag (see
<A HREF="#table">Table tag</A>).
<P>Within the <CODE>tabular</CODE> tag you have rows an collumns wich are separating the
text.
You have to have at least one collumn and one row.
<BLOCKQUOTE>Wouldn't be very
usefull otherwise.</BLOCKQUOTE>
<P>The <CODE>&lt;tabular&gt;</CODE> tag has a mandatory <CODE>ca</CODE> attribute for <EM>collumn
allignement</EM>.
The collumn allignement holds a single character for each collumn in their
order from left to right.
The chracters you may place per collumn described in table
<A HREF="#tcalign">Collumns allignements</A><P>
<CENTER><TABLE BORDER><TR><TD>
<BR>
char</TD><TD>alignment</TD></TR><TR><TD>
</TD></TR><TR><TD>
l</TD><TD>left</TD></TR><TR><TD>
c</TD><TD>centered</TD></TR><TR><TD>
r</TD><TD>right
<CAPTION>Column alignments
<A NAME="tcalign"></A> </CAPTION>
</TD></TR></TABLE></CENTER>
<P>In theory you should be able to place a | into the <CODE>ca</CODE> attribure for
drawing a horizontal line for separating two collumns.
The problem: It doesn't work.
The parser accepts it nicely, only the LaTeX output will map <CODE>|</CODE> to
<CODE>{$|$}</CODE> wich is of course the set for four collumns with invalid collumn
allignement for all four collums.
I'll try to figure out what to do about it.
<P>The columns within the <CODE>&lt;tabular&gt;</CODE> tag are separated by a <EM>collumn
separator</EM>, the <CODE>&lt;colsep&gt;</CODE> tag. The character <CODE>|</CODE> is translated to
<CODE>&lt;colsep&gt;</CODE> so you can also place that one instead
<BLOCKQUOTE>Less
typing, more fun.</BLOCKQUOTE>
.
<P>What's valid for collumns is also valid for rows. You separate the by a
<EM>row separator</EM>, the <CODE>&lt;rowsep&gt;</CODE> tag.
The character <CODE>@</CODE> is translated to <CODE>&lt;rowsep&gt;</CODE>.
<P>Optional you can place a <EM>horizontal line</EM> with the <CODE>&lt;hline&gt;</CODE> tag.
Take care with that one:
The SGML tools will parse it nicely weather you place it in front of the row
you want under the line, or behind the end of the row you want over it.
But the only place to write it without causing the parser to shout
&quot;error&quot; is to write it dircetly and without space or newline behind
the row separator.
<P>
<PRE>
&lt;tabular ca="lcr">
Look|this|table@&lt;hline>
Isn't|it|nice@
1.234|mixed|columns@
&lt;/tabular>
</PRE>
<P>Results in table
<A HREF="#ttabularsample">Sample table for tabular tag</A><P>
<CENTER><TABLE BORDER><TR><TD>
<BR>
Look</TD><TD>this</TD><TD>table</TD></TR><TR><TD>
</TD></TR><TR><TD>
Isn't</TD><TD>it</TD><TD>nice</TD></TR><TR><TD>
1.234</TD><TD>mixed</TD><TD>columns</TD></TR><TR><TD>
<CAPTION>Sample table for tabular tag
<A NAME="ttabularsample"></A> </CAPTION>
</TD></TR></TABLE></CENTER>
<P>
<DL>
<DT><B>Attention:</B><DD><P>In LaTeX mapping everything works nice if you place a
<EM>tabular tag</EM> without a <EM>table tag</EM>, only in the other mappings (e.g.
html) it will be messed up.
</DL>
<P>
<H2><A NAME="mathpar"></A> <A NAME="ss7.5">7.5 Mathematical Paragraph</A>
</H2>
<P>
<HR>
<PRE>
&lt;!entity % mathpar " dm | eq " >
</PRE>
<HR>
<P>A <EM>mathematical paragraph</EM> consits either of a <EM>displayed formula</EM>,
tagged by <CODE>&lt;dm&gt;</CODE>
<BLOCKQUOTE>No, sorry, not for Deutschmark! ;-)</BLOCKQUOTE>
or an <EM>equation</EM>, tagged by <CODE>&lt;eq&gt;</CODE>.
They work very much the same.
<P>Both of these tags contain a mathematical formula.
See
<A HREF="Linuxdoc-Reference-9.html#formula">Mathematical Formulas</A> for the tags valid here.
<P>
<DL>
<DT><B>Note:</B><DD><P>Because neither Netscape nor Microsoft has seen any need
to add mathematical mappings to their browsers (like demanded and defined by
<EM>w3c</EM>), there is no nice way of mapping, or at least displaying the math
stuff in html. So if you view the online version, feel free to wonder what
nonsense this man is telling here. Might be you should take a glance at the
postscript version.
</DL>
<P>
<P>
<H3><A NAME="dm"></A> Displayed Formula Tag</H3>
<P>This tag displays a <EM>mathematical formula</EM> as a <EM>paragraph</EM>.
The formula is mapped centered as a single line
<BLOCKQUOTE>No guarantee for
that. You know: Mapping is a matter of taste.</BLOCKQUOTE>
.
<P>
<PRE>
&lt;dm>(a+b)&lt;sup/2/=a&lt;sup/2/+2ab+b&lt;sup/2/&lt;/dm>
</PRE>
Is mapped to:
<DM>
(a+b)<SUP>2</SUP>=a<SUP>2</SUP>+2ab+b<SUP>2</SUP>
</DM>
<P>
<P>
<H3><A NAME="eq"></A> Equation Tag</H3>
<P>
<PRE>
&lt;dm>(a+b)&lt;sup/2/=a&lt;sup/2/+2ab+b&lt;sup/2/&lt;/dm>
</PRE>
Is mapped to:
<DM>
(a+b)<SUP>2</SUP>=a<SUP>2</SUP>+2ab+b<SUP>2</SUP>
</DM>
<P>
<P>
<H2><A NAME="thrm"></A> <A NAME="ss7.6">7.6 Theorem Paragraph</A>
</H2>
<P>
<HR>
<PRE>
&lt;!entity % thrm
" def | prop | lemma | coroll | proof | theorem " >
&lt;!element def - - (thtag?, p+) >
&lt;!element prop - - (thtag?, p+) >
&lt;!element lemma - - (thtag?, p+) >
&lt;!element coroll - - (thtag?, p+) >
&lt;!element proof - - (p+) >
&lt;!element theorem - - (thtag?, p+) >
</PRE>
<HR>
As you can see the different types of <EM>theorem</EM> paragraphs are nearly
identical.
The only exception wich is a little bit different is the <EM>proof</EM> wich
doesn't own a <CODE>thtag</CODE>.
For all the others the <CODE>thtag</CODE> is giving the <EM>tag</EM> of the theorem
paragraph.
<P>Yust try to use that one, wich is fitting the meaning of what you are typing.
<P>
<PRE>
&lt;thrm>
&lt;thtag>Alexander's thrm&lt;/thtag>
Let &lt;f>&amp;lt;fi/G/&lt;/f> be a set of non-trivially achievable subgoals
and &amp;mu; an order on &lt;f>&amp;lt;fi/G/&lt;/f>. &amp;mu; is abstractly
indicative if and only if it is a linearization of
&lt;f>&lt;lim>&lt;op>&amp;mu;&lt;/op>&lt;ll>&lt;fi/G/&lt;/ll>&lt;ul>&amp;ast;&lt;/ul>&lt;/lim>&lt;/f>.
&lt;/theorem>
</PRE>
<P>The <CODE>thrm</CODE> is replaced by the adequate tag.
<P>Maybe somebody knowing about mathematics would be shocked about my abuse of
the types, but I'm lazy so I simply copied the examples:
<P><EM>Definition</EM> (<CODE>def</CODE>):
<DEF><THTAG>Alexander's Definition</THTAG><P>Let <FI>G</FI> be a set of nontrivially achievable subgoals and &micro;
an order on <FI>G</FI>. &micro; is abstractly indicative if and only
if it is a linearization of
<LIM><OP>&micro;</OP><LL><FI>G</FI></LL><UL>&ast;</UL></LIM>.
</DEF>
<P><EM>Proposition</EM> (<CODE>prop</CODE>):
<PROP><THTAG>Alexander's Proposition</THTAG><P>Let <FI>G</FI> be a set of nontrivially achievable subgoals and &micro;
an order on <FI>G</FI>. &micro; is abstractly indicative if and only
if it is a linearization of
<LIM><OP>&micro;</OP><LL><FI>G</FI></LL><UL>&ast;</UL></LIM>.
</PROP>
<P><EM>Lemma</EM> (<CODE>lemma</CODE>):
<LEMMA><THTAG>Alexander's Lemma</THTAG><P>Let <FI>G</FI> be a set of nontrivially achievable subgoals and &micro;
an order on <FI>G</FI>. &micro; is abstractly indicative if and only
if it is a linearization of
<LIM><OP>&micro;</OP><LL><FI>G</FI></LL><UL>&ast;</UL></LIM>.
</LEMMA>
<P><EM>Corollation</EM> (<CODE>coroll</CODE>):
<COROLL><THTAG>Alexander's Corollary</THTAG><P>Let <FI>G</FI> be a set of nontrivially achievable subgoals and &micro;
an order on <FI>G</FI>. &micro; is abstractly indicative if and only
if it is a linearization of
<LIM><OP>&micro;</OP><LL><FI>G</FI></LL><UL>&ast;</UL></LIM>.
</COROLL>
<P>
<THEOREM><THTAG>Alexander's Theorem</THTAG><P>Let <FI>G</FI> be a set of nontrivially achievable subgoals and &micro;
an order on <FI>G</FI>. &micro; is abstractly indicative if and only
if it is a linearization of
<LIM><OP>&micro;</OP><LL><FI>G</FI></LL><UL>&ast;</UL></LIM>.
</THEOREM>
<P>The proof is just the same without the <CODE>thtag</CODE>:
<P>
<PROOF><P>Let <FI>G</FI> be a set of nontrivially achievable subgoals and &micro;
an order on <FI>G</FI>. &micro; is abstractly indicative if and only
if it is a linearization of
<LIM><OP>&micro;</OP><LL><FI>G</FI></LL><UL>&ast;</UL></LIM>.
</PROOF>
<P>
<H2><A NAME="codeandverb"></A> <A NAME="ss7.7">7.7 Code and verbatim Paragraphs</A>
</H2>
<P>Both tags from a paragraph and have very similar behavior.
Inside this tags most special characters don't need their named form
as in section
<A HREF="Linuxdoc-Reference-14.html#namedsymbols">Named Symbols</A>.
The exceptions are:
<OL>
<LI>&amp;etago;&nbsp;-&gt;&nbsp;&lt;/&nbsp;-&gt;&nbsp;<CODE>end of tag open</CODE></LI>
</OL>
Maybe later the list will grow.
<P>In difference to the normal paragraph mapping white-spaces and newlines will be
mapped literally (as you write them in your source).
<P>Also (with respect to manual layout) the font for mapping will be a
non-proportional one.
<BLOCKQUOTE>See the difference between IIWW and
<CODE>IIWW</CODE>.</BLOCKQUOTE>
<P>
<DL>
<DT><B>Note:</B><DD><P>Aggain, I'm neither a native speaker not I love mathematics a lot.
So I just placed some nonsense, wich might cause headache and grey hair for
people who want to use this document for learning to formulate mathematical
or physical theories.
<P>Feel free to send better examples.
</DL>
<P>
<P>
<H3><A NAME="code"></A> Code Tag</H3>
<P>
<HR>
<PRE>
&lt;!element code - - rcdata>
</PRE>
<HR>
<P>Use the <EM>code tag</EM>, if you want to write sourcecode example within your
text.
<P>A code sample
<P>&lt;code>
<HR>
<PRE>
#include &lt;stdio.h>
int main() {
printf("Hello world");
return 1;
}
</PRE>
<HR>
&lt;/code>
<P>
<H3><A NAME="verbatim"></A> Verbatim Tag</H3>
<P>
<HR>
<PRE>
&lt;!element verb - - rcdata>
</PRE>
<HR>
<P>Use the <EM>verbatim tag</EM> for anything else than sourcecode
(use
<A HREF="#code">Code Tag</A> for this) which needs the good old
whitespace padding, like terminal hardcopy, ASCII-Graphics etc.
<P>A verb sample
<P>&lt;verb>
<PRE>
/////////
| * * |
| | |
| &lt;---> |
\_____/
</PRE>
&lt;/verb>
<P>
<HR>
<A HREF="Linuxdoc-Reference-8.html">Next</A>
<A HREF="Linuxdoc-Reference-6.html">Previous</A>
<A HREF="Linuxdoc-Reference.html#toc7">Contents</A>
</BODY>
</HTML>
Reference in New Issue View Git Blame Copy Permalink