Sophie: hevea-1.10-4mdv2010.0 i586

hevea-1.10-4mdv2010.0.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
            "http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD>

<META http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<META name="GENERATOR" content="hevea 1.10">
<META name="Author" content="Luc Maranget">
<LINK rel="stylesheet" type="text/css" href="manual.css">
<TITLE>Extra Features</TITLE>
</HEAD>
<BODY >
<A HREF="manual037.html"><IMG SRC="previous_motif.gif" ALT="Previous"></A>
<A HREF="manual022.html"><IMG SRC="contents_motif.gif" ALT="Up"></A>
<A HREF="manual-packages.html"><IMG SRC="next_motif.gif" ALT="Next"></A>
<HR>
<H2 CLASS="section"><A NAME="htoc122">B.16</A>&#XA0;&#XA0;Extra Features</H2><UL>
<LI><A HREF="manual038.html#toc95">T<sub>E</sub>X macros</A>
</LI><LI><A HREF="manual038.html#toc96">Command Definition inside Command Definition</A>
</LI><LI><A HREF="manual038.html#toc97">Date and time</A>
</LI><LI><A HREF="manual038.html#toc98">Fancy sectioning commands</A>
</LI><LI><A HREF="manual038.html#toc99">Targetting Windows</A>
</LI><LI><A HREF="manual038.html#toc100">H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A as a Back-End for VideoC</A>
</LI></UL>
<P>
This section describes H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A functionalities that extends on plain L<sup>A</sup>T<sub>E</sub>X,
as defined in [<A HREF="manual047.html#latex">L<sup>A</sup>T<sub>E</sub>X</A>].
Most of the features described here are performed by default.</P><H3 CLASS="subsection"><A NAME="toc95"></A><A NAME="htoc123">B.16.1</A>&#XA0;&#XA0;T<sub>E</sub>X macros</H3><P><A NAME="texmacro"></A>
Normally, H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A does not recognize constructs that are specific to
T<sub>E</sub>X.
However, some of the internal commands of H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A are homonymous to
T<sub>E</sub>X macros, in order to enhance compatibility.
Note that full compatibility with T<sub>E</sub>X is not guaranteed.</P><H4 CLASS="subsubsection">B.16.1.1&#XA0;&#XA0;&#XC0; la T<sub>E</sub>X macros definitions</H4><P><A NAME="texmacros"></A>
<A NAME="@default187"></A><A NAME="@default188"></A>
The <CODE>\def</CODE> construct for defining commands is supported.
It is important to
notice that H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A semantics for <CODE>\def</CODE> 
follows T<sub>E</sub>X semantics.
That is, defining a command that already
exists with <CODE>\def</CODE> succeeds.
This is an important change with respect to previous versions of
H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A, where <CODE>\def</CODE> had the same semantics as
<CODE>\newcommand</CODE>.</P><P>Delimiting characters in command definition are supported.
Consider the following example from the T<sub>E</sub>X Book:
</P><PRE CLASS="verbatim">\def\Look{\textsc{Look}}
\def\x{\textsc{x}}
\def\cs AB#1#2C$#3\$ {#3{ab#1}#1 c\x #2}
\cs AB {\Look}{}C${And \$}{look}\$ 5.
</PRE><P>It yields:



And $lookab<SPAN STYLE="font-variant:small-caps">LookLook</SPAN> c<SPAN STYLE="font-variant:small-caps">x</SPAN>5.</P><P>Please note that delimiting characters are supported as far as I
could, problems are likely with delimiting characters which include
spaces or command names, in particular the command name <CODE>\{</CODE>.
One can include <CODE>\{</CODE> in a command argument by using the grouping
characters <CODE>{</CODE>&#X2026; <CODE>}</CODE>:
</P><PRE CLASS="verbatim">\def\frenchquote(#1){\guillemotleft~\emph{#1}~\guillemotright{} (in French)}
he said \frenchquote(Alors cette accolade ouvrante {``\{''}~?).
</PRE><P>Yields:
he said &#XAB;&#XA0;<EM>Alors cette accolade ouvrante &#X201C;{&#X201D;&#XA0;?</EM>&#XA0;&#XBB; (in French).
</P><P>Another source of incompatibilty with T<sub>E</sub>X is that substitution of
macros parameters is not performed at the same moment by H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A and
T<sub>E</sub>X.
However, things should go smoothly at the first level of macro
expansion, that is when the delimiters
appear in source code at the same level as the macro that is to
parse them.
For instance, the following source will give different results in
L<sup>A</sup>T<sub>E</sub>X and in H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A:
</P><PRE CLASS="verbatim">\def\cs#1A{``#1''}
\def\othercs#1{\cs#1A}
\othercs{coucouA}
</PRE><P>L<sup>A</sup>T<sub>E</sub>X output is &#X201C;coucou&#X201D;A, while H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A output is &#X201C;coucouA&#X201D;.
Here is H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A output:


&#X201C;coucouA&#X201D;
Please note that in most situations this discrepancy will make
H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A crash. </P><H4 CLASS="subsubsection">B.16.1.2&#XA0;&#XA0;The <TT>\let</TT> construct</H4><P>
<A NAME="@default189"></A>H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A also processes a
limited version of <CODE>\let</CODE>:
</P><DIV CLASS="flushleft">
<CODE>\let</CODE> <I>macro-name1</I> = <I>macro-name2</I>
</DIV><P>
The effect is to bind <I>macro-name1</I> to whatever <I>macro-name2</I>
is bound to at the time <CODE>\let</CODE> is processed. This construct may
prove very useful in situations where
one whishes to slightly modify basic commands.
See sections&#XA0;<A HREF="manual020.html#customize-let">10.3</A> and&#XA0;<A HREF="manual024.html#exlet">B.2</A> for examples of using
<CODE>\let</CODE> in such a situation.</P><H4 CLASS="subsubsection">B.16.1.3&#XA0;&#XA0;The <TT>\global</TT> construct</H4><P>
<A NAME="@default190"></A>
It is possible to escape scope and to make global definitions
and bindings by using the T<sub>E</sub>X construct <CODE>\global</CODE>.
The <CODE>\global</CODE> construct is significant before
<CODE>\def</CODE> and <CODE>\let</CODE> constructs.</P><P><A NAME="@default191"></A>
Also note that <CODE>\gdef</CODE> is equivalent to <CODE>\global\def</CODE>.</P><H4 CLASS="subsubsection">B.16.1.4&#XA0;&#XA0;T<sub>E</sub>X Conditional Macros</H4><P><A NAME="texcond"></A>
<A NAME="@default192"></A><A NAME="@default193"></A><A NAME="@default194"></A><A NAME="@default195"></A>
The <CODE>\newif\if</CODE><I>name</I>, where <I>name</I> is made of letters
only, creates three macros:
<CODE>\if</CODE><I>name</I>, <CODE>\</CODE><I>name</I><CODE>true</CODE> and
<CODE>\</CODE><I>name</I><CODE>false</CODE>.
The latter two set the <I>name</I> condition to <I>true</I> and
<I>false</I>, respectively.
The <CODE>\if</CODE><I>name</I> command tests the condition <I>name</I>:
</P><DIV CLASS="flushleft">
<CODE>\if</CODE><I>name<BR>
text<SUB>1</SUB></I><BR>
<CODE>\else</CODE><BR>
<I>text<SUB>2</SUB></I><BR>
<CODE>\fi</CODE><BR>
</DIV><P>
Text <I>text<SUB>1</SUB></I> is processed when <I>name</I> is
<I>true</I>, otherwise <I>text<SUB>2</SUB></I> is processed.
If <I>text<SUB>2</SUB></I> is empty, then the <CODE>\else</CODE> keyword can be
omitted.</P><P>Note that H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A also implements L<sup>A</sup>T<sub>E</sub>X <TT>ifthen</TT> package
and that T<sub>E</sub>X simple conditional macros are fully compatible with
L<sup>A</sup>T<sub>E</sub>X boolean registers. More precisely,
we have the following correspondences:
</P><DIV CLASS="center">
<TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP COLSPAN=2>T<sub>E</sub>X</TD><TD ALIGN=center NOWRAP>L<sup>A</sup>T<sub>E</sub>X</TD></TR>
<TR><TD CLASS="hbar" COLSPAN=3></TD></TR>
<TR><TD VALIGN=top ALIGN=left><CODE>\newif\if</CODE><I>name</I></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left><CODE>\newboolean{</CODE><I>name</I><CODE>}</CODE></TD></TR>
<TR><TD VALIGN=top ALIGN=left><CODE>\</CODE><I>name</I><CODE>true</CODE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left><CODE>\setboolean{</CODE><I>name</I><CODE>}{true}</CODE></TD></TR>
<TR><TD VALIGN=top ALIGN=left><CODE>\</CODE><I>name</I><CODE>false</CODE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left><CODE>\setboolean{</CODE><I>name</I><CODE>}{false}</CODE></TD></TR>
<TR><TD VALIGN=top ALIGN=left><CODE>\if</CODE><I>name text<SUB>1</SUB></I><CODE>\else</CODE>
<I>text<SUB>2</SUB></I><CODE>\fi</CODE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left><CODE>\ifthenelse{\boolean{</CODE><I>name</I><CODE>}}{</CODE><I>text<SUB>1</SUB></I><CODE>}{</CODE><I>text<SUB>2</SUB></I><CODE>}</CODE></TD></TR>
</TABLE>
</DIV><H4 CLASS="subsubsection">B.16.1.5&#XA0;&#XA0;Other T<sub>E</sub>X Macros</H4><P>
H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A implements the macros <CODE>\unskip</CODE> and <CODE>\endinput</CODE>.
It also supports the <CODE>\csname</CODE>&#X2026; <CODE>\endcsname</CODE>
construct.</P><H3 CLASS="subsection"><A NAME="toc96"></A><A NAME="htoc124">B.16.2</A>&#XA0;&#XA0;Command Definition inside Command Definition</H3><P>
<A NAME="@default196"></A><A NAME="@default197"></A>
If one strictly follows the L<sup>A</sup>T<sub>E</sub>X manual, only commands with no
arguments can be defined inside other commands.
Parameters (<EM>i.e.</EM> <CODE>#</CODE><I>n</I>) occurring inside command bodies
refer to the outer definition, even when they appear in nested
command definitions.
That is, the following source:
</P><PRE CLASS="verbatim">\newcommand{\outercom}[1]{\newcommand{\insidecom}{#1}\insidecom}
\outercom{outer}
</PRE><P>yields this output:
</P><DIV CLASS="center">

outer
</DIV><P>Nevertheless, nested commands with arguments are allowed.
Standard parameters <CODE>#</CODE><I>n</I> still refer to the outer
definition, while nested parameters <CODE>##</CODE><I>n</I> refer to the
inner definition.
That is, the source:
</P><PRE CLASS="verbatim">\newcommand{\outercom}[1]{\newcommand{\insidecom}[1]{##1}\insidecom{inner}}
\outercom{outer}
</PRE><P>yields this output:
</P><DIV CLASS="center">

inner
</DIV><H3 CLASS="subsection"><A NAME="toc97"></A><A NAME="htoc125">B.16.3</A>&#XA0;&#XA0;Date and time</H3><P>
<A NAME="@default198"></A><A NAME="@default199"></A>
Date and time support is not enabled by default, for portability and
simplicity reasons.</P><P>However, H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A source distribution includes a simple (<TT>sh</TT>)
shell script
<TT>xxdate.exe</TT> that activates date and time support.
The <TT>hevea</TT> command, should be invoked as:
</P><PRE CLASS="verbatim"># hevea -exec xxdate.exe ...
</PRE><P>This will execute the script <TT>xxdate.exe</TT>, whose output is then
read by H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A.
As a consequence, standard L<sup>A</sup>T<sub>E</sub>X counters <CODE>year</CODE>,
<CODE>month</CODE>, <CODE>day</CODE> and
<CODE>time</CODE> are defined and
L<sup>A</sup>T<sub>E</sub>X command <CODE>\today</CODE> works properly.
<A NAME="@default200"></A>
Additionnally the following counters and commands are defined:
</P><DIV CLASS="center">
<TABLE CELLSPACING=6 CELLPADDING=0><TR><TD VALIGN=top ALIGN=left NOWRAP>&nbsp;</TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD></TR>
<TR><TD CLASS="hbar" COLSPAN=3></TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>Counter <TT>weekday</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left>day of week, 0&#X2026;6
(e.g. 2)</TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>Counter <TT>Hour</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left>hour, 00&#X2026;11
(e.g. 02)</TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>Counter <TT>hour</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left>hour, 00&#X2026;23 (e.g. 14)</TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>Counter <TT>minute</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left>minute, 00&#X2026;59
(e.g. 29)</TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>Counter <TT>second</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left>second, 00&#X2026;61<SUP><A NAME="text9" HREF="#note9">8</A></SUP>(e.g. 25)</TD></TR>
<TR><TD CLASS="hbar" COLSPAN=3></TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>Command <CODE>\ampm</CODE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left>AM or PM
(e.g. PM)</TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>Command <CODE>\timezone</CODE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left>Time zone
(e.g. CEST)</TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>Command <CODE>\heveadate</CODE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;</TD><TD VALIGN=top ALIGN=left>Output of the <TT>date</TT> Unix
command, (e.g. mardi 21 ao&#XFB;t 2007, 14:29:25 (UTC+0200))</TD></TR>
<TR><TD CLASS="hbar" COLSPAN=3></TD></TR>
</TABLE>
</DIV><P>Note that I chose to add an extra option (and not an extra
<CODE>\@exec</CODE> primitive) for security reasons. You certainly do
not want to enable H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A to execute silently an arbitrary program
without being conscious of that fact.
Moreover, the <TT>hevea</TT> program does not execute
<TT>xxdate.exe</TT> by default since it is difficult to write such 
a script in a portable manner.</P><P>Windows users should enjoy the same features with the version of
<TT>xxdate.exe</TT> included in the Win32 distribution. </P><H3 CLASS="subsection"><A NAME="toc98"></A><A NAME="htoc126">B.16.4</A>&#XA0;&#XA0;Fancy <A NAME="fancysection"></A>sectioning commands</H3><P>
<A NAME="@default201"></A>
Loading the <TT>fancysection.hva</TT> file will radically change the
style of sectional units headers: they appear over a green
backgroud, the backgrould color saturation decreases as the sectioning
commands themselves do (this is the style of this manual).
Additionnaly, the document background color is white.</P><P><B>Note : </B>Fancy section has been re-implemented using style-sheets. While it respects the old behavior, users are encouraged to try out style-sheets for more flexibility. See Section&#XA0;<A HREF="manual019.html#style:sheets">9</A> for details.</P><P>The <TT>fancysection.hva</TT> file is intended to be loaded after
the document base style. Thus, to use fancy section style in
<TT>doc.tex</TT> whose base style is <I>article</I>
you should issue the command:
</P><PRE CLASS="verbatim">  # hevea article.hva fancysection.hva doc.tex
</PRE><P>You can also make a <TT>doc.hva</TT> file that contains the two lines:
</P><PRE CLASS="verbatim">  \input{article.hva}
  \input{fancysection.hva}
</PRE><P>And then launch <TT>hevea</TT> as:
</P><PRE CLASS="verbatim">  # hevea doc.hva doc.tex
</PRE><P>Sectioning command background colors can be changed by
redefining the corresponding colors (<TT>part</TT>, <TT>chapter</TT>,
<TT>section</TT>,&#X2026;).
For instance, you get various mixes of red and orange by:
</P><PRE CLASS="verbatim">\input{article.hva}
\input{fancysection.hva}
\definecolor{part}{named}{BrickRed}
\definecolor{section}{named}{RedOrange}
\definecolor{subsection}{named}{BurntOrange}
</PRE><P>(See section&#XA0;<A HREF="manual036.html#color:package">B.14.2</A> for details on the <TT>named</TT>
color model that is used above.)</P><P><A NAME="@default202"></A>
Another choice is issuing the command
<CODE>\colorsections{</CODE><I>hue</I><CODE>}</CODE>, where
<I>hue</I> is a hue value to be interpreted in the HSV model.
For instance,
</P><PRE CLASS="verbatim">\input{article.hva}
\input{fancysection.hva}
\colorsections{20}
</PRE><P>will yield sectionnal headers on a red-orange background.</P><H3 CLASS="subsection"><A NAME="toc99"></A><A NAME="htoc127">B.16.5</A>&#XA0;&#XA0;Targetting <A NAME="winfonts"></A>Windows</H3><P>
<A NAME="@default203"></A>At the time of this release, Windows support for symbols
through Unicode is not as complete as the one of Linux, which I am
using for testing&#XA0;H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A.</P><P>One of the most salient shortcomings is the inability to display sub-elements
for big brackets, braces and parenthesis, which H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A normally
outputs when it processes <CODE>\left[</CODE>, <CODE>\right\}</CODE> etc.</P><P>We (hopefully) expect Windows fonts to display more of
Unicode easily in a foreseable future. As a temporary fix, we provide
a style file <TT>winfonts.hva</TT>.
Authors concerned by producing pages that do not look too ugly
when viewed through Windows browsers are thus advised to
load the file <TT>winfonts.hva</TT>.
For instance they can invoke H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A as:
</P><PRE CLASS="verbatim"># hevea winfonts.hva ...
</PRE><P>At the moment, loading <TT>winfonts.hva</TT>
only changes the rendering
of L<sup>A</sup>T<sub>E</sub>X big delimiters, avoiding the troublesome Unicode entities.
As an example, here are some exemples of rendering.
</P><TABLE CLASS="display dcenter"><TR VALIGN="middle"><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD CLASS="hbar" COLSPAN=5></TD></TR>
<TR><TD ALIGN=center NOWRAP COLSPAN=2>delimiters</TD><TD ALIGN=center NOWRAP COLSPAN=2>default</TD><TD ALIGN=center NOWRAP>winfonts</TD></TR>
<TR><TD CLASS="hbar" COLSPAN=5></TD></TR>
<TR><TD ALIGN=left NOWRAP><TT>\left\{&#XA0;&#XA0;&#X2026;&#XA0;&#XA0;\right\}</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell">&#X23A7;<BR>
&#X23AA;<BR>
&#X23A8;<BR>
&#X23AA;<BR>
&#X23A9;</TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell">&#X23AB;<BR>
&#X23AA;<BR>
&#X23AC;<BR>
&#X23AA;<BR>
&#X23AD;</TD></TR>
</TABLE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell">&#XA0;/&#XA0;<BR>
&#XA0;|&#XA0;<BR>
&lt;&#XA0;<BR>
&#XA0;|&#XA0;<BR>
&#XA0;\&#XA0;</TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell">&#XA0;\<BR>
&#XA0;|<BR>
&#XA0;&gt;<BR>
&#XA0;|<BR>
&#XA0;/</TD></TR>
</TABLE></TD></TR>
<TR><TD ALIGN=left NOWRAP><TT>\left[&#XA0;&#XA0;&#X2026;&#XA0;&#XA0;\right]</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell">&#X23A1;<BR>
&#X23A2;<BR>
&#X23A2;<BR>
&#X23A3;</TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell">&#X23A4;<BR>
&#X23A5;<BR>
&#X23A5;<BR>
&#X23A6;</TD></TR>
</TABLE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell"><TABLE CLASS="delimleft"><TR><TD CLASS="bracell hbar" STYLE="width:6px;"></TD></TR>
<TR><TD CLASS="bracell" ALIGN="left"><DIV CLASS="vbar" STYLE="height:4em;"></DIV></TD></TR>
<TR><TD CLASS="bracell hbar" STYLE="width:6px;"></TD></TR>
</TABLE></TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell"><TABLE CLASS="delimright"><TR><TD CLASS="bracell hbar" STYLE="width:6px;"></TD></TR>
<TR><TD CLASS="bracell" ALIGN="right"><DIV CLASS="vbar" STYLE="height:4em;"></DIV></TD></TR>
<TR><TD CLASS="bracell hbar" STYLE="width:6px;"></TD></TR>
</TABLE></TD></TR>
</TABLE></TD></TR>
<TR><TD ALIGN=left NOWRAP><TT>\left(&#XA0;&#XA0;&#X2026;&#XA0;&#XA0;\right)</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell">&#X239B;<BR>
&#X239C;<BR>
&#X239C;<BR>
&#X239D;</TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell">&#X239E;<BR>
&#X239F;<BR>
&#X239F;<BR>
&#X23A0;</TD></TR>
</TABLE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell">/&#XA0;<BR>
|&#XA0;<BR>
|&#XA0;<BR>
\&#XA0;</TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell">&#XA0;\<BR>
&#XA0;|<BR>
&#XA0;|<BR>
&#XA0;/</TD></TR>
</TABLE></TD></TR>
<TR><TD ALIGN=left NOWRAP><TT>\left\vert&#XA0;&#XA0;&#X2026;&#XA0;&#XA0;\right\vert</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell">&#X23AA;<BR>
&#X23AA;<BR>
&#X23AA;<BR>
&#X23AA;</TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell">&#X23AA;<BR>
&#X23AA;<BR>
&#X23AA;<BR>
&#X23AA;</TD></TR>
</TABLE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell"><DIV CLASS="vbar" STYLE="height:4em; margin:0ex 4px;"></DIV></TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell"><DIV CLASS="vbar" STYLE="height:4em; margin:0ex 4px;"></DIV></TD></TR>
</TABLE></TD></TR>
<TR><TD ALIGN=left NOWRAP><TT>\left\Vert&#XA0;&#XA0;&#X2026;&#XA0;&#XA0;\right\Vert</TT></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell">&#X23AA;&#X23AA;<BR>
&#X23AA;&#X23AA;<BR>
&#X23AA;&#X23AA;<BR>
&#X23AA;&#X23AA;</TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell">&#X23AA;&#X23AA;<BR>
&#X23AA;&#X23AA;<BR>
&#X23AA;&#X23AA;<BR>
&#X23AA;&#X23AA;</TD></TR>
</TABLE></TD><TD VALIGN=top ALIGN=center NOWRAP>&#XA0;&#XA0;&#XA0;&#XA0;</TD><TD ALIGN=center NOWRAP><TABLE CLASS="display"><TR VALIGN="middle"><TD CLASS="dcell"><DIV CLASS="vbar" STYLE="height:4em; margin:0ex 2px;"></DIV></TD><TD CLASS="dcell"><DIV CLASS="vbar" STYLE="height:4em; margin:0ex 2px;"></DIV></TD><TD CLASS="dcell"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=center NOWRAP>1</TD></TR>
<TR><TD ALIGN=center NOWRAP>2</TD></TR>
<TR><TD ALIGN=center NOWRAP>3</TD></TR>
</TABLE></TD><TD CLASS="dcell"><DIV CLASS="vbar" STYLE="height:4em; margin:0ex 2px;"></DIV></TD><TD CLASS="dcell"><DIV CLASS="vbar" STYLE="height:4em; margin:0ex 2px;"></DIV></TD></TR>
</TABLE></TD></TR>
<TR><TD CLASS="hbar" COLSPAN=5></TD></TR>
</TABLE></TD></TR>
</TABLE><P>More generally, it remains authors responsability to be careful not to
issue too refined Unicode entities. To that aim, authors that target
a wide audience should first limit themselves to the most common
symbols (<EM>e.g.</EM> use <CODE>\leq</CODE> [&#X2264;]
in place of <CODE>\preceq</CODE> [&#X227C;]) and, above all,
they should control the rendering of their documents using several browsers.</P><H3 CLASS="subsection"><A NAME="toc100"></A><A NAME="htoc128">B.16.6</A>&#XA0;&#XA0;H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A as a Back-End for VideoC</H3><P>
H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A is one of the back-ends of the VideoC system for producing
educational CDROM to teach programming languages.
VideoC author is Christian Queinnec and the documentation is available
at:
</P><DIV CLASS="center">
<TT><A HREF="http://www-spi.lip6.fr/~queinnec/VideoC/VideoC.html">http://www-spi.lip6.fr/~queinnec/VideoC/VideoC.html</A></TT>.
</DIV><P>VideoC translates L<sup>A</sup>T<sub>E</sub>X source into a variety of formats, including
HTML. VideoC source may contain some special constructs for
typesetting source code or to annotate text in sophisticated ways.
H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A internal engine implements some of the core constructs needed
by VideoC. The rest of VideoC constructs are implemented by
the <TT>.hva</TT> files from VideoC distribution.</P><HR CLASS="ffootnoterule"><DL CLASS="thefootnotes"><DT CLASS="dt-thefootnotes">
<A NAME="note9" HREF="#text9">8</A></DT><DD CLASS="dd-thefootnotes">According to
<TT>date</TT> man page.
</DD></DL>
<HR>
<A HREF="manual037.html"><IMG SRC="previous_motif.gif" ALT="Previous"></A>
<A HREF="manual022.html"><IMG SRC="contents_motif.gif" ALT="Up"></A>
<A HREF="manual-packages.html"><IMG SRC="next_motif.gif" ALT="Next"></A>
</BODY>
</HTML>