<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="generator" content="hevea 2.06">
<META name="Author" content="Luc Maranget"><link rel="stylesheet" type="text/css" href="manual.css">
<title>Classes, Packages and Page Styles</title>
</head>
<body>
<a href="sectioning.html"><img src="previous_motif.gif" alt="Previous"></a>
<a href="manual022.html"><img src="contents_motif.gif" alt="Up"></a>
<a href="manual028.html"><img src="next_motif.gif" alt="Next"></a>
<hr>
<h2 class="section" id="sec118">B.5  Classes, Packages and Page Styles</h2>
<ul>
<li><a href="manual027.html#sec119">Document Class</a>
</li><li><a href="manual027.html#sec120">Packages and Page Styles</a>
</li><li><a href="manual027.html#sec121">The Title Page and Abstract</a>
</li></ul>
<h3 class="subsection" id="sec119">B.5.1  Document Class</h3>
<p>
Both L<sup>A</sup>T<sub>E</sub>X 2є <code>\documentclass</code> and old L<sup>A</sup>T<sub>E</sub>X
<code>\documentstyle</code> are accepted.
Their argument <em>style</em> is interpreted by attempting to load a
<em>style</em><span class="c013">.hva</span> file.
Presently, only the style files <span class="c013">article.hva</span>, <span class="c013">seminar.hva</span>,
<span class="c013">book.hva</span> and <span class="c013">report.hva</span> exist, the latter two
being equivalent.</p><p>If one of the recognized styles has already been loaded at the time when
<code>\documentclass</code> or
<code>\documentstyle</code> is executed, then no attempt to load a style
file is made. This allows to override the document style file by
giving one of the four recognized style files of H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A as a command
line argument (see <a href="manual004.html#otherbase">2.2</a>).</p><p>Conversely, if H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A attempt to load <em>style</em><span class="c013">.hva</span>
fails, then a fatal error is flagged, since it can be sure
that the document cannot be processed.</p>
<h3 class="subsection" id="sec120">B.5.2  Packages and Page Styles</h3>
<p><a id="usepackage"></a>
<a id="hevea_default157"></a>
H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A reacts to
<code>\usepackage[</code><span class="c018">options</span><code>]{</code><span class="c018">pkg</span><code>}</code> in
the following way:
</p><ol class="enumerate" type=1><li class="li-enumerate">
The whole
<code>\usepackage</code> command with its arguments gets echoed to the
<em>image</em> file (see <a href="manual008.html#imagen">6</a>).
</li><li class="li-enumerate">H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A attempt to load file <span class="c018">pkg</span><span class="c013">.hva</span>,
(see section <a href="manual041.html#search%3Apath">C.1.1.1</a> on where H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A searches for files).
</li></ol><p>
Note that H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A will not fail if it cannot load
<span class="c018">pkg</span><span class="c013">.hva</span> and that no warning is issued in that case.</p><p>The H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A distribution contains implementations of some packages,
such as <span class="c013">verbatim</span>, <span class="c013">colors</span>, <span class="c013">graphics</span>, etc.</p><p>In some situations it may not hurt at all if H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A does not
implement a package, for instance H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A does not provide an
implementation for the <span class="c013">fullpage</span> package.</p><p>Users needing an implementation of a package that is widely used and
available are encouraged to contact the
<a href="mailto:Luc.Maranget@inria.fr">author</a>.
Experienced users may find it fun to attempt to write package
implementations by themselves.</p>
<h3 class="subsection" id="sec121">B.5.3  The Title Page and Abstract</h3>
<p>
All title related commands exist, with the following peculiarities:
</p><ul class="itemize"><li class="li-itemize">
The argument to the <code>\title</code><a id="hevea_default158"></a> command appears
in the html document header. As a consequence, titles should
remain simple. Normal design (as regards H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A) is for
<code>\title</code> to occur in the document preamble, so that the title
is known at the time when the document header is emitted (while
processing <code>\begin{document}</code>). However, there are two subtleties.<p>If no <code>\title</code>
command occurs in document preamble and that one <code>\title</code>
command appears in the document, then the title is saved into the
<span class="c013">.haux</span> file for a next run of H<span class="c015"><sup>E</sup></span>V<span class="c015"><sup>E</sup></span>A to put it in the
html document header.</p><p>If <code>\title</code> commands are present both in preamble and after
<code>\begin{document}</code>, then the former takes precedence.</p></li><li class="li-itemize">When not present the date is left empty. The
<code>\today</code><a id="hevea_default159"></a> command generates will work properly
only if <span class="c013">hevea</span> is invoked with the <code>-exec xxdate.exe</code>
option. Otherwise <code>\today</code> generates nothing and a warning is
issued.
</li></ul><p>The <code>abstract</code> environment is present is all base styles,
including the <em>book</em> style.
The <code>titlepage</code> environment does nothing.</p>
<hr>
<a href="sectioning.html"><img src="previous_motif.gif" alt="Previous"></a>
<a href="manual022.html"><img src="contents_motif.gif" alt="Up"></a>
<a href="manual028.html"><img src="next_motif.gif" alt="Next"></a>
</body>
</html>
