\newif
name, where name is made of letters
only, creates three macros:
\if
name, \
nametrue
and
\
namefalse
.
The latter two set the name condition to true and
false, respectively.
The \if
name command tests the condition name:
\if
name\else
\fi
\else
keyword can be
omitted.TeX | LATEX | |
[-.5ex]
\newif name |
\newboolean{ name} |
|
\ nametrue |
\setboolean{ name}{true} |
|
\ namefalse |
\setboolean{ name}{false} |
|
\if name text1\else
text2\fi |
\ifthenelse{\boolean{ name}}{ text1}{ text2} |
\verbatiminput
command (cf. [LATEX -bis, Page 66]) is
fully supported. Basically, this command typesets the content of a
file whose name is given as argument inside a verbatim environment.\setcounter{
name}{
num}
and \addtocounter{
name}{
num}
constructs (see [LATEX -bis, Section A.4])\setlength
and
\addtolength
constructs.
HEVEA does not implement this extension, since it does not
implement length registers in the first place.\newcolumntype
construct for user-defined column
specifications.
Table 1 gives a summary of the new column
specifications and of how HEVEA
implement them.
Note that centered, top-aligned or bottom-aligned in the vertical direction, do not have exactly the same meaning in LATEX and in HTML. However, the aspect is the same when all columns agree w.r.t. vertical alignment. Ordinary column types (
m{
width}
Equivalent to the p
column specification (the width argument is ignored, entries are typeset in paragraph mode with paragraph breaks being reduced to a single line break), except that the entries are centered vertically.b{
width}
Equivalent to the p
column specification, except that the entries are bottom-aligned vertically.>{
decl}
Can be used before l
,c
,r
,p{
...}
,m{
...}
orb{
...}
. It inserts decl in front of the entries in the corresponding column.<{
decl}
Can be used after l
,c
,r
,p{
...}
,m{
...}
orb{
...}
. It inserts decl after entries in the corresponding column.!{
decl}
Equivalent to @{
decl}
c
, l
and r
)
do not specify vertical alignment, which therefore becomes browser
dependent.>{
decl}
and <{
decl}
constructs permit the encoding of TeX \cases
macro as follows:
\def\cases#1{\left\{\begin{array}{l>{$}l<{$}}#1\end{array}\right.}(This is an excerpt of the hevea.hva file.)
\newcolumntype
construct:
\newcolumntype{
col}[
narg]{
body}
#
int).
Examples are:
\newcolumntype{C}{>{\bf}c} \newcolumntype{E}[1]{*{#1}{c}} \begin{tabular}{CE{3}}\hline one & two & three & four \\ five & six & seven & eight \\ \hline \end{tabular}The column specification C means that entries will be typeset centered and using bold font, while the column specifications
E{
num}
stands for num centered columns. We get:one | two | three | four |
five | six | seven | eight |
\newcommand
style. Thus, they have the same behavior as regards
double definition, which is not performed and induces a warning
message.
Thus, a column specification that is
first defined in a macro.hva specific
file, overrides the document definition.tabularx
package [LATEX -bis, Section 5.3.5]
provides a new tabular environment
tabularx
and a new column type X
. HEVEA makes the
former equivalent to tabular
and the latter equivalent to
p{
ignored}
.
By contrast with the subtle array formatting that the
tabularx package performs, this may seem a crude implementation.
However, rendering is usually correct, although different.