Sometimes, HEVEA just cannot process its input, but it remains acceptable to have LATEX process it, to produce an image from LATEX output and to include a link to this image into HEVEA output. HEVEA provides a limited support for doing this.
While outputting doc.html, HEVEA echoes some of its input to the image file, doc.image.tex. Part of this process is done at the user’s request. More precisely, the following two constructs send text to the image file:
\begin{toimage}\end{toimage}%BEGIN IMAGE%END IMAGE
Additionally, \usepackage commands, top-level and global
definitions
are automatically echoed to the image file. This enables using
document-specific commands in text above.
Output to the image file builds up a current page, which is flushed
by the \imageflush command.
This command has the following effect: it outputs a strict page break
in the image file, increments the image counter and
output a <img src="pagename.png"> tag in HEVEA
output file, where pagename is build from the image counter
and HEVEA output file name.
Then the imagen script has to be run by:
# imagen doc
This will process the doc.image.tex file through LATEX, dvips, ghostscript and a few others tools, which must all be present (see section C.4.1), finally producing one pagename.png file per page in the image file.
The usage of imagen is described at
section C.1.5. Note that imagen is a simple shell
script. Unix users can pass hevea the command-line option
-fix. Then hevea will
itself call imagen, when appropriate.
Consider the “blob” example from section 4.2. Here is the active part of a blob.tex file:
\newcommand{\blob}{\rule[.2ex]{1ex}{1ex}}
\blob\ Blob \blob
This time, we would like \blob to produce a small black square, which
\rule[.2ex]{1ex}{1ex} indeed does in LATEX.
Thus we can write:
\newcommand{\blob}{%
\begin{toimage}\rule[.2ex]{1ex}{1ex}%
\end{toimage}%
\imageflush}
\blob\ Blob \blob
Now we issue the following two commands:
# hevea blob.tex # imagen blob
And we get:
Blob
Observe that the trick can be used to replace missing symbols by small
.png images. However, the cost may be prohibitive, text rendering
is generally bad, fine placement is ignored and font style changes are
problematic.
Cost can be lowered using \savebox, but the other problems remain.
In this section, a technique to transform included Postscript images into included bitmap images is described. Note that this technique is used by HEVEA implementation of the graphics package (see section B.14.1), which provides a more standard manner to include Postscript images in LATEX documents.
Included images are easy to manage: it suffices to let LATEX do the job. Let round.ps be a Postscript file, which is included as an image in the source file round.tex (which must load the epsf package):
\begin{center}
\epsfbox{round.ps}
\end{center}
Then, HEVEA can have this image translated into a inlined (and centered) .png image by modifying source as follows:
\begin{center}
%BEGIN IMAGE
\epsfbox{round.ps}
%END IMAGE
%HEVEA\imageflush
\end{center}
(Note that the round.tex file
still can be processed by LATEX, since comment equivalents
of the toimage environment are used and that
the \imageflush command is inside
a %HEVEA comment — see section 5.3.)
Then, processing round.tex through HEVEA and imagen yields:
It is important to notice that things go smoothly because the
\usepackage{epsf} command gets echoed to the
image file. In more complicated cases, LATEX may fail
on the image file because it does not load the right
packages or define the right macros.
However, the above solution implies modifying the original LATEX
source code.
A better solution is to define the \epsfbox
command, so that HEVEA echoes \epsfbox and its argument to
the image file and performs \imageflush:
\newcommand{\epsfbox}[1]{%
\begin{toimage}
\epsfbox{#1}
\end{toimage}
\imageflush}
Such a definition must be seen by HEVEA only. So, it is best put
in a separate file whose name is given as an extra argument on
HEVEA command-line (see section 5.1).
Putting it in the document source
protected inside an %HEVEA comment is a bad idea, because it might then get echoed to the image file
and generate trouble when LATEX is later run by imagen.
Observe that the above definition of \epsfbox is a definition
and not a redefinition (i.e. \newcommand is used and not
\renewcommand),
because HEVEA does not know about \epsfbox by default.
Also observe that this not a recursive definition, since
commands do not get expanded inside the toimage environment.
Finally, if the Postscript image is produced from a bitmap, it is a pity to translate it back into a bitmap. A better idea is first to generate a PNG file from the bitmap source independantly and then to include a link to that PNG file in html output, see section 8.2 for a description of this more adequate technique.
Some programs extend LATEX capabilities using a filter principle. In such a scheme, the document contains source fragments for the program. A first run of the program on LATEX source changes these fragments into constructs that LATEX (or a subsequent stage in the paper document production chain, such as dvips) can handle. Here again, the rule of the game is keeping HEVEA away from the normal process: first applying the filter, then making HEVEA send the filter output to the image file, and then having imagen do the job.
Consider the gpic filter, for making drawings.
Source for gpic is enclosed in .PS….PE,
then the result is available to subsequent LATEX source as a TEX
box \box\graph.
For instance the following source, from a smile.tex file,
draws a “Smile!” logo as a centered
paragraph:
.PS
ellipse "{\Large\bf Smile!}"
.PE
\begin{center}
~\box\graph~
\end{center}
Both the image description (.PS… .PE) and usage (\box\graph)
are for the image file, and they should be
enclosed by %BEGIN IMAGE… %END IMAGE comments.
Additionally, the image link is put where it belongs by an
\imageflush command:
%BEGIN IMAGE
.PS
ellipse "{\Large\bf Smile!}"
.PE
%END IMAGE
\begin{center}
%BEGIN IMAGE
~\box\graph~
%END IMAGE
%HEVEA\imageflush
\end{center}
The gpic filter is applied first, then come hevea and imagen:
# gpic -t < smile.tex > tmp.tex # hevea tmp.tex -o smile.html # imagen smile
And we get:
Observe how the -o argument to HEVEA is used and that
imagen argument is HEVEA output basename (see
section C.1.1.2 for the full definition of HEVEA output basename).
In the gpic example, modifying user source cannot be totally avoided. However, writing in a generic style saves typing. For instance, users may define the following environment for centered gpic pictures in LATEX:
\newenvironment{centergpic}{}{\begin{center}~\box\graph~\end{center}}
Source code will now be as follows:
\begin{centergpic}
.PS
ellipse "{\Large\bf Smile!}"
.PE
\end{centergpic}
HEVEA will process this source correctly, provided it is given its
own definition for the centergpic environment beforehand:
\newenvironment{centergpic}
{\begin{toimage}}
{\box\graph\end{toimage}\begin{center}\imageflush\end{center}}
Assuming that the definition above is in a smile.hva file, the command sequence for translating smile.tex now is:
# gpic -t < smile.tex > tmp.tex # hevea smile.hva tmp.tex -o smile.html tmp.tex:5: Warning: ignoring definition of \centergpic tmp.tex:5: Warning: not defining environment centergpic # imagen smile
The warnings above are normal: they are issued when HEVEA runs
across the LATEX-intended definition of the centergpic
environment and refuses to override its own definition for that
environment.
hevea-2.36-manual/thaihevea.htoc 0000644 0043171 0051216 00000000453 14252364057 016664 0 ustar maranget cristal \begin{tocenv}
\tocitem \@locref{sec1}{\begin{@norefs}\@print{1}\quad{}Latin/Thai Character Set{}\end{@norefs}}
\tocitem \@locref{sec2}{\begin{@norefs}\@print{2}\quad{}Thai in \LaTeX{}\end{@norefs}}
\tocitem \@locref{sec3}{\begin{@norefs}\@print{3}\quad{}Thai in \hevea{}\end{@norefs}}
\end{tocenv}
hevea-2.36-manual/manual001.png 0000644 0043171 0051216 00000006532 14252364055 016255 0 ustar maranget cristal PNG
IHDR v &iCCPicc HgPY<@BPC*%Z(ҫ@PEl+4EE\"kE t,ʺqQAYp ?{ossp e{bRɎ(tջ {i常r)t eJOYLgWX\2XyKο,]~
)sT8بlOrTzV $G&D~S GfDnr&AltL:5204_gK!FgE_z s z t@WOm| :3z
@(U t08 |A $`( E` 8@-h M<.L@ށA2@F 7
Bh( ʀrPT
UAuP t݄84
}aXև0v}p4
^O 6< "@]p$BV)GVC!Bd h(&JerFTVT1
uՁECDh2Z @Ёht ]nDѓw aa0Θ L f3sӆL`X VkaӱJI%v G)p`\.Wk]
p xq:o;IA"X| q
B+aH$͉^XvbqD%iRi/82!
L ے&US{1O,BlXXؐ+
NP6Pr(3;Yq8W
Both LATEX 2є \documentclass and old LATEX
\documentstyle are accepted.
Their argument style is interpreted by attempting to load a
style.hva file.
Presently, only the style files article.hva, seminar.hva,
book.hva and report.hva exist, the latter two
being equivalent.
If one of the recognized styles has already been loaded at the time when
\documentclass or
\documentstyle 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 HEVEA as a command
line argument (see 2.2).
Conversely, if HEVEA attempt to load style.hva fails, then a fatal error is flagged, since it can be sure that the document cannot be processed.
HEVEA reacts to
\usepackage[options]{pkg} in
the following way:
\usepackage command with its arguments gets echoed to the
image file (see 6).
Note that HEVEA will not fail if it cannot load pkg.hva and that no warning is issued in that case.
The HEVEA distribution contains implementations of some packages, such as verbatim, colors, graphics, etc.
In some situations it may not hurt at all if HEVEA does not implement a package, for instance HEVEA does not provide an implementation for the fullpage package.
Users needing an implementation of a package that is widely used and available are encouraged to contact the author. Experienced users may find it fun to attempt to write package implementations by themselves.
All title related commands exist with the following peculiarities:
\title command
appears in the html document header. As a consequence titles
should remain simple. Normal design (as regards HEVEA) is
for \title to occur in the document preamble, so that the
title is known at the time when the document header is emitted, this
is, while processing \begin{document}. However, there are
two subtleties.\title command occurs in document preamble and
that one \title command appears in the document, then the
title is saved into the .haux file for the next run of
HEVEA to put it in the html document header.\title commands are present both in preamble and
after \begin{document} the former takes precedence.
\today command generates will work properly
only if hevea is invoked with the
-exec xxdate.exe option. Otherwise \today generates
nothing and a warning is issued.
The abstract environment is present in all base styles,
including the book style. The titlepage environment
does nothing.
HEVEA places the \title argument into an h1-element
with class titlemain and puts the arguments of \author
and \date into a h3-element with class titlerest.
The abstract goes into a blockquote-element with
class abstract.
hevea-2.36-manual/manual040.html 0000644 0043171 0051216 00000004452 14252364057 016441 0 ustar maranget cristal
Part C |
hevea-2.36-manual/manual003.html 0000644 0043171 0051216 00000005122 14252364056 016432 0 ustar maranget cristal
Assume that you have a file, a.tex, written in LATEX, using the article, book or report style. Then, translation is achieved by issuing the command:
# hevea a.tex
Probably, you will get some warnings. If HEVEA does not crash, just ignore them for the moment (Section 4 explains how to correct errors).
If everything goes fine, this will produce a new file, a.html, which you can visualise through a html browser.
If you wish to experiment HEVEA on small LATEX source fragments, then launch HEVEA without arguments. HEVEA will read its standard input and print the translation on its standard output. For instance:
# hevea
$x \in \mathcal{E}$
^D
<span style="font-style:italic">x</span> ∈ <span style="color:red"><span style="font-style:italic">E</span></span>
Incidentally, notice that the symbol “∈” translates to the appropriate numerical character reference and that the calligraphic letter “E” renders as a red “E”. You can find some more elaborate examples in the on-line documentation.
hevea-2.36-manual/manual005.html 0000644 0043171 0051216 00000065732 14252364056 016451 0 ustar maranget cristal
Sequence of spaces normally are translated into one single space.
Newlines in the input document undergo a special treatement.
A newline triggers a special scanning mode that reads all following
spaces and newlines. In case at least one additional newline character
is read, then HEVEA executes the \par command.
Otherwise, HEVEA outputs a single newline character.
This process approximates TEX process for introducting paragraph
breaks and, as a result, empty lines produce paragraph breaks.
Space after commands with no argument is skipped (as in LATEX) — however this is not true in math mode, as explained in section 3.2.1.
The following two subsections describe management of paragraphs and spaces after command sequences in greater detail. They can be skipped in first reading.
Paragraphs are rendered by the means of p elements.
HEVEA is a bit simplistic in breaking paragraphs and spurious paragraphs
may be present in the final html document.
Normally, as HEVEA never outputs p elements whose contents is
made of spaces only, this should not happen very often.
Unfortunately, some commands do not produce any output in LATEX,
while they do produce output in HEVEA: those commands
are \label, \index etc.
HEVEA translates
\label{name} into the anchor
<a id="name"></a>. As a result, the following
source fragment will introduce a spurious paragraph.
This a first paragraph.
\label{label}
This is another paragraph.
Indeed, whe have the following translation:
<p>This a first paragraph.</p> <p><a id="label"></a></p> <p>This is another paragraph.</p>
Which your browser renders as follows — with additional borders
emphasizing p elements.
This a first paragraph.
This is another paragraph.
Most of the time, such extra paragraphs remain unnoticed. Of course, they can be supressed by erasing one of the empty lines. For instance:
This a first paragraph.
\label{label}
This is another paragraph.
A similar situation occurs when a sectioning command is followed by
\label and a paragraph break:
\section*{A section}\label{section:label}
First paragraph.
Produced html is, after a few cosmetic simplifications:
<h2 class="section">A section</h2> <p><a id="section:label"></a></p> <p>First paragraph.</p>
Output is so, because closing the element h2 implies re-opening
a new paragraph.
Your browser renders the above html fragment as follows:
A section
First paragraph.
Here, two possible re-writing of source are:
\section*{A\label{section:label} section}
First paragraph.
| \section*{A section}
\label{section:label}First paragraph.
|
In all cases, this amounts to avoiding a paragraph whose contents
consists in a sole \label command.
Spurious paragraphs are more easily seen by running hevea
with the command-line option -dv, which instructs
hevea to add border on some of the elements it produces,
including p elements.
Space after commands with no argument is skipped. Consider the following example:
\newcommand{\open}{(}
\newcommand{\close}{)}
\open text opened by ``\verb+\open+''
and closed by ``\verb+\close+''\close.
We get:
(text opened by “\open” and closed by “\close”).
In the output above, the space after \open does not
find its way to the output.
More generally,
HEVEA tries to emulate LATEX behaviour in all situations, but
discrepancies probably exist.
Thus, users are invited to make explicit what they want.
This is good practice anyway, because LATEX is mysterious
here. Consider the following example, where the \tryspace
macro is first applied and then expansed by hand:
\newcommand{\bfsymbol}{\textbf{symbol}}
\newcommand{\tryspace}[1]{#1 XXX}
Some space: \tryspace{\bfsymbol}\\
No space: \bfsymbol XXX
Spacing is a bit chaotic here,
the space after symbol remains when #1 is substituted for it
by LATEX (or HEVEA).
Some space : symbol XXX No space : symbolXXX
Note that, if a space before “XXX” is wanted, then one should probably write:
\newcommand{\tryspace}[1]{#1{} XXX}
Finally, whether the tabulation character is a space or not is random, so avoid tabs in your source document.
HEVEA math mode is not very far from normal text mode, except that all letters are shown in italics and that space after macros is echoed.
However, typesetting math formulas in html rises two difficulties. First, formulas contain symbols, such as Greek letters; second, even simple formulas do not follow the simple basic typesetting model of html.
By contrast with LATEX, spaces from the input are significant in
math mode, this
feature allows users to instruct HEVEA
on how to put space in their formulas.
For instance, \alpha\rightarrow\beta is typeset without spaces between
symbols, whereas \alpha \rightarrow \beta produces these spaces.
|
Note that LATEX ignores spaces in math mode, so that users can freely adjust HEVEA output without changing anything to LATEX output.
\in: ∈ \notin: ∉ \int: ∫ \prod: ∏ \preceq: ≼ \prec: ≺ \leq: ≤ \geq: ≥ \cup: ∪ \cap: ∩ \supset: ⊃ \subset: ⊂ \supseteq: ⊇ \subseteq: ⊆
With respect to previous versions of HEVEA since the begining, the treatment of symbols has significantly evolved. Outputting symbols is now performed by using Unicode character references, an option that much more complies whith standards than the previous option of selecting a “symbol” font. Observe that this choice is now possible, because more and more browsers correctly display such references. See Figure 1 for a few such symbols.
However, this means that ancient or purposely limited browsers (such as text-oriented browsers) cannot display maths, as translated by HEVEA. For authors that insist on avoiding symbols that cannot be shown by any browser, HEVEA offers a degraded mode that outputs text in place of symbols. HEVEA operates in this mode when given the -textsymbols command-line option. Replacement text is in English. For instance. the “∈” symbol is replace by “in”. This is far from being satisfactory, but degraded mode may be appropriate for documents than contain few symbols.
Apart from containing symbols, formulas specify strong typesetting constraints: sub-elements must be combined together following patterns that departs from normal text typesetting. For instance, fractions numerators and denominators must be placed one above the other. HEVEA handles such constraints in display mode only.
The main two operating modes of HEVEA are text mode and display mode. Text mode is the mode for typesetting normal text, when in this mode, text items are echoed one following the other and paragraph breaks are just blank lines, both in input and output. The so called displayed-paragraph environments of LATEX (such as center or quote) are rendered by html block-level elements (such as div or blockquote). Rendering is correct becauses both LATEX displayed environments and html block-level elements start a new line. Conversly, since opening a html block-level elements means starting a new line, any text that sould appear inside a paragraph must be translated using only html text-level elements. HEVEA chooses to translate in-text formulas that way.
HEVEA display mode allows more control on text placement, since
entering display mode means opening
a html table element and that tables allow to control the
relative position of their sub-elements.
Displays come in two flavor, horizontal displays and vertical
displays.
An horizontal display is a one-row table, while a vertical display is
a one-column table. These tables holds display sub-elements, displays
sub-elements being centered vertically in horizontal display mode and
horizontally in vertical display mode.
Display mode is first opened by opening a displaymath environment
(e.g. by $$
or \[).
Then, sub-displays are opened by LATEX constructs which require
them.
For instance, a displayed fraction (\frac) opens a vertical display.
The distinction between text and display modes clearly appears while
typesetting math formulas.
An in-text formula such as
$\int_1^2 xdx = \frac{3}{2}$ appears as:
∫12 xdx =3/2,
while the same formula has a better aspect in display mode:
| ∫ |
| xdx = |
|
As a consequence, HEVEA is more powerful in display mode and formulas should be displayed as soon as they get a bit complicated. This rule is also true in LATEX but it is more strict in HEVEA, since html capabilities to typeset formulas inside text are quite poor. In particular, it is not possible to get in-text “real” fractions or in-text limit-like subscripts.
Users should remember that HEVEA is not TEX or LATEX and that HEVEA author neither is D. E. Knuth nor L. Lamport. Thus, some formulas may be rendered poorly. For instance, two fractions with different denominator and numerator height look strange.
| = |
|
The reason is that vertical displays in an horizontal display are html tables that always get centered in the vertical direction. Such a crude model cannot faithfully emulate any TEX box placement.
Users can get an idea on how HEVEA combines elements in display mode
by giving the -dv command-line option, which
instructs HEVEA to add
borders to the table elements introduced by displays.
By contrast with formulas, which HEVEA attempts to render with
text-level elements only when they appear inside paragraphs, LATEX arrays
always translate to the
block-level element table, thereby introducing non-desired line
breaks before and after in-text arrays.
As a consequence, in-text arrays yield an acceptable output, only while
alone in a paragraph.
Consider the following source:
This is a small array:
\begin{tabular}{|cc|}
\hline item-1 & item-2 \\
\hline\end{tabular}. Next sentence.
We get:
This is a small array:. Next sentence.
item-1 item-2
However, since in some sense, all html tables are displayed, the
array and tabular environments implicitly open display
mode, thus allowing a satisfactory typesetting of formulas in
arrays. More precisely, array elements whose column format
specification is l, c or r are typeset in display
mode (see section B.10.2).
When HEVEA thinks it cannot translate a symbol or construct properly, it issues a warning. This draws user attention onto a potential problem. However, rendering may be correct.
In the following (silly) example, HEVEA gets nervous because of
the complicated length given as argument to \hspace:
\newlength{\mylength}\setlength{\mylength}{5pt}
\begin{tabular}{c@{\hspace{\mylength}}c}
Before & After
\end{tabular}
Running HEVEA on this input produces a warning:
# hevea manual.tex ... manual.tex:697: Warning: Command not found: \mylength manual.tex:697: Warning: \hspace with arg '' ...
However the final rendering is correct:
Before After
Note that all warnings can be suppressed with the -s (silent)
option.
When a warning reveals a real problem, it can often be cured by
writing a specific macro. The next two sections introduce HEVEA
macros, then section 4 describes how to proceed with
greater detail.
Just like LATEX, HEVEA can be seen as a macro language, macros are rewritten until no more expansion is possible. Then, either some characters (such as letters, integers…) are outputed or some internal operation (such as changing font attributes, or arranging text items in a certain manner) are performed.
This scheme favors easy extension of program capabilities by users. However, predicting program behaviour and correcting errors may prove difficult, since final output or errors may occur after several levels of macro expansion. As a consequence, users can tailor HEVEA to their needs, but it remains a subtle task. Nevertheless, happy LATEX users should enjoy customizing HEVEA, since this is done by writing LATEX code.
LATEX and html differ in many aspects. For instance, LATEX allows fine control over text placement, whereas html does not. More symbols and font attributes are available in LATEX than in html. Conversely, html has font attributes, such as color, which standard LATEX has not.
Therefore, there are many situations where HEVEA just cannot
render the visual effect of LATEX constructions. Here some choices
have to be made. For instance, calligraphic letters (\mathcal)
are rendered in red.
If you are not satisfied with HEVEA rendering of text style
declarations, then you
can choose your own, by redefining the \cal
macros, using \renewcommand, the macro redefinition operator of
LATEX. The key point is that you need not worry about HEVEA
internals: just redefine the old-LATEX style text-style
declarations (i.e. \it, \sc, etc.) and everything should
get fine:
\renewcommand{\sc}{\Huge}
\renewcommand{\cal}{\em}
(See sections 4 and 5 on how to make such changes while leaving your file processable by LATEX, and section 10.2 for a more thorough descripton of customizing type styles).
With such redefinitions, we get:
This is small caps and this is CALLIGRAPHIC LETTERS
Note that many of LATEX commands and environments are defined in the hevea.hva file that HEVEA loads before processing any input. These constructs are written using LATEX source code, in the end they invoke HEVEA internal commands.
Other LATEX constructs, such as
LATEX key constructs or HEVEA internal commands (see section 8.3),
that require special processing are defined
in HEVEA source code.
However, the vast majority of these definitions can be overridden by a
redefinition.
This may prove useless, since there is little point in
redefining core constructs such as \newcommand for instance.
hevea-2.36-manual/manual046.html 0000644 0043171 0051216 00000006675 14252364057 016460 0 ustar maranget cristal
The following people contributed to HEVEA development:
alltt environment.
-text and -info
output modes (see section 11).
hevea-2.36-manual/manual003.png 0000644 0043171 0051216 00000006130 14252364055 016251 0 ustar maranget cristal PNG
IHDR 5 . &iCCPicc HgPY<@BPC*%Z(ҫ@PEl+4EE\"kE t,ʺqQAYp ?{ossp e{bRɎ(tջ {i常r)t eJOYLgWX\2XyKο,]~
)sT8بlOrTzV $G&D~S GfDnr&AltL:5204_gK!FgE_z s z t@WOm| :3z
@(U t08 |A $`( E` 8@-h M<.L@ށA2@F 7
Bh( ʀrPT
UAuP t݄84
}aXև0v}p4
^O 6< "@]p$BV)GVC!Bd h(&JerFTVT1
uՁECDh2Z @Ёht ]nDѓw aa0Θ L f3sӆL`X VkaӱJI%v G)p`\.Wk]
p xq:o;IA"X| q
B+aH$͉^XvbqD%iRi/82!
L ے&US{1O,BlXXؐ+
NP6Pr(3;Yq8W'w78 )Za 4)ձkXN=Nkhp4{m{
%|$sq:ȏq"NpOyc#s 78']N,eIFU8 LATEX comments that start with “
Command names follow strict LATEX syntax. That is, apart from
Users are strongly advised to follow strict LATEX syntax for
arguments. That is, mandatory arguments are enclosed in curly braces
Also note that, by contrast with LATEX, comments are parsed during
argument scanning, as an important consequence brace nesting is also
checked inside comments.
With respect to previous versions,
HEVEA has been improved as regards emulation of complicated
argument passing. That is,
commands and their arguments can now appear in
different static text bodies. As a consequence,
HEVEA correctly processes the following source:
The definition of The above example arguably is no “legal” LATEX,
but HEVEA handles it.
Of course, there remains
numerous “clever” LATEX tricks that exploits TEX internal
behaviour, which HEVEA does not handle.
For instance consider the following source:
LATEX typesets the text “In bold” using bold font, leaving
the rest of the text alone. While HEVEA typesets everything using
bold font. Here is HEVEA output:
Note that, in most similar situations, HEVEA will likely crash. As a conclusion of this important section,
Users are strongly advised to use ordinary command names and
curly braces and not to think too much the TEX way. Environment opening and closing is performed like in LATEX, with
It is not advised to use
Fragile commands are not relevant to HEVEA and
Scope rules are the same as in LATEX.
I am a bit lost here. However spaces in the output should correspond
to users expectations. Note that, to HEVEA being
invisible commands is a static property attached to command name. The It is possible to have pictures and graphics processed by
imagen (see section 6.1).
In the case of the picture environment
it remains users responsibility to explicitly choose
source chunks that will get rendered as images.
In the case of the commands from the graphics package,
this choice is made by HEVEA. For instance consider the following picture:
Users should enclose all picture elements in a
This will result in normal processing by LATEX and image inclusion
by HEVEA: All commands from the graphics package are implemented using the
automatic image inclusion feature.
More precisely, the outermost invocations of
the For instance, consider a document doc.tex that
loads the graphics package and that includes some (scaled)
images by:
Then, issuing the following two commands:
yields html that basically consists in three image links,
the images being generated by imagen.
Since the advent of pdflatex,
using HEVEA partly implements the color package.
Implemented commands are Colours are defined by
As regards color models, HEVEA implements the rgb,
cmyk, hsv and hls color models.
In those models, color specifications are floating point numbers less
than one.
For instance, here is the definition for the red color:
The named color model is also supported, in this model color
specification are just names…
Named colours are the ones of dvips.
There are at least three ways to use colours from the named
model.
That is:
Which yields:
HEVEA also implements the
Those two commands accept an optional first argument that specifies
the color model, as Colours should be used carefully. Too many colours
hinders clarity and some of the colours may not be readable on the
document background color.
With respect to the LATEX color package, HEVEA features
an additional
bgcolor environment, for changing the background color of some
subparts of the document.
The bgcolor environment is a displayed environment and it
normally starts a new line.
Simple usage is The bgcolor environment is implemented by one-cell
The resulting output will be red letters
on a yellow background and no padding:
High-level colours are color names
defined with One changes the high-level high-color into a low-level color by
There is also HEVEA home page is http://hevea.inria.fr/. It contains links to the
on-line manual
and to the distribution. The author can be contacted at Luc.Maranget@inria.fr.
HEVEA can be freely used and redistributed without modifications.
Modifying and redistributing HEVEA implies a few constraints.
More precisely, HEVEA is distributed under the terms of the
Q Public License, but HEVEA binaries include the Objective Caml
runtime system, which is distributed under the Gnu Library General
Public License (LGPL).
See the LICENSE file for details. The manual itself is distributed under the terms of
the
Free Document Dissemination Licence.
Starting with version 1.08, HEVEA offers support for style sheets
(of the CSS variant see [CSS-2]). Style sheets provide enhanced expressiveness. For instance, it is now possible
to get “real” (whatever real means here) small caps in html, and in a
relatively standard manner. There are other, discrete, maybe
unnoticeable, similar enhancements. However, style sheets mostly offer an additional mechanism to
customise their documents to HEVEA users. To do so, users should
probably get familiar with how HEVEA uses style sheets in the first
place. HEVEA interest for style sheets is at the moment confined to
block-level elements ( As an example the LATEX command
By default, most styles are undefined, and default rendering of
block-level elements applies. However, some packages (such as, for
instance fancysection, see Section B.16.4) may
define them.
If you wish to change the style of section headers, loading the
fancysection package may prove appropriate (see B.16.4).
However, one can also proceed more directly, by appending new
definitions to the document style
sheet, with the command
This declaration adds some style element to the
subsection class (notice the dot!):
blocks that declare to belong to the class
will show dark-blue text, some padding
(space inside the box) is added and a border will be drawn around the block.
These specification will normally affect all subsections in the document.
Given the previous style definition, the sectioning command
should yield:
The following points are worth noticing:
In this very document, all verbatim environments appear over
a light green background, with small left and right margins.
This has been performed by simply issuing the following command in
the document preamble.
Observe that, in the explicit numerical color argument above, the
hash character “#” has to be escaped.
One can also change the style class attached to a given instance of
an environment and thus control styling of environments more precisely. As a matter of fact, the name of the class attribute of
environment env is referred to through an indirection, by
using the command
Observe how the class of environment verbatim is changed from
its default value to the
new value myverbatim. The change remains active until the
end of the current group (here, the “}” at the end). Then, the class
of environment verbatim is restored to its default value
— which happen to be verbatim.
This example also shows two new ways to specify colours in style
definition, with a
conventional html color name (here maroon) or as
a high-level color (see Section B.14.2), given as an argument to
the A good way of specifying style class changes probably is by defining
new environments.
Then, we can use Generally, the styling of environment env is performed through
the commands
Concretely, this means that most of the environments are styled through
an homonymous style class. Here is a non-exhaustive list of such
environments
All sectioning commands ( List making-environment introduce extra style classes for items.
More specifically, for list-making environments
itemize and enumerate,
That is, The description, trivlist and list environments
(which all get translated into DL elements) are styled in
a similar way, internal DT and DD elements being
styles through names dt-env and
dd-env respectively.
The command
Users can impact on title formatting by adding style in the
appropriate style classes.
For instance the following style class definitions:
will normally produce a title in dark blue, centered in a box, with
author and date in small-caps.
At the moment, due to the complexity of the task, environments
tabular and array cannot be styled as others
environments can be,
by defining an appropriate class in the preamble.
However, even for such constructs,
limited styling can be performed, by using
the divstyle environment.
The opening command As an example consider the style class definition below.
The intended behaviour is to add a black border around the inner block
(with some padding), and to have maroon text over
a light brown background. If we, for instance, enclose an itemize environment, the
resulting effect is more or less what we have expected:
However, enclosing a centered
tabular environment in a divstyle{ruled} one
is less satisfactory.
In the html version of this document,
one sees that the brown background extend on all the width
of the displayed page. This problem can be solved by introducing an extra table.
We first open an extra centered table and then only open the
divstyle environment.
This works because of the rules that
govern the width of html Another solution is to specify the display property
of the styling div block as being inline-block:
Our idea is highlight lists with a left border whose color fades
while lists are nested.
Such a design may be appropriate for tables of content, as
the one of this document.
The text above is typeset from the following LATEX source.
For simplicity, we assume a limit of four over the nesting depth of
toc environment.
We first define four style classes toc1, toc2,
toc3 and toc4 in the document preamble.
Since those classes are similar, a command
The toc environment uses a counter to record nesting depth.
Notice how the style class of the itemize environment is
redefined before
The outputted html is:
HACHA now produces an additional file: a style sheet, which is
shared by all the html files produced by HACHA.
Please refer to section 7.1 for details.
By default, style declarations defined with
The HEVEA command
produces the following html text in the
To yield some effect, Notice that the argument to
At the moment, style class definitions cumulate, and appear
in the Those limitations do not apply of course to style classes whose
names are new, since there cannot be default definitions for them.
Then, linking with external style sheets can prove useful to
promote uniform styling of several documents produced by HEVEA. c ڵk`W(|rRWW'uuu7n\*Y <{1tRt)&^Cy㉓'{! _xQ~y 09`664FYk
B.1 Commands and Environments
B.1.1 Command Names and Arguments
%” and end at end of line are ignored and produce no output.
Usually, HEVEA ignore such comments. However, HEVEA processes
text that follows “%HEVEA” and some other comments have a specific meaning to it (see
section 5.3).#, $, ~, _ and ^, they either are
“\” followed by a single non-letter character or
“\” followed by a sequence of letters.
Additionally, the letter sequence may be preceded by “@”
(and this is the case of many of HEVEA internal commands), or
terminated by “*” (starred variants are implemented as plain
commands).{… } and braces inside arguments must be properly
balanced.
Optional arguments are enclosed in square brackets […
].
However, HEVEA does its best to read arguments even when they are
not enclosed in curly braces.
Such arguments are a single, different from “\”, “{”
and “ ”, character or
a command name.
Thus, constructs such as \'ecole,
$a_1$ or $a_\Gamma$ are
recognized and processed as école a1 and aΓ.
By contrast, a^\mbox{...} is not recognized
and must be written a^{\mbox{...}}.\newcommand{\boite}{\textbf}
\boite{In bold}
\boite makes it reduces as
\textbf and HEVEA succeeds in fetching the argument
“{In bold}”. We get
In bold
\newcommand{\boite}[1]{\textbf#1}
\boite{{In bold}, Not in Bold.}
In bold, Not in Bold.
B.1.2 Environments
\begin{env} and
\end{env}.
The *-form of an environment is a plain environment.\env and
\endenv in place of \begin{env} and
\end{env}.B.1.3 Fragile Commands
\protect is
defined as a null command.B.1.4 Declarations
B.1.5 Invisible Commands
B.1.6 The \\ Command
\\ and \\* commands are the same, they perform a
line break, except inside arrays where they end the current row.
Optional arguments to \\ and \\* are ignored.
hevea-2.36-manual/manual017.html 0000644 0043171 0051216 00000001513 14252364056 016437 0 ustar maranget cristal
hevea-2.36-manual/manual036.html 0000644 0043171 0051216 00000040157 14252364056 016447 0 ustar maranget cristal
B.14 Pictures and Colours
B.14.1 The picture environment and the graphics
Package
\newcounter{cms}
\setlength{\unitlength}{1mm}
\begin{picture}(50,10)
\put(0,7){\makebox(0,0)[b]{cm}}
\multiput(10,7)(10,0){5}{\addtocounter{cms}{1}\makebox(0,0)[b]{\arabic{cms}}}
\multiput(1,0)(1,0){49}{\line(0,1){2.5}}
\multiput(5,0)(10,0){5}{\line(0,1){5}}
\thicklines
\put(0,0){\line(1,0){50}}
\multiput(0,0)(10,0){6}{\line(0,1){5}}
\end{picture}
toimage
environment (or inside %BEGIN IMAGE… %END IMAGE comments) and insert an \imageflush command, where they want
the image to appear in html output:
%BEGIN IMAGE
\newcounter{cms}
\setlength{\unitlength}{1mm}
\begin{picture}(50,10)
...
\end{picture}
%END IMAGE
%HEVEA\imageflush
\includegraphics, \scalebox,
etc. commands are sent to the image image file and there will
be one image per outermost invocation of these commands.\begin{center}
\scalebox{.5}{\includegraphics{round.ps}}
\scalebox{.75}{\includegraphics{round.ps}}
\includegraphics{round.ps}
\end{center}
# hevea doc.tex
# imagen doc
\includegraphics to insert bitmap images
(e.g. .gif or .jpg)
became frequent.
In that case, users are advised not to use HEVEA default
implementation of the graphics package.
Instead, they may use a simple variation of
the technique described in Section 8.2.B.14.2 The color Package
\definecolor, \color,
\colorbox,
\textcolor, \colorbox and \fcolorbox.
Other commands do not exist.
At startup,
colours black, white,
red, green, blue,
cyan, yellow and magenta are
pre-defined.\definecolor{name}{model}{spec},
where name is the color name, model is the color
model used, and spec is the color specification according to
the given model.
Defined colours are used by the declaration
\color{name} and by the command
\textcolor{name}{text}, which
change text color.
Please note that, the \color declaration
accepts color specifications directly
when invoked as
\color[model]{spec}.
The \textcolor command has a similar feature.\definecolor{red}{rgb}{1, 0, 0}
GreenYellow,
Yellow,
Goldenrod,
Dandelion,
Apricot,
Peach,
Melon,
YellowOrange,
Orange,
BurntOrange,
Bittersweet,
RedOrange,
Mahogany,
Maroon,
BrickRed,
Red,
OrangeRed,
RubineRed,
WildStrawberry,
Salmon,
CarnationPink,
Magenta,
VioletRed,
Rhodamine,
Mulberry,
RedViolet,
Fuchsia,
Lavender,
Thistle,
Orchid,
DarkOrchid,
Purple,
Plum,
Violet,
RoyalPurple,
BlueViolet,
Periwinkle,
CadetBlue,
CornflowerBlue,
MidnightBlue,
NavyBlue,
RoyalBlue,
Blue,
Cerulean,
Cyan,
ProcessBlue,
SkyBlue,
Turquoise,
TealBlue,
Aquamarine,
BlueGreen,
Emerald,
JungleGreen,
SeaGreen,
Green,
ForestGreen,
PineGreen,
LimeGreen,
YellowGreen,
SpringGreen,
OliveGreen,
RawSienna,
Sepia,
Brown,
Tan,
Gray,
Black,
White.
\color and \textcolor.
\definecolor{rouge-brique}{named}{BrickRed}\textcolor{rouge-brique}{Text as a brick}.
\textcolor[named]{BrickRed}{Text as another brick}.
\textcolor{BrickRed}{Text as another brick}.
\colorbox and \fcolorbox commands.
\colorbox{red}{Red background},
\fcolorbox{magenta}{red}{Red background, magenta border}.
Red background,
Red background, magenta border.
\textcolor does:
\fcolorbox[named]{RedOrange}{Apricot}{Apricot background, RedOrange border}.
Apricot background, RedOrange border.
B.14.2.1 The bgcolor environment
\begin{bgcolor}{color}…
\end{bgcolor}, where
color is a color defined with \definecolor.
Hence the following source yield a paragraph with a red background:
\begin{bgcolor}{red}
\color{yellow}Yellow letters on a red backgroud
\end{bgcolor}
Yellow letters on a red background
table element, it takes an
optional argument that is used as an attribute for the inner td
element (default value is style="padding:1em").
Advanced users may change the default, for instance as:
\begin{bgcolor}[style="padding:0"]{yellow}
\color{red}Red letters on a yellow backgroud
\end{bgcolor}
Red letters on a yellow background, no padding
B.14.2.2 From High-Level Colours to Low-Level Colours
\definecolor.
Low-level colours are html-style colours.
That is, they are either one of the sixteen conventional colours black,
silver etc., or a RGB hexadecimal color specification of the form
"#XXXXXX".\@getcolor{high-color}.
Low-level colours are appropriate inside html attributes and as
arguments to the \@fontcolor internal macro.
An example of \@getcolor usage can be found at the end of
section 8.5.\@getstylecolor command that acts
like\@getcolor, except that it does not output the double
quotes around RGB hexadecimal color specifications.
Such low-level colours are appropriate for style definitions in
cascading style sheets [CSS-2]. See
Section 9.3 for an example.
hevea-2.36-manual/manual010.png 0000644 0043171 0051216 00000011643 14252364056 016255 0 ustar maranget cristal PNG
IHDR ~ 1 bKGD ̿ pHYs a a?i tIME 2p IDATxϫ.Y?g dمhƀq1Dw. =,+,zxҁ0f1 .mN :BǞE=]]U]qX/ۿϷ Gne
*}7 7ozt}d.G&[ }3r 6mZ :B/ 4K ]m~ep?>#GS ٌ%#GFA@|Ԗm]`y/n\,>b@;A06(2iFNؿCƃ] u,
ٜ
'ŷiJ4) 2]; iIm3fo,7|4%mjCjirv *ۢ@ @˯&Rz/? PM
CSG 9 =>Jzd>JX aCGF /`bPC
rS { c%CC~cG+4ߚKc1$WM@-zȾa )0h7p͋ME 4^D)}&c03}ڥ
/pG?NԀ^4 +h47ud )\0 t@M!B4zJ 8wm.d (O]C uxarʁ.
| ICl"R{1 .t "" f`jyDFN}ƭأwqsAna%" >#[srhũ7q}vP$9/͜uKG6KrН wB*%9f'6oZY*:9 Op( ZҟyW'dAIcV͞v\#03dPӢ%4@﹒1aN%GY0IQS8FZ һZ5i0.^ɞ& |.9mZr':\v-U$ N{ٝlˇb@9fAT :oyه[Zgh8o(0|ϟQ3H<-!k8p/F҃8me}e}?:0`( 0;
s'l
4P=U@ @.є F ,w~x~bk\CO9ݸƳx{_@ s4
x(
NIGXD )-30|]ۤNg
'z6 7Nχn<)
."%% !wG{S4
C.3 Availability
C.3.1 Internet stuff
C.3.2 Law
hevea-2.36-manual/manual019.html 0000644 0043171 0051216 00000062222 14252364056 016445 0 ustar maranget cristal
9 Support for style sheets
9.1 Overview
div, table, H<n>,
etc.).
The general principle is as follows: when a command or an
environment gets translated into a block-level element,
the opening tag of the block level element has a
class="name" attribute, where name is the
command or environment name.\subsection
is implemented with the element h3, resulting in
html output of the form:
<h3 class="subsection">
...
</h3>
\newstyle.
For instance, here is a \newstyle to add style for subsections.
\newstyle{.subsection}{padding:1ex;color:navy;border:solid navy;}
\subsection*{A styled subsection heading}
A styled subsection heading
\newstyle commands must appear
in the document preamble, i.e. before \begin{document}.
\newstyle commands are processed.
9.2 Changing
the style of all instances of an environment
\newstyle{.verbatim}{margin:1ex 1ex;padding:1ex;background:\#ccffcc;}
9.3 Changing the style of some instances of an environment
\getenvclass{env}.
The class attribute can be changed with the command
\setenvclass{env}{class}.
The \setenvclass command internally defines a command
\env@class, whose content is read
by the \getenvclass command. As a consequence, the class
attribute of environments follows normal scoping rules.
For instance, here is how to change the style of one verbatim
environment.
{\setenvclass{verbatim}{myverbatim}
\begin{verbatim}
This will be styled through class 'myverbatim', introduced by:
\newstyle{.myverbatim}
{margin:1ex 3x;padding:1ex;
color:maroon;
background:\@getstylecolor[named]{Apricot}}
\end{verbatim}}\@getstylecolor internal command
(here Apricot from the named color model).\newenvironment{flashyverbatim}
{\setenvclass{verbatim}{myverbatim}\verbatim}
{\endverbatim}
\begin{flashyverbatim}…
\end{flashyverbatim} to get verbatim environments style with
the intended myverbatim style class.
This text is typeset inside the environment
\emph{flashyverbatim}, and hence with the \emph{myverbatim}
style.
9.4 Which class affects what
\getenvclass{env}
and \setenvclass{env}{…},
with \getenvclass{env} producing the
default value of env.
figure, table, itemize, enumerate, list, description,
trivlist, center, flushleft, flushright, quote,
quotation, verbatim, abstract, mathpar (cf
Section B.17.16), lstlisting
(cf. Section B.17.14), etc.
\part, \section etc.)
output H<n> block-level elements, which are styled
through style classes named part, section, etc.li elements are styled as follows:
<ul class="itemize">
<li class="li-itemize"> ...
</ul>
<ol class="enumerate">
<li class="li-enumerate"> ...
</ol>
li elements are styled as environments, the key name
being li-env.9.5 A few examples
9.5.1 The title of the document
\maketitle formats the document
title within a table element, with
class title, for display. The name of the title is displayed
inside block h1, with class titlemain, while all other
information (author, date) are displayed inside block h3, with class
titlerest.
<table class="title">
<tr>
<td style="padding:1ex">
<h1 class="titlemain">..title here..</h1>
<h3 class="titlerest">..author here..</h3>
<h3 class="titlerest">..date here..</h3>
</td>
</tr>
</table>
\newstyle{.title}
{text-align:center;margin:1ex auto;color:navy;border:solid navy;}
\newstyle{.titlerest}{font-variant:small-caps;}
Title
Date
Author
9.5.2 Enclosing things in a styled div
\begin{divstyle}{class}
takes the name of a class as
an argument, and translates to <div class="class">.
Of course the closing command \end{divstyle} translates to
</div>.
The limitation is that the enclosed part may generate more html
blocks, and that not all style attribute defined in class class
class will apply to those inner blocks.\newstyle{.ruled}{border:solid black;padding:1ex;background:\#eeddbb;color:maroon}
\begin{divstyle}{ruled}
\begin{itemize}
\item A ruled itemize
\item With two items.
\end{itemize}
\end{divstyle}
\begin{divstyle}{ruled}
\begin{center}\begin{tabular}{|c|c|}
\hline \bf English & \bf French\\ \hline
Good Morning & Bonjour\\ Thank You & Merci\\ Good Bye & Au Revoir\\ \hline
\end{tabular}\end{center}
\end{divstyle}
English French Good Morning Bonjour Thank You Merci Good Bye Au Revoir \begin{center}\begin{tabular}{c}
\begin{divstyle}{ruled}
\begin{tabular}{|c|c|}
\hline \bf English & \bf French\\ \hline
Good Morning & Bonjour\\ Thank You & Merci\\ Good Bye & Au Revoir\\
\hline
\end{tabular}
\end{divstyle}
\end{tabular}\end{center}
table elements, which yield
minimal width. This trick is used in
numerous places by HEVEA, for instance in document titles, and looks
quite safe.
English French Good Morning Bonjour Thank You Merci Good Bye Au Revoir \newstyle{.ruledbis}
{border:solid black;padding:1ex;background:\#eeddbb;color:maroon;display:inline-block;}
English French Good Morning Bonjour Thank You Merci Good Bye Au Revoir 9.5.3 Styling the itemize environment
\begin{toc}
\item Part~A
\begin{toc}
\item Chapter~I
\begin{toc}
\item Section~I.1
\item Section~I.2
\end{toc}
...
\end{toc}
\end{toc}
\newtocstyle is
designed.
\newcommand{\newtocstyle}[2]
{\newstyle{.toc#1}{list-style:none;border-left:1ex solid #2;padding:0ex 1ex;}}
\newtocstyle{1}{\@getstylecolor{Sepia}}
\newtocstyle{2}{\@getstylecolor{Brown}}
\newtocstyle{3}{\@getstylecolor{Tan}}
\newtocstyle{4}{\@getstylecolor{Melon}}
\begin{itemize}.
\newcounter{toc}
\newenvironment{toc}
{\stepcounter{toc}\setenvclass{itemize}{toc\thetoc}\begin{itemize}}
{\addtocounter{toc}{-1}\end{itemize}}
<ul class="toc1"><li class="li-itemize">
Part A
<ul class="toc2"><li class="li-itemize">
Chapter I
<ul class="toc3"><li class="li-itemize">
Section I.1
<li class="li-itemize">Section I.2
...
</ul>
</ul>
9.6 Miscellaneous
9.6.1 HACHA and style sheets
9.6.2 Producing an external style sheet
\newstyle go into the header of the html document
doc.html.
However, one can send those declaration into an external style file,
whose name is doc.css.
Then, HEVEA automatically relates doc.html to
its style sheet doc.css.
To achieve this behaviour, it suffices to set the value of the boolean
register externalcss to true, by issuing the command
\externalcsstrue in the preamble of the source document.
Notice that HEVEA output still can be processed by HACHA, with
correct behaviour.9.6.3 Linking to external style sheets
\loadcssfile{url} allows the
user to link to an external style sheet (like the link option for
HTML). The command takes an url of the external
sheet as argument and emits the HTML text to
link to the given external style sheet. As an example, the command
\loadcssfile{../abc.css}
head of the document.
<link rel="stylesheet" type="text/css" href="../abc.css">
\loadcssfile must appear in the document
preamble. Several \loadcssfile commands can be issued. Then
the given external style sheets appear in the output, following source
order.\loadcssfile is processed. Thus, if it
contains special characters such as “#” or “$”, those must be specified
as \# and \$ respectively.
A viable alternative would be to quote
the argument using the \url command from the url
package (see Section B.17.12).9.6.4 Limitations
style element in the order they are given in the
document source. There is no way to cancel the default class
definitions performed by HEVEA before it starts to process the
user’s document.
Additionally, external style sheets specified with \loadcssfile
appear before style classes defined with \newstyle.
As a consequence (if I am right), styles
declared by \newstyle take precedence over those contained in
external style sheets. Thus, using external style-sheets, especially
if they alter the styling of elements, may produce awkward results.
hevea-2.36-manual/manual.hind 0000644 0043171 0051216 00000045624 14252364054 016176 0 ustar maranget cristal \begin{indexenv}
\indexitem `` '' (space), \@locref{hevea_default157}{B.3.1}
\begin{indexenv}
\indexitem after macro, \@locref{hevea_default2}{3.1.2}
\begin{indexenv}
\indexitem in math, \@locref{hevea_default4}{3.2.1}, \defocc{\@locref{hevea_default175}{B.7.7}}
\end{indexenv}
\end{indexenv}
\indexspace
\indexitem \texttt{\#\#}\textit{n}, \@locref{hevea_default211}{B.16.2}
\indexspace
\indexitem \texttt{-
todir} (\texttt{imagen} option), \@locref{hevea_default141}{10.6}
\indexitem \texttt{-dv} (\texttt{hevea} option), \@locref{hevea_default1}{3.1.1}, \@locref{hevea_default6}{3.2.3}
\indexitem \texttt{-e} (\texttt{hevea} option), \@locref{hevea_default188}{B.11.4}
\indexitem \texttt{-fix} (\texttt{hevea} option), \@locref{hevea_default28}{6.1}, \@locref{hevea_default143}{10.7}, \@locref{hevea_default162}{B.4.3}, \@locref{hevea_default183}{B.11.1}, \@locref{hevea_default280}{C.1.5}, \@locref{hevea_default281}{C.1.6}
\indexitem \texttt{-gif} (\texttt{imagen} option), \@locref{hevea_default139}{10.5}
\indexitem \texttt{-O} (\texttt{hevea} option), \@locref{hevea_default94}{8.4}, \@locref{hevea_default255}{B.17.14}
\indexitem \texttt{-o} (\texttt{hevea} option), \@locref{hevea_default271}{C.1.1.2}
\indexitem \texttt{-pdf} (\texttt{imagen} option), \@locref{hevea_default265}{B.17.17}
\indexitem \texttt{-textsymbols} (\texttt{hevea} option), \@locref{hevea_default5}{3.2.2}
\indexitem \texttt{-tocbis} (\texttt{hacha} option), \@locref{hevea_default38}{7.2.3}
\indexitem \texttt{-tocter} (\texttt{hacha} option), \@locref{hevea_default39}{7.2.3}
\indexitem \texttt{-w} (\texttt{hevea} option), \@locref{hevea_default144}{11.1}
\indexspace
\indexitem \texttt{\char92@addimagenopt}, \defocc{\@locref{hevea_default142}{10.7}}
\indexitem \texttt{\char92@addstyle}, \@locref{hevea_default91}{8.3}
\indexitem \texttt{\char92@bodyargs}, \@locref{hevea_default151}{B.2}
\indexitem \texttt{\char92@charset}, \@locref{hevea_default156}{B.2}
\indexitem \texttt{\char92@clearstyle}, \defocc{\@locref{hevea_default86}{8.3}}
\indexitem \texttt{\char92@close}, \defocc{\@locref{hevea_default81}{8.3}}, \@locref{hevea_default101}{8.5}, \@locref{hevea_default111}{8.5}
\indexitem \texttt{\char92@def@charset}, \defocc{\@locref{hevea_default115}{8.6}}, \@locref{hevea_default239}{B.17.4}
\indexitem \texttt{\char92@fontcolor}, \defocc{\@locref{hevea_default88}{8.3}}
\indexitem \texttt{\char92@fontsize}, \defocc{\@locref{hevea_default87}{8.3}}
\indexitem \texttt{\char92@footnotelevel}, \defocc{\@locref{hevea_default58}{7.3.7}}
\indexitem \texttt{\char92@getcolor}, \@locref{hevea_default112}{8.5}, \defocc{\@locref{hevea_default200}{B.14.2.2}}
\indexitem \texttt{\char92@getprint}, \defocc{\@locref{hevea_default77}{8.3}}, \@locref{hevea_default106}{8.5}
\indexitem \texttt{\char92@getstylecolor}, \@locref{hevea_default122}{9.3}, \defocc{\@locref{hevea_default201}{B.14.2.2}}
\indexitem \texttt{\char92@hevealibdir}, \defocc{\@locref{hevea_default270}{C.1.1.1}}
\indexitem \texttt{\char92@hr}, \defocc{\@locref{hevea_default79}{8.3}}
\indexitem \texttt{\char92@htmlargs}, \@locref{hevea_default152}{B.2}
\indexitem \texttt{\char92@meta}, \@locref{hevea_default153}{B.2}
\indexitem \texttt{\char92@nostyle}, \defocc{\@locref{hevea_default85}{8.3}}, \@locref{hevea_default107}{8.5}, \@locref{hevea_default108}{8.5}
\indexitem \texttt{\char92@open}, \defocc{\@locref{hevea_default80}{8.3}}, \@locref{hevea_default100}{8.5}, \@locref{hevea_default110}{8.5}
\indexitem \texttt{\char92@print}, \defocc{\@locref{hevea_default76}{8.3}}, \@locref{hevea_default105}{8.5}
\indexitem \texttt{\char92@print@u}, \@locref{hevea_default8}{4.2}, \defocc{\@locref{hevea_default78}{8.3}}, \@locref{hevea_default113}{8.5}, \@locref{hevea_default114}{8.6}
\indexitem \texttt{\char92@span}, \defocc{\@locref{hevea_default84}{8.3}}
\indexitem \texttt{\char92@style}, \defocc{\@locref{hevea_default82}{8.3}}
\indexitem \texttt{\char92@styleattr}, \defocc{\@locref{hevea_default83}{8.3}}
\indexspace
\indexitem \verb+\bigl,\bigr+ etc., \@locref{hevea_default173}{B.7.5}
\indexitem \verb+\boxed+, \@locref{hevea_default172}{B.7.5}
\indexitem \verb+\sqrt+, \@locref{hevea_default166}{B.7.3}
\indexspace
\indexitem \texttt{\char92addcontentsline}, \defocc{\@locref{hevea_default161}{B.4.3}}
\indexitem \texttt{\char92ahref}, \defocc{\@locref{hevea_default61}{8.1.1}}
\indexitem \texttt{\char92ahrefloc}, \@locref{hevea_default54}{7.3.6}, \defocc{\@locref{hevea_default64}{8.1.1}}
\indexitem \texttt{\char92ahrefurl}, \defocc{\@locref{hevea_default62}{8.1.1}}
\indexitem \texttt{amsmath} package, \@locref{hevea_default233}{B.17.1}
\indexitem \texttt{amssymb} package, \@locref{hevea_default234}{B.17.1}
\indexitem \texttt{\char92aname}, \@locref{hevea_default53}{7.3.6}, \defocc{\@locref{hevea_default65}{8.1.1}}
\indexitem argument\begin{indexenv}
\indexitem of commands, \@locref{hevea_default147}{B.1.1}
\indexitem of \texttt{\char92 input}, \@locref{hevea_default187}{B.11.4}
\end{indexenv}
\indexitem \texttt{array} package, \@locref{hevea_default235}{B.17.2}
\indexspace
\indexitem babel\begin{indexenv}
\indexitem languages, \@locref{hevea_default249}{B.17.11.2}
\end{indexenv}
\indexitem \texttt{babel} package, \@locref{hevea_default248}{B.17.11}
\indexitem \texttt{bgcolor} environment, \@locref{hevea_default109}{8.5}, \defocc{\@locref{hevea_default199}{B.14.2.1}}
\indexitem block-level elements, \@locref{hevea_default75}{8.3}
\indexitem browser configuration, \@locref{hevea_default282}{C.2}
\indexspace
\indexitem \texttt{calc} package, \@locref{hevea_default237}{B.17.3}
\indexitem \texttt{chapterbib} package, \@locref{hevea_default247}{B.17.10}
\indexitem \texttt{cleveref} package, \@locref{hevea_default268}{B.17.20}
\indexitem color\begin{indexenv}
\indexitem of background, \see{\texttt{\char92@bodyargs}}{\@locref{hevea_default150}{B.2}}
\indexitem of section headings, \@locref{hevea_default216}{B.16.4}
\end{indexenv}
\indexitem \texttt{\char92color}, \@locref{hevea_default195}{B.14.2}
\indexitem \texttt{color} package, \@locref{hevea_default194}{B.14.2}
\indexitem \texttt{\char92colorbox}, \@locref{hevea_default197}{B.14.2}
\indexitem \texttt{\char92colorsections}, \defocc{\@locref{hevea_default218}{B.16.4}}
\indexitem command\begin{indexenv}
\indexitem and arguments, \@locref{hevea_default146}{B.1.1}
\indexitem definition, \defocc{\@locref{hevea_default176}{B.8.1}}, \@locref{hevea_default203}{B.16.1.1}, \@locref{hevea_default212}{B.16.2}
\indexitem syntax, \@locref{hevea_default145}{B.1.1}
\end{indexenv}
\indexitem comment\begin{indexenv}
\indexitem \texttt{\%BEGIN IMAGE}, \@locref{hevea_default23}{5.3}
\indexitem \texttt{\%BEGIN LATEX}, \@locref{hevea_default22}{5.3}
\indexitem \texttt{\%END IMAGE}, \@locref{hevea_default25}{5.3}
\indexitem \texttt{\%END LATEX}, \@locref{hevea_default24}{5.3}
\indexitem \texttt{\%HEVEA}, \@locref{hevea_default21}{5.2.3}
\end{indexenv}
\indexitem \texttt{comment} package, \@locref{hevea_default241}{B.17.7}
\indexitem \texttt{\char92cutdef}, \@locref{hevea_default36}{7.2.2}, \@locref{hevea_default40}{7.2.4}
\indexitem \texttt{\char92cutend}, \@locref{hevea_default37}{7.2.2}, \@locref{hevea_default41}{7.2.4}
\indexitem \texttt{cutflow} environment, \defocc{\@locref{hevea_default52}{7.3.6}}
\indexitem \texttt{cutflow*} environment, \defocc{\@locref{hevea_default55}{7.3.6}}
\indexitem \texttt{\char92cuthere}, \@locref{hevea_default35}{7.2.2}, \@locref{hevea_default42}{7.2.4}
\indexitem \texttt{\char92cutname}, \defocc{\@locref{hevea_default46}{7.3.1}}
\indexitem \texttt{cuttingdepth} counter, \@locref{hevea_default34}{7.2.2}
\indexitem \texttt{\char92cuttingunit}, \@locref{hevea_default31}{7.2.2}, \@locref{hevea_default43}{7.2.4}
\indexspace
\indexitem \texttt{deepcut} package, \@locref{hevea_default44}{7.2.5}
\indexitem \texttt{\char92def}, \@locref{hevea_default202}{B.16.1.1}
\indexitem display problems\begin{indexenv}
\indexitem for authors, \@locref{hevea_default220}{B.16.5}
\indexitem for viewers, \@locref{hevea_default283}{C.2}
\end{indexenv}
\indexitem \texttt{displayjax} environment, \defocc{\@locref{hevea_default223}{B.16.6}}, \defocc{\@locref{hevea_default227}{B.16.6.1}}
\indexitem \texttt{divstyle} environment, \defocc{\@locref{hevea_default126}{9.5.2}}
\indexspace
\indexitem \texttt{\char92else}, \@locref{hevea_default209}{B.16.1.4}
\indexitem \texttt{esponja} command, \@locref{hevea_default273}{C.1.3}
\indexitem \texttt{externalcss} (boolean register), \defocc{\@locref{hevea_default128}{9.6.2}}
\indexitem \texttt{\char92externalcsstrue}, \defocc{\@locref{hevea_default129}{9.6.2}}
\indexspace
\indexitem \texttt{fancysection} package, \@locref{hevea_default217}{B.16.4}
\indexitem \texttt{\char92fcolorbox}, \@locref{hevea_default198}{B.14.2}
\indexitem \texttt{\char92fi}, \@locref{hevea_default210}{B.16.1.4}
\indexitem \texttt{figcut} package, \@locref{hevea_default45}{7.2.5}
\indexitem \texttt{\char92flushdef}, \defocc{\@locref{hevea_default57}{7.3.7}}, \@locref{hevea_default59}{7.3.7}
\indexitem \texttt{\char92footahref}, \defocc{\@locref{hevea_default63}{8.1.1}}
\indexitem \texttt{\char92footnoteflush}, \defocc{\@locref{hevea_default56}{7.3.7}}
\indexitem \texttt{\char92footurl}, \@locref{hevea_default71}{8.1.1}
\indexitem \texttt{\char92formatlinks}, \defocc{\@locref{hevea_default51}{7.3.5}}
\indexspace
\indexitem GIF, \@locref{hevea_default135}{10.5}, \@locref{hevea_default276}{C.1.5}
\indexitem \texttt{\char92gdef}, \@locref{hevea_default206}{B.16.1.3}
\indexitem \texttt{\char92getenvclass}, \@locref{hevea_default103}{8.5}, \defocc{\@locref{hevea_default121}{9.3}}
\indexitem \texttt{\char92global}, \@locref{hevea_default205}{B.16.1.3}
\indexitem \texttt{graphics} package, \@locref{hevea_default192}{B.14.1}
\indexitem \texttt{graphicx} package, \@locref{hevea_default193}{B.14.1}
\indexspace
\indexitem \texttt{hacha} command, \@locref{hevea_default272}{C.1.2}
\indexitem \texttt{hanging} package, \@locref{hevea_default267}{B.17.19}
\indexitem \texttt{hevea} boolean register, \@locref{hevea_default20}{5.2.3}
\indexitem \texttt{hevea} command, \@locref{hevea_default269}{C.1.1}
\indexitem \texttt{hevea.sty} \LaTeX{} style file, \@locref{hevea_default9}{5.2}
\indexitem \texttt{\char92heveadate}, \@locref{hevea_default215}{B.16.3}
\indexitem \texttt{\char92heveaimagedir}, \@locref{hevea_default140}{10.6}
\indexitem \texttt{\char92home}, \defocc{\@locref{hevea_default68}{8.1.1}}
\indexitem \texttt{\char92htmlcolor}, \@locref{hevea_default72}{8.1.2}
\indexitem \texttt{\char92htmlfoot}, \@locref{hevea_default149}{B.2}
\indexitem \texttt{\char92htmlhead}, \@locref{hevea_default148}{B.2}
\indexitem \texttt{htmlonly} environment, \defocc{\@locref{hevea_default11}{5.2.1}}
\indexitem \texttt{\char92htmlprefix}, \defocc{\@locref{hevea_default47}{7.3.2}}
\indexitem hyperlinks, \@locref{hevea_default60}{8.1.1}, \@locref{hevea_default251}{B.17.12}
\indexspace
\indexitem \texttt{\char92if}, \@locref{hevea_default208}{B.16.1.4}
\indexitem \texttt{ifpdf} package, \@locref{hevea_default264}{B.17.17}
\indexitem \texttt{ifthen} package, \@locref{hevea_default179}{B.8.5}
\indexitem image inclusion\begin{indexenv}
\indexitem bitmap, \@locref{hevea_default73}{8.2}
\indexitem in Postscript, \defocc{\@locref{hevea_default29}{6.3}}, \@locref{hevea_default132}{10.4}, \@locref{hevea_default191}{B.14.1}
\indexitem output format, \@locref{hevea_default133}{10.5}
\end{indexenv}
\indexitem \texttt{\char92imageflush}, \defocc{\@locref{hevea_default27}{6.1}}, \@locref{hevea_default137}{10.5}
\indexitem \texttt{imagen} command, \@locref{hevea_default274}{C.1.5}
\indexitem \texttt{\char92imgsrc}, \@locref{hevea_default50}{7.3.4}, \defocc{\@locref{hevea_default67}{8.1.1}}, \@locref{hevea_default74}{8.2}, \@locref{hevea_default104}{8.5}, \@locref{hevea_default138}{10.5}
\indexitem \texttt{index} package, \@locref{hevea_default242}{B.17.8}
\indexitem \texttt{indexcols} counter, \@locref{hevea_default190}{B.11.5}
\indexitem \texttt{indexenv} environment, \defocc{\@locref{hevea_default189}{B.11.5}}
\indexitem inference rules, \@locref{hevea_default260}{B.17.16}
\indexitem \texttt{\char92input}, \defocc{\@locref{hevea_default186}{B.11.4}}
\indexitem \texttt{inputenc} package, \@locref{hevea_default238}{B.17.4}
\indexitem \texttt{\char92inputencoding}, \defocc{\@locref{hevea_default240}{B.17.4}}
\indexspace
\indexitem \texttt{\char92label}, \@locref{hevea_default159}{B.4.1}, \defocc{\@locref{hevea_default184}{B.11.2}}
\indexitem \texttt{latexonly} environment, \defocc{\@locref{hevea_default10}{5.2.1}}, \@locref{hevea_default17}{5.2.2}
\indexitem \texttt{\char92let}, \@locref{hevea_default154}{B.2}, \defocc{\@locref{hevea_default204}{B.16.1.2}}
\indexitem \texttt{listings} package, \@locref{hevea_default254}{B.17.14}
\indexitem \texttt{\char92loadcssfile}, \defocc{\@locref{hevea_default130}{9.6.3}}
\indexitem \texttt{longtable} package, \@locref{hevea_default257}{B.17.15}
\indexitem \texttt{\char92lstavoidwhitepre}, \defocc{\@locref{hevea_default256}{B.17.14}}
\indexspace
\indexitem \texttt{\char92mailto}, \defocc{\@locref{hevea_default66}{8.1.1}}
\indexitem \texttt{\char92marginpar}, \defocc{\@locref{hevea_default180}{B.9.3}}
\indexitem math accents, \@locref{hevea_default174}{B.7.6}
\indexitem \texttt{mathjax} environment, \defocc{\@locref{hevea_default231}{B.16.6.1}}
\indexitem \texttt{mathjax} package, \@locref{hevea_default222}{B.16.6}
\begin{indexenv}
\indexitem \texttt{displayjax} environment, \@locref{hevea_default226}{B.16.6.1}
\indexitem \texttt{mathjax} environment, \@locref{hevea_default230}{B.16.6.1}
\indexitem \verb+\textjax+, \@locref{hevea_default228}{B.16.6.1}
\end{indexenv}
\indexitem \texttt{mathjax.sty} \LaTeX{} style file, \@locref{hevea_default225}{B.16.6}
\indexitem \texttt{mathjaxauto.hva} file, \@locref{hevea_default232}{B.16.6.2}
\indexitem \texttt{mathpartir} package, \@locref{hevea_default259}{B.17.16}
\begin{indexenv}
\indexitem derivation trees, \@locref{hevea_default263}{B.17.16.4}
\indexitem \verb+\inferrule+, \@locref{hevea_default262}{B.17.16.2}
\indexitem \texttt{mathpar} environment, \@locref{hevea_default261}{B.17.16.1}
\end{indexenv}
\indexitem \texttt{multibib} package, \@locref{hevea_default245}{B.17.10}
\indexitem \texttt{multind} package, \@locref{hevea_default243}{B.17.8}
\indexspace
\indexitem \texttt{natbib} package, \@locref{hevea_default244}{B.17.9}
\indexitem \texttt{\char92newcites}, \@locref{hevea_default246}{B.17.10}
\indexitem \texttt{\char92newcommand}, \@locref{hevea_default177}{B.8.1}
\indexitem \texttt{\char92newif}, \@locref{hevea_default207}{B.16.1.4}
\indexitem \texttt{\char92newstyle}, \defocc{\@locref{hevea_default118}{9.1}}
\indexitem \texttt{\char92normalmarginpar}, \defocc{\@locref{hevea_default182}{B.9.3}}
\indexitem \texttt{\char92notocnumber}, \@locref{hevea_default33}{7.2.2}
\indexspace
\indexitem \texttt{\char92oneurl}, \@locref{hevea_default70}{8.1.1}
\indexspace
\indexitem PDF, \@locref{hevea_default278}{C.1.5}
\indexitem PNG, \@locref{hevea_default134}{10.5}, \@locref{hevea_default275}{C.1.5}
\indexitem pdflatex, \@locref{hevea_default279}{C.1.5}
\indexitem \texttt{\char92purple}, \@locref{hevea_default99}{8.5}
\indexspace
\indexitem \texttt{raw} environment, \@locref{hevea_default95}{8.4}
\indexitem \texttt{rawhtml} environment, \defocc{\@locref{hevea_default12}{5.2.1}}, \@locref{hevea_default92}{8.4}, \@locref{hevea_default155}{B.2}
\indexitem \texttt{\char92rawhtmlinput}, \@locref{hevea_default93}{8.4}
\indexitem \texttt{\char92rawinput}, \@locref{hevea_default96}{8.4}
\indexitem \texttt{rawtext} environment, \@locref{hevea_default97}{8.4}
\indexitem \texttt{\char92rawtextinput}, \@locref{hevea_default98}{8.4}
\indexitem \texttt{\char92ref}, \defocc{\@locref{hevea_default185}{B.11.2}}
\indexitem \texttt{\char92renewcommand}, \@locref{hevea_default178}{B.8.1}
\indexitem \texttt{\char92reversemarginpar}, \defocc{\@locref{hevea_default181}{B.9.3}}
\indexitem \texttt{\char92rule}, \@locref{hevea_default7}{4.2}
\indexspace
\indexitem SVG, \@locref{hevea_default136}{10.5}, \@locref{hevea_default277}{C.1.5}
\indexitem \texttt{\char92setenvclass}, \@locref{hevea_default102}{8.5}, \defocc{\@locref{hevea_default120}{9.3}}
\indexitem \texttt{\char92setlinkstext}, \defocc{\@locref{hevea_default49}{7.3.4}}
\indexitem spacing, \see{`` ''}{\@locref{hevea_default158}{B.3.1}}
\indexitem sqrt, \@locref{hevea_default167}{B.7.3}
\indexitem style-sheets, \@locref{hevea_default117}{9}
\begin{indexenv}
\indexitem \verb+\divstyle+, \@locref{hevea_default125}{9.5.2}
\indexitem \verb+\loadcssfile+, \@locref{hevea_default131}{9.6.3}
\indexitem \verb+\newstyle+, \@locref{hevea_default119}{9.1}
\indexitem and \hacha, \@locref{hevea_default30}{7.1}
\end{indexenv}
\indexitem styles for\begin{indexenv}
\indexitem lists, \@locref{hevea_default127}{9.5.3}
\indexitem miscellaneous objects, \@locref{hevea_default124}{9.5.2}
\indexitem title, \@locref{hevea_default123}{9.5.1}
\end{indexenv}
\indexitem \texttt{supertabular} package, \@locref{hevea_default258}{B.17.15}
\indexspace
\indexitem \texttt{\char92tableofcontents}, \defocc{\@locref{hevea_default160}{B.4.3}}
\indexitem \texttt{tabularx} package, \@locref{hevea_default236}{B.17.2}
\indexitem tabulation, \@locref{hevea_default3}{3.1.2}
\indexitem text-level elements, \@locref{hevea_default89}{8.3}
\begin{indexenv}
\indexitem span, \@locref{hevea_default90}{8.3}
\end{indexenv}
\indexitem \texttt{\char92textcolor}, \@locref{hevea_default196}{B.14.2}
\indexitem \texttt{\char92textjax}, \defocc{\@locref{hevea_default224}{B.16.6}}, \defocc{\@locref{hevea_default229}{B.16.6.1}}
\indexitem \texttt{\char92textoverline}, \@locref{hevea_default171}{B.7.5}
\indexitem \texttt{\char92textstackrel}, \@locref{hevea_default169}{B.7.5}
\indexitem \texttt{\char92textunderline}, \@locref{hevea_default170}{B.7.5}
\indexitem Thai, \@locref{hevea_default266}{B.17.18}
\indexitem \texttt{\char92title}, \@locref{hevea_default164}{B.5.3}
\indexitem \texttt{\char92tocnumber}, \@locref{hevea_default32}{7.2.2}
\indexitem \texttt{\char92today}, \@locref{hevea_default165}{B.5.3}, \@locref{hevea_default213}{B.16.3}
\indexitem \texttt{toimage} environment, \defocc{\@locref{hevea_default13}{5.2.1}}, \@locref{hevea_default19}{5.2.2}, \@locref{hevea_default26}{6.1}
\indexitem \texttt{\char92toplinks}, \defocc{\@locref{hevea_default48}{7.3.3}}
\indexspace
\indexitem \texttt{undersection} package, \@locref{hevea_default219}{B.16.4}
\indexitem unicode, \@locref{hevea_default168}{B.7.4}
\indexitem \texttt{\char92url}, \@locref{hevea_default69}{8.1.1}, \defocc{\@locref{hevea_default250}{B.17.12}}
\indexitem \texttt{url} package, \@locref{hevea_default252}{B.17.12}
\indexitem \texttt{\char92urldef}, \@locref{hevea_default253}{B.17.12}
\indexitem \texttt{\char92usepackage}, \@locref{hevea_default0}{2.3.2}, \@locref{hevea_default163}{B.5.2}
\indexspace
\indexitem \texttt{verbimage} environment, \defocc{\@locref{hevea_default14}{5.2.1}}, \@locref{hevea_default18}{5.2.2}
\indexitem \texttt{verblatex} environment, \defocc{\@locref{hevea_default15}{5.2.1}}, \@locref{hevea_default16}{5.2.2}
\indexspace
\indexitem \texttt{winfonts} package, \@locref{hevea_default221}{B.16.5}
\indexspace
\indexitem \texttt{xxcharset.exe} script, \@locref{hevea_default116}{8.6}
\indexitem \texttt{xxdate.exe} script, \@locref{hevea_default214}{B.16.3}
\end{indexenv}
hevea-2.36-manual/manual.css 0000644 0043171 0051216 00000014010 14252364056 016027 0 ustar maranget cristal .c000{background-color:green;height:3px}
.c001{border-spacing:0;}
.c002{border-spacing:6px;border-collapse:separate;}
.c003{border:0;border-spacing:1;border-collapse:separate;}
.c004{border:0;border-spacing:1px;border-collapse:separate}
.c005{border:1px solid black;}
.c006{color:#006600}
.c007{color:#B7140B}
.c008{color:black}
.c009{color:fuchsia}
.c010{color:maroon}
.c011{color:purple}
.c012{color:red}
.c013{color:white}
.c014{color:yellow}
.c015{display:inline-block;transform:translateY(calc(0pt - ( 2px )))}
.c016{font-family:Helvetica}
.c017{font-family:monospace}
.c018{font-family:monospace;font-weight:bold}
.c019{font-family:sans-serif}
.c020{font-size:small}
.c021{font-size:x-large}
.c022{font-size:xx-large}
.c023{font-style:italic}
.c024{font-style:oblique}
.c025{font-variant:small-caps}
.c026{font-variant:small-caps;font-size:small}
.c027{font-weight:bold}
.c028{font-weight:bold;color:blue}
.c029{font-weight:bold;color:red}
.c030{height:4em; margin:0ex 2px;}
.c031{height:4em; margin:0ex 4px;}
.c032{text-align:center}
.c033{text-align:center;border:solid 1px;white-space:nowrap}
.c034{text-align:center;white-space:nowrap}
.c035{text-align:left}
.c036{text-align:left;border:solid 1px;white-space:nowrap}
.c037{text-align:left;white-space:nowrap}
.c038{text-align:right;white-space:nowrap}
.c039{vertical-align:bottom}
.c040{vertical-align:middle}
.c041{vertical-align:middle;text-align:left;}
.c042{vertical-align:top}
.c043{vertical-align:top;text-align:center;border:solid 1px;white-space:nowrap}
.c044{vertical-align:top;text-align:left;}
.c045{vertical-align:top;text-align:left;border:solid 1px;}
.c046{vertical-align:top;text-align:left;white-space:nowrap}
.c047{whitespace:nowrap;text-align:center}
.c048{whitespace:nowrap;text-align:left}
.c049{width:10%;text-align:center}
.c050{width:100%;}
.c051{width:40%;text-align:center}
.c052{width:5%;text-align:center}
.c053{width:6px;}
.c054{width:90%;text-align:center}
.floatrule{background-color: black; border: none; height: 1px; width: 80%}
.li-itemize{margin:1ex 0ex;}
.li-enumerate{margin:1ex 0ex;}
.dd-description{margin:0ex 0ex 1ex 4ex;}
.dt-description{margin:0ex;}
.footnotetext{margin:0ex; padding:0ex;}
div.footnotetext P{margin:0px; text-indent:1em;}
.thefootnotes{text-align:left;margin:0ex;}
.dt-thefootnotes{margin:0em;}
.dd-thefootnotes{margin:0em 0em 0em 2em;}
.caption{padding-left:2ex; padding-right:2ex; margin-left:auto; margin-right:auto}
.title{margin:2ex auto;text-align:center}
.titlemain{margin:1ex 2ex 2ex 1ex;}
.titlerest{margin:0ex 2ex;}
.center{text-align:center;margin-left:auto;margin-right:auto;}
.flushleft{text-align:left;margin-left:0ex;margin-right:auto;}
.flushright{text-align:right;margin-left:auto;margin-right:0ex;}
div table{margin-left:inherit;margin-right:inherit;margin-bottom:2px;margin-top:2px}
td table{margin:auto;}
table{border-collapse:collapse;}
td{padding:0;}
.cellpadding0 tr td{padding:0;}
.cellpadding1 tr td{padding:1px;}
pre{text-align:left;margin-left:0ex;margin-right:auto;}
blockquote{margin-left:4ex;margin-right:4ex;text-align:left;}
td p{margin:0px;}
.quote{margin-left:3em;margin-right:3em;text-align:inherit;text-indent:0pt}
.rule-rect{fill: black;}
.lrbox{box-sizing:border-box;display:inline-block;overflow:visible;white-space:nowrap;}
.framebox{border:1px solid black;padding:0.25em;}
.vertical-rule{border:none;width:2px;background-color:black;}
.horizontal-rule{border:none;background-color:black;}
.hrule{border:none;height:2px;width:100%;background-color:black;}
.display{border-collapse:separate;border-spacing:2px;line-height:1.1;width:auto; border:none;}
.dcell{white-space:nowrap;padding:0px; border:none;}
.dcenter{margin:0ex auto;}
.marginparleft{float:left; clear:left; margin-left:0ex; margin-right:1ex;}
.marginparright{float:right; clear:right; margin-left:1ex; margin-right:0ex;}
.part{margin:2ex auto;text-align:center}
.clisting{font-family:monospace;white-space:pre;
border-left:solid black;padding-left:2ex;margin-left:2ex;}
.delimleft{border-collapse:separate;border-spacing:0px;margin:0px 4px 0px 0px;}
.delimright{border-collapse:separate;border-spacing:0px;margin:0px 0px 0px 4px;}
.bracell{padding:0ex;}
.lstlisting{font-family:monospace;white-space:pre;margin-right:auto;margin-left:0pt;text-align:left}
.mprow{border-collapse:separate;border-spacing:2ex;width:100%;margin:0ex;}
.mprcell{padding:0px;width:auto;}
.subsectionex{padding:1ex;color:navy;border:solid navy;}
.verbatim{margin:1ex 1ex;padding:1ex;background:#CCFFCC;}
.myverbatim{margin:1ex 3ex;padding:1ex;
color:maroon;
background:#FFAD7A}
.toc1{list-style:none;border-left:1ex solid #4C0D00;padding:0ex 1ex;}
.toc2{list-style:none;border-left:1ex solid #661300;padding:0ex 1ex;}
.toc3{list-style:none;border-left:1ex solid #DB9370;padding:0ex 1ex;}
.toc4{list-style:none;border-left:1ex solid #FF897F;padding:0ex 1ex;}
.xtitle{text-align:center;margin:1ex auto;color:navy;border:solid navy;}
.xtitlerest{font-variant:small-caps;}
.ruled{border:solid black;padding:1ex;background:#eeddbb;color:maroon}
.ruledbis{border:solid black;padding:1ex;background:#eeddbb;color:maroon;display:inline-block}
.show{border:solid black; border-width:thin; margin:2ex;}
body{background-color:white}
a:link{color:#00B200;text-decoration:underline;}
a:visited{color:#006600;text-decoration:underline;}
a:hover{color:black;text-decoration:none;background-color:#99FF99}
.title{background-color:#00B200}
.titlemain{background-color:#00B200}
.titlerest{ackground-color:#00B200}
.part{padding:1ex;background-color:#00CC00}
.section{padding:.5ex;background-color:#2DE52D}
.subsection{padding:0.3ex;background-color:#66FF66}
.subsubsection{padding:0.5ex;background-color:#99FF99}
.paragraph{padding:0.5ex;background-color:#CCFFCC}
.fmarginpar{border:solid thin #66FF66; width:20%; text-align:left}
.ffootnoterule{border:none;margin:1em auto 1em 0px;width:50%;background-color:#00CC00}
.ftoc1{list-style:none;margin:0ex 1ex;padding:0ex 1ex;border-left:1ex solid #00CC00}
.ftoc2{list-style:none;margin:1ex 1ex;padding:0ex 1ex;border-left:1ex solid #2DE52D}
.ftoc3{list-style:none;margin:0ex 1ex;padding:0ex 1ex;border-left:1ex solid #66FF66}
hevea-2.36-manual/thaihevea001.png 0000644 0043171 0051216 00001163543 14252364060 016741 0 ustar maranget cristal PNG
IHDR v @I# &iCCPicc HgPY<@BPC*%Z(ҫ@PEl+4EE\"kE t,ʺqQAYp ?{ossp e{bRɎ(tջ {i常r)t eJOYLgWX\2XyKο,]~
)sT8بlOrTzV $G&D~S GfDnr&AltL:5204_gK!FgE_z s z t@WOm| :3z
@(U t08 |A $`( E` 8@-h M<.L@ށA2@F 7
Bh( ʀrPT
UAuP t݄84
}aXև0v}p4
^O 6< "@]p$BV)GVC!Bd h(&JerFTVT1
uՁECDh2Z @Ёht ]nDѓw aa0Θ L f3sӆL`X VkaӱJI%v G)p`\.Wk]
p xq:o;IA"X| q
B+aH$͉^XvbqD%iRi/82!
L ے&US{1O,BlXXؐ+
NP6Pr(3;Yq8WM&L }}}%K'Đ)T*:tP6£EW.###ڴij722D' JMM%KP߾}ҥK4sL$/۷oF!@ǎ cߞ={h
t-o忒N#}}} P3K3n8""rћ7o(55
{Q4}9h @,,,(44cАZ--\C/_&{{{h4M
63N:E
4j֬IsΥׯSiҥ$I||ܜRSSIOO?aj @Z-*P3qDSRRTRAiiiO$ŋY`kP&MԩS$IF+WPΝitA3g]rzI i4PEP4'O&NGTN q O `tӦM͛7b
TP% Pnj(|w9s&̠ 333L8ӦMCxx8&Lua}6LMM5(5%%ӧO7MSNaIGXr;wr"ؤI SSScÆ
غu+M,Ygnck}) l<` ܻw$\r+j G Z,X]vQZPҥ 8p sxz Ǝwuʔ)[h5z\|91sLzLHHPAzܹsJ, ;v 556l@LLLf]d= (_< 2fʔ) 겜V!Z*r9v>F."cccy'_F