\hy-9{0}{
}






\hy-5{2}{Manual for Tex2RTF 1.33:
A LaTeX to RTF and HTML converter}

\hy-6{3}{Julian Smart
Artificial Intelligence Applications Institute

University of Edinburgh
EH1 1HN}

March 1994





\hy-5{1}{

Contents

}
\hy-6{4}{Copyright notice}

\hy-6{6}{Introduction}

\hy-6{111}{Hypertext features}

\hy-6{118}{Special sections}

\hy-6{138}{Running Tex2RTF}

\hy-6{170}{Tex2RTF for non-LaTeX users}

\hy-6{192}{Macro reference}

\hy-6{639}{Errors and bugs}

\hy-6{664}{References}

\hy-6{676}{Glossary}


\hy-10{5}{Copyright notice}


Copyright (c) 1993 Julian Smart.

Permission to use, copy, modify, and distribute this software and its
documentation for any purpose is hereby granted without fee, provided that the
above copyright notice, author statement and this permission notice appear in
all copies of this software and related documentation.

THE SOFTWARE IS PROVIDED ``AS-IS'' AND WITHOUT WARRANTY OF ANY KIND, EXPRESS,
IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT SHALL JULIAN SMART OR THE ARTIFICIAL INTELLIGENCE
APPLICATIONS INSTITUTE OR UNIVERSITY OF EDINBURGH BE LIABLE FOR ANY
SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR
ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY
OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.


\hy-10{7}{Introduction}


This document describes a utility for converting \hy-13{8}{LaTeX} files into
several other formats, and the C++ library which the converters rely on for
parsing and other services.

Only a subset of LaTeX can be processed by this utility, especially
since the target document language will never perfectly match LaTeX.
Whether the quality of the results is good enough will depend upon the
application and your own expectations.

Tex2RTF is heavily biased towards making on-line, hypertext versions of
LaTeX documents, but the \hy-13{9}{RTF} converter can be used for normal, linear
documents too.

The latest version of Tex2RTF can be accessed by anonymous ftp from:

\hy-14{10}{skye.aiai.ed.ac.uk (192.41.104.6)
}

in the directory /pub/tex2rtf. It is available in SPARC Open Look and
Windows 3.1 versions.

Tex2RTF was developed using the free Open Look, Motif and Windows 3.1
C++ class library \hy-13{11}{wxWindows}, also available from the
above FTP site in the /pub/wxwin/beta directory.

\hy-8{12}{Status of Tex2RTF}

\hy-8{17}{Why use LaTeX?}

\hy-8{21}{Help versus the printed page}

\hy-8{26}{Output Formats}

\hy-8{31}{What compromises must I make?}

\hy-8{49}{Changes to LaTeX syntax}

\hy-8{71}{Tex2RTF change log}


\hy-10{112}{Hypertext features}



LaTeX is inherently suitable for specifying hypertext documents since
it encourages description of the logical structure of a document using
section commands. Therefore, a LaTeX document is automatically
a hypertext document, without any further editing.

For Windows Help, a single RTF file is generated with topics
corresponding to sections. A top level contents page shows each chapter
or top-level section, and each chapter or section ends with a list of
further sections or subsections. Tex2RTF outputs help files that may be
read linearly using the << and >> buttons.

Similarly, a single wxHelp XLP file is generated.

For HTML, a different file is generated for each section, since the XMOSAIC browser
works best with a large number of small files. The files are named automatically
based on the name of the output file, with the contents page filename being
formed from the output filename with \hy-14{113}{_contents} appended to the name.
This may result in the generation of several hundred files for a large LaTeX 
input file. 

To specify explicit jumps around a hypertext file, the \hy-13{114}{helpref} macro is
used. The first argument is the text to be displayed at the point of reference,
which will be highlighted in a hypertext file to allow jumping to a reference.
The second argument is the reference label (there should be a corresponding
\hy-13{115}{label} command in the file, following a section or figure).

To use extra Tex2RTF features in proper LaTeX, such as \hy-8{116}{helpref}
and the C++ and CLIPS class reference documentation features, include
the style file \hy-14{117}{texhelp.sty}.


\hy-10{119}{Special sections}



The treatment of bibliography, glossary and index are worth special mention.

\hy-8{120}{Bibliography}

\hy-8{129}{Glossary}

\hy-8{134}{Index}


\hy-10{139}{Running Tex2RTF}



Tex2RTF may be run in a number of ways: with or without command line arguments,
interactively or in batch mode, and with an optional initialisation file
for specifying LaTeX macros and detailed options.

Tex2RTF accepts two arguments (input and output filenames) and trailing
(optional) switches.  If both filenames are given, the utility will work
in batch mode.  Otherwise, if Tex2RTF has been compiled for GUI
operation, a main window will be shown, with appropriate menu items for
selecting input and output filenames, starting off the conversion
process, and so on.

Note that if the file \hy-14{140}{bullet.bmp} is found by Tex2RTF, this bitmap
will be used as the bullet for items in \hy-7{141}{itemize} lists, for WinHelp
output. Otherwise, a symbol will be inserted (linear RTF) or bold `o'
will be used instead (all other formats).

Syntax error reporting is fairly minimal. Unrecognised macro errors may
actually be produced by an unbalanced brace or passing the wrong number of
arguments to a macro, so look in the vicinity of the error for the
real cause.

It is recommended that you run Tex2RTF twice in order to be sure of
of resolving all references and including an up-to-date contents page.

\hy-8{142}{Command line arguments}

\hy-8{154}{Initialisation file syntax}


\hy-10{171}{Tex2RTF for non-LaTeX users}



You don't need to have LaTeX installed to use Tex2RTF. You
can still output RTF files to be imported into your favourite
word processor, and hypertext files for on-line help.

This chapter gives a very brief introduction to LaTeX. For further
information, Kopka and Daly's \hy-7{172}{A Guide to LaTeX} [3] is
recommended.

\hy-8{173}{What is LaTeX?}

\hy-8{176}{Document structure}

\hy-8{183}{Command syntax}

\hy-8{187}{Space}


\hy-10{193}{Macro reference}



The following lists macros which are recognised by the converters. Other
macros not not mentioned can be assumed to be unrecognised or ignored.

Each command is listed with its name, the number of arguments it takes
(excluding optional arguments), and a description. Note that if the
command is used as an environment (using \hy-7{194}{begin} and \hy-7{195}{end}) then
the number of arguments must be either one or two. For example, the \hy-7{196}{
tabular} environment takes two arguments: a first argument for
specifying the formatting, and the second argument for the body of the
environment.

\hy-14{197}{\begin{tabular}{|l|l|}
\row{One}{Two}
\row{Three}{Four}
\end{tabular}
}

\hy-8{198}{Commands}

\hy-8{631}{Accents}


\hy-10{640}{Errors and bugs}



\hy-8{641}{Errors}

\hy-8{650}{Bugs}


\hy-10{665}{References}
[1] \hy-8{666}{Boggan, Scott and Fakas, David and Welinske, Joe}. 1993. \hy-7{667}{Developing on-line help for Windows. }Sams Publishing. 11711 North College, Carmel, Indiana 46032, USA. 

[2] \hy-8{668}{Smart, Julian}. 1993. \hy-7{669}{wxWindows 1.50 User Manual. }University of Edinburgh. Artificial Intelligence Applications Institute. 80 South Bridge, Edinburgh, EH1 1HN. 

[3] \hy-8{670}{Kopka, Helmut and Daly, Patrick W.} 1993. \hy-7{671}{A Guide to LaTeX. }Addison-Wesley. 

[4] \hy-8{672}{Robins, Gabriel}. 1987 (September). \hy-7{673}{The ISI grapher: a portable tool for displaying graphs pictorially (ISI/RS-87-196). }Technical report. University of South California. 

[5] \hy-8{674}{Pfeiffer, Katherine Shelly}. 1994. \hy-7{675}{Word for Windows Design Companion. }Ventana Press. 


\hy-10{677}{Glossary}

\hy-8{678}{GUI}

\hy-8{680}{HTML}

\hy-8{682}{LaTeX}

\hy-8{684}{Metafile}

\hy-8{686}{Open Look}

\hy-8{688}{RTF}

\hy-8{690}{wxHelp}

\hy-8{692}{wxWindows}

\hy-8{694}{XView}


\hy-10{13}{Status of Tex2RTF}

Tex2RTF is under continual development, often following users'
suggestions. From version 1.33, Tex2RTF is effectively in a second phase
of development. In addition to the bare minimum of syntax and facilities
for producing useable help systems or linear RTF, commands are being
added to allow visually effective, even aesthetically pleasing,
documentation to be produced.

Examples are the \hy-7{14}{indented}, \hy-7{15}{twocollist} and \hy-7{16}{marginpar} 
commands; over time I hope to be able to reproduce most of the popular
styles of formatting and presentation in Windows Help files, whilst
allowing a reasonable equivalent to be generated in the other formats.


\hy-10{18}{Why use LaTeX?}

LaTeX happens to be a very convenient format if you need to produce
documents (such as manuals, help facilities, up-to-date information) in
both printed and on-line media. Being a language rather than a WYSIWYG system,
it allows explicit specification of layout and document structure, lending
itself well to hypertext applications and automatic document generation.
Many people also prefer to use LaTeX for ordinary use since it encourages
a logical document structure and the user is not distracted by having to perfect
the appearance; many layout decisions are taken by LaTeX automatically.

Although LaTeX is not as fancy as modern word processors and desk-top
publishing packages, it is for many purposes quite adequate, and sometimes
more flexible than its modern counterparts.

The conversion utility gives LaTeX a new lease of life by allowing
virtually all other wordprocessor formats to be generated from documents
containing a reasonable subset of LaTeX syntax. From the same LaTeX 
sources, we can now generate printed manuals, Windows Help files, \hy-13{19}{wxHelp} 
files, RTF-compatible word processor formats such as MS Word, and \hy-13{20}{HTML}
files for use in the World Wide Web. Since the conversion tool is
free, as are LaTeX, HTML viewers, wxHelp and (effectively) Windows
Help, there are no financial or time penalties for providing
documentation in a wide range of printed and hypertext formats.


\hy-10{22}{Help versus the printed page}

The purist may argue, quite rightly, that on-line help systems and
printed manuals have different characteristics; help windows tend to be
much smaller than pages, help topics should be more stand-alone than
pages in a manual, navigation methods are very different, etc. Therefore,
help systems should be \hy-7{23}{based} on printed documentation but
separately hand-crafted into hypertext help, preferably by an
independent person or team.

This might be the ideal, but many organisations or individuals simply
do not have the time: on-line help wouldn't get done if the
documentation effort had to be doubled. However, Tex2RTF does provide
some commands to allow tailoring the docmentation to printed or
on-line form, such as \hy-7{24}{helponly} and \hy-7{25}{helpignore}. An awareness
of the design issues should go a long way to making the compromise
a good one, so a book such as [1] is highly recommended.


\hy-10{27}{Output Formats}

At present the following output formats are supported:



\hy-8{28}{o}  RTF (Rich Text Format). This is the most well developed
converter. RTF is commonly used as a document exchange format amongst
Windows-based applications, and is the input for the Windows Help
Compiler. Tex2RTF supports both linear documents and Windows Help
hypertext format.
\hy-8{29}{o}  wxHelp. This is the platform-independent help system for
the class library wxWindows [2]. It can display ASCII files with embedded codes
for changing font styles, but no formatting is done by wxHelp.
\hy-8{30}{o}  HTML (Hypertext Markup Language). This an SGML-like format
commonly used by documents in the World Wide Web distributed hypertext
system, and formats text dynamically rather like Windows Help.



\hy-10{32}{What compromises must I make?}

As a LaTeX user, you need to be aware that some macros or facilities
don't transfer to other formats, either because they are not supported
by the target format or because the converter does not support them. 
Maths formatting is a good example of an unsupported feature.

Sometimes LaTeX facilities must be accessed in a slightly different
way to support the variety of formats, particularly hypertext formats
where LaTeX references are often replaced by hypertext jumps (but must
still look right in printed documentation). Tables don't transfer well
to RTF (and not at all to the other formats) but an attempt is made
to approximate tables so long as special row macros are used, instead
of the usual end of row delimiter.

Bibliographies are handled quite well since the utilities can read in
\hy-14{33}{.bib} files and resolve citations. Numbers are used in citations;
the references are not yet sorted alphabetically.

Pictures are handled in a limited way: if the PSBOX macro package is
used, an \hy-7{34}{image} macro can be used to place Encapsulated PostScript
files in LaTeX, and Windows RGB-encoded bitmap files or placeable
metafiles when converting to RTF.

Nested file inclusion (input, include, verbatiminput), is handled,
and the comment environment is supported. However, using \hy-7{35}{input}
to include macro packages is not advisable. If you do this,
make sure you add a line in the Tex2RTF initialisation file to ignore
this file, unless it's a simple LaTeX file that conforms to Tex2RTF
restrictions. The file \hy-14{36}{psbox.tex} is the only file ignored
by Tex2RTF by default.

Because of the way LaTeX is parsed, some syntax has to conform to a
few simple rules. Macros such as \hy-7{37}{bf} and \hy-7{38}{it} need to occur
immediately after a left brace, and have a block of their own, since
the text within their scope is regarded as its argument. This syntax
means the same thing as using \hy-7{39}{begin ... end}, which is usually
a one argument macro (the argument is the text between the \hy-7{40}{begin}
and \hy-7{41}{end}). See \hy-13{42}{Space}.

As a Windows hypertext help writer, you don't have access to all RTF
commands but you'll be able to get most of what you want. In particular,
any LaTeX document you write will automatically be a hypertext
document, because the converter takes advantage of the hierarchy of
sections. Further jumps can be placed using the commands
\hy-13{43}{label}, \hy-13{44}{helpref},
\hy-13{45}{helprefn}, and \hy-13{46}{popref}.
Tex2RTF outputs help files that may be read linearly using the
<< and >> buttons, and an additonal Up button for
ease of navigation.

When writing HTML, multiple files are generated from one LaTeX file
since browsing HTML works best with many small files rather than a few
large ones.

wxHelp files are least well supported since there is no formatting
support, only font style, sizes and colours. Still, some hypertext help
support on UNIX/X platforms is better than none. The class library
wxWindows may be extended in future to allow using a better help viewer,
such as \hy-7{47}{xmosaic}. Of course there is nothing to stop xmosaic being
used as a help system, but it won't be integrated with wxWindows
programs as wxHelp is.

Sometimes you will use a local macro package that is unrecognised by
the converters. In this case, you may define a custom macro file
where macros are defined in terms of supported LaTeX commands
and text. Even if the result is not the same as in LaTeX, you
can probably end up with something adequate, and at least avoid
undefined macro errors. See \hy-13{48}{Initialisation file syntax} for
further information.


\hy-10{50}{Changes to LaTeX syntax}

Here are the conventions you need to observe to satisfy the Tex2RTF
parser.

\hy-8{51}{Space}

\hy-8{56}{Command arguments}

\hy-8{60}{Avoid the setlength macro}

\hy-8{64}{Units}

\hy-8{68}{Labels}


\hy-10{72}{Tex2RTF change log}

Changes in version 1.33:



\hy-8{73}{o}  Added -charset command-line switch.
\hy-8{74}{o}  Added \hy-7{75}{itemsep, twocolumn, onecolumn, setfooter, setheader, pagestyle,
pagenumbering, thechapter, thesection, thepage, thebibliography, bibitem} commands.
\hy-8{76}{o}  New environment called \hy-7{77}{twocollist} for making two-column lists,
with formatting optimized for target file format.
\hy-8{78}{o}  New \hy-7{79}{indented} environment for controlling indentation.
\hy-8{80}{o}  List indentation and bulleting improved.
\hy-8{81}{o}  Added commands \hy-7{82}{normalbox, normalboxd} for putting borders around text.
\hy-8{83}{o}  Many options can now be specified in the .ini file along with custom macros.
\hy-8{84}{o}  Cured bug that put too much vertical space after some commands.
\hy-8{85}{o}  Improved table formatting.
\hy-8{86}{o}  Optional `Up' button in WinHelp files for easier navigation.
\hy-8{87}{o}  Verbatim lines followed by \hy-7{88}{par} in RTF, to improve WinHelp wrapping.
\hy-8{89}{o}  Conversion may now be aborted under Windows by attempting to close the application.
\hy-8{90}{o}  Added conditional output for all formats: \hy-7{91}{latexignore, latexonly, rtfignore, rtfonly,
winhelpignore, winhelponly, htmlignore, htmlonly, xlpignore, xlponly.}
\hy-8{92}{o}  HTML generator can now add Contents, Up, << and >> buttons (text or bitmap) to
each page except titlepage.


Changes in version 1.32:



\hy-8{93}{o}  \hy-7{94}{footnote} command now supported in WinHelp RTF, and \hy-7{95}{footnotepopup}
added.


Changes in version 1.31:



\hy-8{96}{o}  \hy-7{97}{footnote} command now supported, in linear RTF only.
\hy-8{98}{o}  Added -bufsize option, for converting large documents.


Changes in version 1.30:



\hy-8{99}{o}  \hy-7{100}{image} command now scales metafiles (but not bitmaps).
\hy-8{101}{o}  Fixed macro loading bug, now informs the user of the found macro filename.
\hy-8{102}{o}  Now supports paragraph and subparagraph commands.
\hy-8{103}{o}  Support for some accents added.
\hy-8{104}{o}  \hy-7{105}{verb} command now supported.
\hy-8{106}{o}  Bug in subsubsection handling fixed.
\hy-8{107}{o}  Can save conversion log in a text file.


Changes in version 1.22:



\hy-8{108}{o}  More informative, warns against use of some commands.
\hy-8{109}{o}  Added compile-time support for non-GUI environments (such as plain UNIX).
\hy-8{110}{o}  Improved HTML support.



\hy-10{121}{Bibliography}

Tex2RTF recognises standard LaTeX bibliography files (usually with \hy-14{122}{.bib} extension)
and resolves citations. The \hy-13{123}{bibliography}
command reads the given \hy-14{124}{.bib} file and includes a list of
references at that point in the input. Only numbered, unsorted
references are catered for at the moment, with no variation in
bibliography style. A \hy-8{125}{References} heading is placed in the contents
section. Note that Tex2RTF must be run twice to ensure the citations are
resolved properly.

Tex2RTF can also cope with the \hy-7{126}{thebibliography} environment, with  
\hy-7{127}{bibitem} commands, so long as the text following the first \hy-7{128}{bibitem} 
argument is enclosed in braces as if it were a second argument.


\hy-10{130}{Glossary}

Glossaries are formatted according to the following scheme.
The \hy-13{131}{helpglossary} environment is used together with
the \hy-13{132}{gloss} command for glossary entries. In LaTeX this
is interpreted as a description list, and each glossary entry is an item.
In on-line help, each glossary entry is a section.

A labelled glossary entry command may be referenced by \hy-13{133}{popref} 
to provide a quick popup explanation of a term.


\hy-10{135}{Index}

The explicit index is assumed to be redundant in on-line help, since
search facilities are provided. Therefore the \hy-7{136}{printindex} command
does nothing in on-line versions (nor in linear RTF).

In Windows Help, all section headings and C++ function names are treated
as keywords. A keyword may be ambiguous, that is, refer to more than one
section in the help file.  This automatic indexing may not always be
adequate, so the LaTeX \hy-13{137}{index} command may be used
to add keywords.

In wxHelp, all section headings are indexed.


\hy-10{143}{Command line arguments}

These are the optional arguments you may give Tex2RTF on the command line.


\hy-8{144}{-bufsize}  Specifies buffer size in K (default 60 under Windows,
500 under UNIX). Large files (particularly large verbatim environments)
may require a large buffer size, equal to the largest argument of a LaTeX command.
Note that this value may not be larger than 64 under Windows.
\hy-8{145}{-html}  Specifies HTML (World Wide Web) output.
\hy-8{146}{-interactive}  Forces interactive mode even if both
filenames are given.
\hy-8{147}{-charset charset}  Specifies a character set for
RTF production. This can be one of ansi, mac, pc, and pca.
The default is ansi.
\hy-8{148}{-macros filename}  Specifies a file for the custom macro
file -- see \hy-13{149}{Macro not found error}.
\hy-8{150}{-rtf}  Specifies linear RTF output.
\hy-8{151}{-sync}  Forces synchronous mode (no yielding to other
processes) -- usually use this in non-interactive mode.
\hy-8{152}{-twice}  Tells Tex2RTF to run the conversion twice to ensure all
references and citations are resolved and the contents page included.
\hy-8{153}{-winhelp}  Specifies Windows Help RTF output.



\hy-10{155}{Initialisation file syntax}

The initialisation file contains further detailed options for
customising Tex2RTF's behaviour. A file may be specified
with the \hy-8{156}{-macros} command line switch, otherwise Tex2RTF
looks for the file \hy-14{157}{tex2rtf.ini} in the working directory
or input file directory.

The file may comprise macro definitions or option settings.

The syntax for a macro definition is:

\hy-14{158}{\name [number of args] {...LaTeX code...}
}

For example:

\hy-14{159}{\crazy      [2]{{\bf #2} is crazy but #1 is not}
\something  [0]{}
\julian     [0]{Julian Smart}
}

The syntax for an option setting is:

\hy-14{160}{name = value
}

For example:

\hy-14{161}{conversionMode = RTF
runTwice = true
titleFontSize = 12
authorFontSize = 10
headerRule = yes
footerRule = yes
}

Options expecting boolean values accept \hy-7{162}{1, 0, true, false, yes, no} in any combination of upper or
lower case.

\hy-8{163}{Tex2RTF options}


\hy-10{174}{What is LaTeX?}

LaTeX is a macro package built on top of the typesetting package,
TeX. TeX was written by Donald Knuth in the 1970s, and Leslie
Lamport wrote LaTeX as a higher-level, easier way to write TeX.

TeX was quite advanced for its day, and is still used (particularly by
academics) because of its free availability and its flexibility in
typesetting maths and other symbols. It's more like a programming
language than a word processor, with embedded commands prefixed by a
backslash and block structure. Like programs, TeX documents are
processed by a `compiler', outputting a .dvi file, which is a device
independent file which can be read by many converters for output
onto physical devices, such as screens and printers.

A reason for its longevity is the ability to add facilities to
TeX, using macro packages that define new commands.

LaTeX is the most popular way to write TeX. Although WYSIWYG
word processors and DTP packages are outstripping LaTeX, the increasing
interest in hypertext and mark-up languages makes LaTeX relevant as
a similar language to SGML documents (such as World Wide Web HTML files).

Also, languages such as LaTeX (and Rich Text Format, which it resembles
in many ways) are \hy-7{175}{complementary} to WYSIWYG packages. These languages
allow automatic production and translation of documents, where manual
mark-up is impractical or undesirable.

Since the source code of TeX and LaTeX is in the public domain,
there are many free and commercial implementations of LaTeX for almost
every computer in existance. Of PC implementations, EmTeX is arguably
the best and most complete. You can download it from various FTP sites.

If you don't want to use LaTeX itself, you may wish to use a program
called lacheck to check your documents before using Tex2RTF, since it
catches some mistakes that Tex2RTF doesn't.


\hy-10{177}{Document structure}

Here is a sample of a typical LaTeX document:

\hy-14{178}{\documentstyle[a4,texhelp]{report}
\title{A title}
\author{Julian Smart}
\date{October 1993}
\begin{document}
\maketitle

\chapter{Introduction}

...

\section{A section}

...

\end{document}
}

The first line is always a \hy-7{179}{documentstyle} command. The square brackets
enclose optional \hy-7{180}{style} files (suffix .sty) that alter the appearance
of the document or provide new commands, and the curly brackets enclose
the mandatory style, in this case `report'.

Before the document begins properly with \hy-7{181}{\begin{document}},
you can write various commands that have an effect on the appearance of the
document or define title page information. The \hy-7{182}{maketitle} command
writes the title page using information defined previously (title, author,
date).

A report has chapters, which are divided into sections, and can be further
divided into subsections and subsubsections. To start a new section, you
write the appropriate section command with the section heading; there is
no specific end section command, since a new section heading or the end
of the document will indicate the end of the previous section.

An article is divided into sections, subsections and subsubsections, but
has no chapters. This is so an article can be included in a report as a chapter.

Tex2RTF is written to deal with reports best, so stick with the report
style if you can.


\hy-10{184}{Command syntax}

There are several kinds of commands in LaTeX. Most involve a keyword
prefixed with a backslash. Here are some examples:

\hy-14{185}{\titlepage

\centerline{This is a centred line}

\begin{center}
This is a centred
paragraph
\end{center}

{\bf This is bold font}
}

The first example has no arguments. The second has one argument. The third
example is an \hy-7{186}{environment} which uses the begin and end keywords instead
of a pair of braces to enclose an argument (usually one). The fourth is an example
of using a command within a pair of braces: the command applies to the scope within
the braces. Tex2RTF treats this form as if it were a command with one argument,
with the right brace delimiting the argument. In this case, the command must
immediately follow a left brace as shown.

Commands may be nested, but not overlapped.


\hy-10{188}{Space}

In LaTeX, white space is mostly ignored, line breaks make no difference.
However, LaTeX interprets two successive newlines (a blank line) as
denoting a paragraph break. You may also use the \hy-7{189}{par} command to end
a paragraph.

\hy-6{190}{\hy-7{191}{To be continued!}}



\hy-10{199}{Commands}

\hy-8{200}{abstract:1}

\hy-8{202}{addcontentsline:3}

\hy-8{204}{author:1}

\hy-8{207}{backslash:0}

\hy-8{209}{bf:1}

\hy-8{211}{bibitem:2}

\hy-8{216}{bibliographystyle:1}

\hy-8{218}{bibliography:0}

\hy-8{221}{caption:1}

\hy-8{225}{cdots:0}

\hy-8{227}{centerline:1}

\hy-8{229}{center:1}

\hy-8{231}{cextract:0}

\hy-8{233}{chapter*:1}

\hy-8{235}{chapter:1}

\hy-8{237}{chapterheading:1}

\hy-8{241}{cinsert:0}

\hy-8{243}{cite:1}

\hy-8{245}{class:1}

\hy-8{247}{clipsfunc:3}

\hy-8{249}{comment:1}

\hy-8{251}{copyright:0}

\hy-8{253}{cparam:2}

\hy-8{256}{date:1}

\hy-8{259}{description:1}

\hy-8{262}{documentstyle:1}

\hy-8{267}{document:1}

\hy-8{269}{em:1}

\hy-8{271}{enumerate:1}

\hy-8{274}{figure:1}

\hy-8{276}{flushleft:1}

\hy-8{278}{flushright:1}

\hy-8{280}{footnote:1}

\hy-8{284}{footnotepopup:2}

\hy-8{289}{functionsection:1}

\hy-8{292}{func:3}

\hy-8{295}{gloss:1}

\hy-8{303}{helpglossary:1}

\hy-8{306}{helpignore:1}

\hy-8{308}{helponly:1}

\hy-8{310}{helpinput:1}

\hy-8{312}{helpfontfamily:1}

\hy-8{314}{helpfontsize:1}

\hy-8{316}{helpref:2}

\hy-8{321}{helprefn:2}

\hy-8{324}{hline:0}

\hy-8{328}{hrule:0}

\hy-8{331}{htmlignore:1}

\hy-8{333}{htmlonly:1}

\hy-8{335}{huge:1}

\hy-8{337}{Huge:1}

\hy-8{340}{HUGE:1}

\hy-8{343}{include:1}

\hy-8{345}{indented:2}

\hy-8{348}{input:1}

\hy-8{350}{itemize:1}

\hy-8{355}{item:0}

\hy-8{360}{itemsep:0}

\hy-8{362}{image:2}

\hy-8{370}{index:1}

\hy-8{372}{it:1}

\hy-8{374}{label:1}

\hy-8{376}{large:1}

\hy-8{378}{Large:1}

\hy-8{381}{LARGE:1}

\hy-8{384}{LaTeX:0}

\hy-8{386}{latexignore:1}

\hy-8{388}{latexonly:1}

\hy-8{390}{ldots}

\hy-8{392}{maketitle}

\hy-8{397}{marginparwidth:1}

\hy-8{399}{marginpar:1}

\hy-8{403}{marginpareven:1}

\hy-8{406}{marginparodd:1}

\hy-8{413}{membersection:1}

\hy-8{415}{member:1}

\hy-8{417}{newcommand:3}

\hy-8{422}{newpage:0}

\hy-8{424}{nocite:1}

\hy-8{427}{noindent:0}

\hy-8{430}{normalbox:1}

\hy-8{434}{normalboxd:1}

\hy-8{438}{normalsize:1}

\hy-8{440}{onecolumn:0}

\hy-8{442}{pagestyle:1}

\hy-8{448}{pagenumbering:1}

\hy-8{455}{paragraph*}

\hy-8{457}{paragraph}

\hy-8{459}{param:1}

\hy-8{462}{parindent:1}

\hy-8{464}{parskip:1}

\hy-8{467}{par:0}

\hy-8{469}{popref:2}

\hy-8{473}{psboxto:2}

\hy-8{476}{quote:1}

\hy-8{478}{quotation:1}

\hy-8{480}{ref:1}

\hy-8{483}{rm:1}

\hy-8{485}{row:1}

\hy-8{489}{ruledrow:1}

\hy-8{493}{rtfignore:1}

\hy-8{495}{rtfonly:1}

\hy-8{497}{rtfsp:0}

\hy-8{499}{sc:1}

\hy-8{501}{section*:1}

\hy-8{503}{section:1}

\hy-8{505}{sectionheading:1}

\hy-8{508}{setfooter:6}

\hy-8{518}{setheader:6}

\hy-8{529}{shortcite:1}

\hy-8{532}{small:1}

\hy-8{534}{subparagraph*:1}

\hy-8{536}{subparagraph:1}

\hy-8{538}{subsection*:1}

\hy-8{540}{subsection:1}

\hy-8{542}{subsubsection*:1}

\hy-8{544}{subsubsection:1}

\hy-8{546}{tabbing:1}

\hy-8{548}{tableofcontents:0}

\hy-8{550}{tabular:2}

\hy-8{563}{TeX:0}

\hy-8{565}{textwidth:1}

\hy-8{568}{thebibliography:1}

\hy-8{572}{title:1}

\hy-8{575}{tiny:1}

\hy-8{577}{today:0}

\hy-8{579}{tt:1}

\hy-8{581}{typeout:1}

\hy-8{583}{twocolitem:2}

\hy-8{587}{twocolitemruled:2}

\hy-8{591}{twocollist:1}

\hy-8{600}{twocolwidtha:1}

\hy-8{604}{twocolwidthb:1}

\hy-8{608}{twocolumn:0}

\hy-8{610}{underline:1}

\hy-8{612}{verbatiminput:1}

\hy-8{615}{verbatim:1}

\hy-8{617}{verb}

\hy-8{623}{winhelpignore:1}

\hy-8{625}{winhelponly:1}

\hy-8{627}{xlpignore:1}

\hy-8{629}{xlponly:1}


\hy-10{632}{Accents}

The following LaTeX accents work for RTF production:


\hy-8{633}{o}  \'{a} produces a. Valid for a, e, i, o, u, A, E, I, O, U
\hy-8{634}{o}  \`{a} produces a. Valid for a, e, i, o, u, y, A, E, I, O, U, Y
\hy-8{635}{o}  \^{a} produces a. Valid for a, e, i, o, u, A, E, I, O, U
\hy-8{636}{o}  \~{a} produces a. Valid for a, n, o, A, N, O
\hy-8{637}{o}  \"{a} produces a. Valid for a, e, i, o, u, y, A, E, I, O, U, Y
\hy-8{638}{o}  \.{a} produces a. Valid for a, A



\hy-10{642}{Errors}

The following sections explain some of the errors that may occur,
and how to deal with them.

\hy-8{643}{Macro not found}

\hy-8{648}{Unresolved references}


\hy-10{651}{Bugs}


\hy-8{652}{Command parsing.}  If a command is used followed by inappropriate
argument syntax, Tex2RTF can crash. This an occur when a command is
used in an asterisk form that is only formed in the non-asterisk
variety. The non-asterisk form is assumed, which makes the following
asterisk trip up the parser.
\hy-8{653}{Setlength.}  Using the \setlength command doesn't work,
since its first argument looks like a macro with the wrong number
of arguments. Use an alternative form instead, e.g. \parindent 0pt instead
of \setlength{parindent}{0pt}.
\hy-8{654}{Newcommand bug.}  Environments in a command definition confuse
Tex2RTF. Use the command form instead (e.g. \flushleft{...} instead
of \begin{flushleft} ... \end{flushleft}.
\hy-8{655}{Bibliography.}  There's no flexibility in the way references
are output: I expect I'll get round to doing something better,
but only if people tell me they need it!
\hy-8{656}{Tables.}  Tables can't handle all LaTeX syntax, and require
the Tex2RTF \row commands for decent formatting. Still, it's
better than it was (RTF only).
\hy-8{657}{Indexes and glossaries.}  Not yet supported.
\hy-8{658}{Crashes.}  Crashes may be due to an input file exceeding the fixed-size
buffer used for converting command arguments, especially for the \hy-7{659}{verbatim}
command. Use the \hy-8{660}{-bufsize} switch to increase the buffer size.
\hy-8{661}{Verbatiminput.}  Verbatiminput files which do not end with a blank line
can trip up following commands.
\hy-8{662}{Comment.}  The \hy-7{663}{comment} environment doesn't really ignore its argument
when parsing, so it will trip up over unrecognised syntax and commands.







\hy-10{679}{GUI}

Graphical User Interface, such as Windows 3 or X.


\hy-10{681}{HTML}

Hypertext Markup Language; an SGML document type, used for providing
hypertext information on the World Wide Web, a distributed hypertext
system on the Internet.


\hy-10{683}{LaTeX}

A typesetting language implemented as a set of TeX macros. It is
distinguished for allowing specification of the document structure,
whilst taking care of most layout concerns. It represents the opposite
end of the spectrum from WYSIWYG word processors.


\hy-10{685}{Metafile}

Microsoft Windows-specific object which may contain a restricted set of
GDI primitives. It is device independent, since it may be scaled without
losing precision, unlike a bitmap. A metafile may exist in a file or in
memory. wxWindows implements enough metafile functionality to use it to
pass graphics to other applications via the clipboard. A placeable metafile
is a metafile with a 22-byte header which can be imported into several
Windows applications, and is a format used by the Microsoft help compiler.


\hy-10{687}{Open Look}

A specification for a GUI `look and feel', initiated by Sun
Microsystems. XView is one toolkit for writing Open Look applications
under X, and wxWindows sits on top of XView.


\hy-10{689}{RTF}

Rich Text Format: an interchange format for word processor files,
used for importing and exporting formatted documents, and as the
input to the Windows Help compiler.


\hy-10{691}{wxHelp}

wxHelp is the hypertext help facility used to provide on-line
documentation for UNIX-based wxWindows applications. Under Windows 3.1,
Windows Help is used instead.


\hy-10{693}{wxWindows}

wxWindows is a free C++ toolkit for writing applications that are
portable across several platforms. Currently these are Motif, Open Look,
Windows 3.1 and Windows NT.


\hy-10{695}{XView}

An X toolkit supplied by Sun Microsystems, initially just for porting
SunView applications to X, but which has become a popular toolkit in its
own right due to its simplicity of use. XView implements Sun's Open Look
`look and feel' for X, but is not the only toolkit to do so.






\hy-10{52}{Space}

Tex2RTF attempts to insert spaces where LaTeX assumes whitespace.
However, for the benefit of RTF conversion, you need to use the \hy-7{53}{
\rtfsp} macro where a command or brace within a paragraph
begins or ends with a macro. For example:

\hy-14{54}{Within a paragraph, you need to be careful about commands that begin
\rtfsp {\it at the start} of a line.
}

As normal with LaTeX, two newlines represents a paragraph break,
although \hy-13{55}{par} can also be used at the end of a paragraph.

You need to have a blank line between section and some environment
commands and the first paragraph or your document will look rather
weird, e.g. headings running into paragraphs.

wxHelp is more fussy than LaTeX or RTF: you need to use percent
characters at line ends liberally to eliminate newlines after commands
on single lines.


\hy-10{57}{Command arguments}

Commands that have one or more arguments can be used in the following
three ways:

\hy-14{58}{\bf{Some text.}

\begin{bf}
Some text.
\end{bf}

{\bf Some text.}
}

The first method is a normal LaTeX command.

The second method is called an \hy-7{59}{environment}; LaTeX has specific
environments that do not always correspond to normal commands, but
Tex2RTF recognizes environments and normal commands interchangeably, so
long as the command has no more than two arguments.

With the third method, it is important that the command has its own
pair of braces, and that the command immediately follows the first brace.
Otherwise, the parser cannot parse the argument(s) properly.
With multiple arguments, each should be enclosed in braces.

Optional arguments are specified using square brackets or parentheses.

Whitespace should be avoided between command names and their arguments.


\hy-10{61}{Avoid the setlength macro}

Using the \setlength command doesn't work, since its first
argument looks like a macro with the wrong number of arguments. Use an
alternative form instead, e.g.

\hy-14{62}{\parindent 0pt
}

instead of

\hy-14{63}{\setlength{\parindent}{0pt}
}


\hy-10{65}{Units}

Only a subset of LaTeX units may be used for specifying dimensions.
Valid units are \hy-7{66}{pt, mm, cm} and \hy-7{67}{in}. Units should usually
be specified for dimensions or the results may be unexpected.


\hy-10{69}{Labels}

The \hy-7{70}{label} command may be used for sections and figure captions,
but must come immediately after the section or caption commands with no
intervening whitespace.


\hy-10{164}{Tex2RTF options}

These are the allowable options in an initialisation file.


OptionDescription
conversionModeOne of RTF, WinHelp, XLP (or wxHelp), and HTML.
documentFontSizeOne of 10, 11 and 12, to specify the main font size
independently of the LaTeX document style command.
chapterFontSizeSpecifies the point size for chapter headings (RTF only).
sectionFontSizeSpecifies the point size for section headings (RTF only).
subsectionFontSizeSpecifies the point size for subsection headings (RTF only).
titleFontSizeSpecifies the point size for the title (RTF only).
authorFontSizeSpecifies the point size for the author and date (RTF only).
ignoreInputAdds the filename to the list of files ignored by the \hy-7{165}{input} command.
The only default filename in the list is \hy-14{166}{psbox.tex}.
mirrorMarginsIf true, margins are mirrored in twosided documents (linear RTF only).
runTwiceIf true, runs the converter twice.
isInteractiveIf true, runs in interactive mode (the default).
headerRuleIf true, draws a rule below headers (linear RTF only).
footerRuleIf true, draws a rule above footers (linear RTF only).
listLabelIndentSpecifies the size of list item label indentation, in points.
itemLabelIndentSpecifies the size of list item indentation, in points.
useUpButtonIf true (the default), WinHelp files will be generated with an \hy-8{167}{Up}
button to make browsing easier. Note that you need to put an extra line in the CONFIG section
of your .HPJ file:

\hy-14{168}{CreateButton("Up", "&Up", "JumpId(`name.hlp', `Contents')")}

where \hy-14{169}{name.hlp} is the name of your help file.
htmlBrowseButtonsAllows generation of Contents, Up, browse back and browse forward
buttons on each HTML page except title page. Specify none, text or bitmap. If you specify
bitmap, make sure that the files contents.gif, up.gif, back.gif and forward.gif are in the
directory where the HTML files will reside: samples are given in the docs directory.



\hy-10{201}{abstract:1}

This standard LaTeX environment prepares an abstract page, and is
treated as an ordinary chapter or section in on-line help.


\hy-10{203}{addcontentsline:3}

Adds a chapter title to the contents page. Linear RTF. Rarely required.


\hy-10{205}{author:1}

Defines the author, for output when \hy-7{206}{maketitle} is used.


\hy-10{208}{backslash:0}

Outputs a backslash in math mode (should be enclosed by two dollar symbols).


\hy-10{210}{bf:1}

Specifies bold font.


\hy-10{212}{bibitem:2}

For parsing convenience, \hy-7{213}{bibitem} requires two arguments: a cite key and item.
LaTeX syntax permits writing this as if it were two arguments,
even though it is in fact only one. This command is used within
a \hy-13{214}{thebibliography} environment. The preferred
method is to store references in .bib files and use the \hy-13{215}{bibliography}
command to generate a bibliography section automatically.


\hy-10{217}{bibliographystyle:1}

Currently doesn't affect the style of bibliography, but probably will
in the future.


\hy-10{219}{bibliography:0}

Includes the bibliography at this point in the document. See the section
on \hy-13{220}{bibliographies}.


\hy-10{222}{caption:1}

Specifies a caption (within a \hy-13{223}{figure} environment). This may
be followed immediately by a \hy-13{224}{label} command.


\hy-10{226}{cdots:0}

Outputs three dots.


\hy-10{228}{centerline:1}

Centres (or centers!) a line of text.


\hy-10{230}{center:1}

Centres a block of text.


\hy-10{232}{cextract:0}

Prints a C++ extraction operator (>>).


\hy-10{234}{chapter*:1}

Outputs a chapter heading with no contents entry.


\hy-10{236}{chapter:1}

Outputs a chapter heading.


\hy-10{238}{chapterheading:1}

Like \hy-13{239}{chapter}, but does not increment the chapter
number and does not print a chapter number in the printed documentation
contents page, or in the chapter heading. Used to implement \hy-13{240}{glossaries} and
other sections that are not real chapters.


\hy-10{242}{cinsert:0}

Prints a C++ insertion operator (<<).


\hy-10{244}{cite:1}

Cite a reference. The argument is a reference key as defined in a LaTeX .bib
file.


\hy-10{246}{class:1}

Outputs the argument, an index entry (LaTeX only) and a keyword entry (WinHelp only).
Used in class reference documentation.


\hy-10{248}{clipsfunc:3}

Formats a CLIPS function, given the return value, function name, and
arguments.


\hy-10{250}{comment:1}

Allows large comments in LaTeX files. Ignored by Tex2RTF.


\hy-10{252}{copyright:0}

Outputs the copyright symbol.


\hy-10{254}{cparam:2}

Formats a CLIPS type and argument. Used within the third argument of
a \hy-13{255}{clipsfunc} command.


\hy-10{257}{date:1}

Specifies the date of a document; only output by \hy-13{258}{maketitle}.


\hy-10{260}{description:1}

A list environment, where each \hy-13{261}{item} command must be
followed by optional (!) square-bracketed text which will be highlighted.


\hy-10{263}{documentstyle:1}

Specifies the main style (report, article etc.) and, optionally, style files
such as \hy-14{264}{texhelp.sty}. A report has \hy-13{265}{chapters}, while an article's top-level
sections are specified using \hy-13{266}{section}.


\hy-10{268}{document:1}

This environment should enclose the body of a document.


\hy-10{270}{em:1}

Emphasizes text (italic in RTF).


\hy-10{272}{enumerate:1}

Enumerate list environment: numbers the \hy-13{273}{items}.


\hy-10{275}{figure:1}

A figure enviroment: does nothin in RTF.


\hy-10{277}{flushleft:1}

Flushes the given text to the left margin.


\hy-10{279}{flushright:1}

Flushes the given text to the right margin.


\hy-10{281}{footnote:1}

In linear RTF, a footnote is created. Whether this appears at the end of
the section or the bottom of the page appears to depend on the current
document style, at least for MS Word 6.0 for Windows. The default seems
to be to put the footnotes at the end of the section, which is probably
not the best assumption.

In WinHelp RTF, a bracketed number is generated for the footnote
and the footnote becomes a popup topic. It is probably preferable
to change footnote commands to \hy-13{282}{footnotepopup},
or \hy-13{283}{popref} references to glossary entries.

This command is not supported for formats other than LaTeX,
linear RTF and WinHelp RTF.


\hy-10{285}{footnotepopup:2}

In linear RTF, a footnote is created following the first argument, as with
\hy-13{286}{footnote}.

In WinHelp RTF, a the first argument is highlighted and becomes
a popup reference to the second argument. See also \hy-13{287}{footnote}
and \hy-13{288}{popref}.

This command is not supported for formats other than LaTeX,
linear RTF and WinHelp RTF.


\hy-10{290}{functionsection:1}

Defines a subsection, adding the C++ function name to the LaTeX index or the
WinHelp keyword list.

Should be followed by a \hy-13{291}{func} command to specify function
details.


\hy-10{293}{func:3}

Defines a C++ function, given the return type, function name, and parameter list.

Should occur after a \hy-13{294}{functionsection} command.


\hy-10{296}{gloss:1}

Marks a glossary entry. In LaTeX, this is a synonym for an \hy-13{297}{item}
with an optional argument, within a \hy-13{298}{description} environment,
and the argument is added to the index.

In Windows Help, this is identical to a \hy-13{299}{section*} in a report.

If labels are associated with the glossary entries, they can be referenced by
\hy-13{300}{helpref} or \hy-13{301}{popref} jumps. A glossary entry is
currently the only type of destination that popref may refer to.

This is an example of making a glossary in a report:

\hy-14{302}{\begin{helpglossary}

\gloss{API}\label{api}

Application Programmer's Interface - a set of calls and classes defining
how a library (in this case, wxWindows) can be used.

\gloss{Canvas}\label{canvas}

A canvas in XView and wxWindows is a subwindow...

\gloss{DDE}\label{dde}

Dynamic Data Exchange - Microsoft's interprocess communication protocol.
wxWindows provides an abstraction of DDE under both Windows and UNIX.

\end{helpglossary}
}


\hy-10{304}{helpglossary:1}

An environment for making a glossary (not standard LaTeX). See \hy-13{305}{gloss} for
usage.


\hy-10{307}{helpignore:1}

Ignores the argument in Tex2RTF generated files, but not LaTeX.


\hy-10{309}{helponly:1}

Only outputs the argument in Tex2RTF generated files.


\hy-10{311}{helpinput:1}

Only includes the given file in Tex2RTF generated files.


\hy-10{313}{helpfontfamily:1}

Specifies the font family for Tex2RTF generated files. The argument
may be Swiss or Times.


\hy-10{315}{helpfontsize:1}

Specifies the font size for Tex2RTF generated files.


\hy-10{317}{helpref:2}

Specifies a jump to a labelled chapter, section, subsection subsubsection
or figure.

The first argument is text to be highlighted (mouseable in help systems)
and the second is the reference label. In linear documents, the section number
is given following the text, unless the \hy-13{318}{helprefn} command
is used instead, where the section number is suppressed.

Note that when generating HTML, the label \hy-7{319}{contents} is automatically defined,
and may be referenced using \hy-7{320}{helpref}.


\hy-10{322}{helprefn:2}

Specifies a jump to a labelled chapter, section, subsection subsubsection
or figure.

The first argument is text to be highlighted (mouseable in help systems)
and the second is the reference label.  See \hy-13{323}{helpref} for
the form where the section number is printed in linear documents.


\hy-10{325}{hline:0}

Within a \hy-13{326}{tabular} environment, draws a horizontal
rule below the current row. Note that this does not work in RTF for the
last row of a table, in which case the command \hy-13{327}{ruledrow}
should be used instead.


\hy-10{329}{hrule:0}

Draws a horizontal line below the current paragraph. For example:

\hy-14{330}{This paragraph should have a horizontal rule following it.\hrule
}

gives:

This paragraph should have a horizontal rule following it.
------------------------------------------------------------------


\hy-10{332}{htmlignore:1}

Ignores the argument in HTML.


\hy-10{334}{htmlonly:1}

Only outputs the argument in HTML.


\hy-10{336}{huge:1}

Outputs the argument in huge text.


\hy-10{338}{Huge:1}

Outputs the argument in huger text that \hy-13{339}{huge}.


\hy-10{341}{HUGE:1}

Outputs the argument in huger text that \hy-13{342}{Huge}.


\hy-10{344}{include:1}

Include the given file. The command must not be preceded by any whitespace,
and spurious whitespace between elements of the command will also
trip up Tex2RTF.


\hy-10{346}{indented:2}

Environment supplied by Tex2RTF to allow (possibly nested) indentation of
LaTeX and RTF text. The first argument is the amount to be indented.

For example:

\hy-14{347}{\begin{indented}{2cm}
This text should be indented by a couple of centimetres. This can be
useful to highlight paragraphs.
\end{indented}
}

produces:


This text should be indented by a couple of centimetres. This can be
useful to highlight paragraphs.



\hy-10{349}{input:1}

Include the given file. The command must not be preceded by any whitespace,
and spurious whitespace between elements of the command will also
trip up Tex2RTF.


\hy-10{351}{itemize:1}

Indents each \hy-13{352}{item} of a list and precedes with a bullet.
If the file \hy-14{353}{bullet.bmp} is found by Tex2RTF, this bitmap will be
used as the bullet (WinHelp RTF); otherwise, a symbol or bold `o' will be used instead,
depending on output format.

Use \hy-13{354}{itemsep} to specify the separation between
list items. Currently this only works for linear or WinHelp RTF output.
If the value is more than zero, an extra paragraph is inserted.


\hy-10{356}{item:0}

Marks an item of a \hy-13{357}{itemize}, \hy-13{358}{description} or \hy-13{359}{enumerate}
list. Items within a description environment should have an `optional' argument
in square brackets which will be highlighted.


\hy-10{361}{itemsep:0}

Use this command to specify the separation between
list items. Currently this only works for linear or WinHelp RTF output.
If the value is zero, no extra paragraph is inserted; if the value
is more than zero, an extra paragraph is inserted.


\hy-10{363}{image:2}

This is translated to a PSBOX macro package \hy-7{364}{psboxto} command in LaTeX,
the first argument being a sizing command and the second a filename.

In HTML mode, the second argument is used to generate a PostScript file reference.

In RTF mode, the second argument is tried with first a BMP extension and
then a WMF extension to find a suitable Windows bitmap file or placeable
metafile. If a suitable file is found, in Windows Help mode a \hy-7{365}{bmc}
command is inserted into the RTF file with a reference to the file. In
linear RTF mode, the bitmap or metafile is converted into hex and
inserted into the RTF document.

Note that only RGB-encoded Windows bitmaps, or placeable metafiles, are
valid for input to Tex2RTF. You can convert a RLE (run length encoded)
bitmap file into a (bigger) RGB file using a program such as Paintshop
Pro. A placeable metafile has a special header with dimension
information. One may be constructed by a wxWindows program by calling
the function wxMakeMetafilePlaceable. The Microsoft Windows SDK has a
sample program that loads and steps through placeable and ordinary
metafiles.

Here is an example of using the \hy-7{366}{image} command.

\hy-14{367}{\begin{figure}
$$\image{5cm;0cm}{heart.ps}$$

\caption{My picture}\label{piccy}
\end{figure}
}

The dollars centre the image in the horizontal plane. The syntax
of the first argument to \hy-7{368}{image} is taken from syntax used by the \hy-7{369}{psbox}
package: it allows specification of the horizontal and vertical
dimensions of the image. Scaling will take place for PostScript
and metafile images. A value of zero indicates that the image should
be scaled in proportion to the non-zero dimension. Zeros for both
dimensions will leave the image unscaled in the case of metafiles,
or scaled to fit the page in the case of PostScript.


\hy-10{371}{index:1}

In WinHelp mode, adds a keyword to the keyword list for the current
topic. This keyword must currently be straight text, with no embedded
commands. The conversion process must be run twice (without quitting
Tex2RTF inbetween) to resolve the keyword references.


\hy-10{373}{it:1}

Marks the argument in italic.


\hy-10{375}{label:1}

Labels the chapter, section, subsection, subsubsection or figure caption
with the given label. This must be an ASCII string, and duplicate items
with different case letters are not allowed.

The command must follow immediately after the section or caption command,
with no intervening whitespace.


\hy-10{377}{large:1}

Marks the argument in large text.


\hy-10{379}{Large:1}

Makes the argument display in larger text than \hy-13{380}{large}.


\hy-10{382}{LARGE:1}

Makes the argument display in larger text than \hy-13{383}{Large}.


\hy-10{385}{LaTeX:0}

Outputs the annoying LaTeX upper and lower case name.


\hy-10{387}{latexignore:1}

Ignores the argument in LaTeX.


\hy-10{389}{latexonly:1}

Only prints the argument in LaTeX.


\hy-10{391}{ldots}

Outputs three dots.


\hy-10{393}{maketitle}

Makes the article or report title by outputting the \hy-13{394}{title},
\hy-13{395}{author} and optionally \hy-13{396}{date}.


\hy-10{398}{marginparwidth:1}

Specifies the width of a margin paragraph.


\hy-10{400}{marginpar:1}

Inserts a marginal note. It is best to use the Tex2RTF extensions 
\hy-13{401}{marginparodd} and \hy-13{402}{marginpareven} 
for best results.


\hy-10{404}{marginpareven:1}

Inserts a marginal note on even pages. This is required for RTF generation since
it is impossible for Tex2RTF to know in advance which side of paper the marginal note
will fall upon, and the text has to be positioned using absolute dimensions.
If only one sided output is required, use \hy-13{405}{marginparodd} 
instead.


\hy-10{407}{marginparodd:1}

Inserts a marginal note on odd pages. This is required for RTF generation since
it is impossible for Tex2RTF to know in advance which side of paper the marginal note
will fall upon, and the text has to be positioned using absolute dimensions.

Also, even if one-sided output is required, this command should be used instead
of \hy-7{408}{marginpar} because the LaTeX macro allows it to be used
just before a paragraph. Normally, if this were done, the marginal note would
not be aligned with the paragraph succeeding it. For example:

\hy-14{409}{\marginparodd{{\it Note:} if nothing happens, perhaps you have not plugged
your computer in at the mains.}%
To start using your WhizzyGig Computer 4001, push the Power button and
wait for some kind of response.
}

Note the percent sign after the \hy-7{410}{marginparodd} command: without it,
LaTeX refuses to believe that the following text is part of the
same paragraph, and will print the note at the wrong place.

You should use \hy-13{411}{textwidth} to allow space for marginal
notes, and also \hy-13{412}{marginparwidth} to specify the size of
the marginal note.

In WinHelp, HTML and wxHelp, marginal notes are treated as normal text delineated
with horizontal rules above and below.


\hy-10{414}{membersection:1}

Used when formatting C++ classes to print a subsection for the member name.


\hy-10{416}{member:1}

Used to format a C++ member variable name.


\hy-10{418}{newcommand:3}

Define a new command; arguments are the command, the number of
arguments, and the command body. For example:

\hy-14{419}{\newcommand{\crazy}[2]{{\bf #1} is crazy but {\bf #2} is not.}
}

The command must have no whitespace at the start of the line or between
the three arguments.

New commands may also be defined in the \hy-14{420}{tex2rtf.ini} file using
slightly different syntax (see \hy-13{421}{Macro not found error}).


\hy-10{423}{newpage:0}

Inserts a page break.


\hy-10{425}{nocite:1}

Specifies that this reference should appear in the bibliography,
but the citation should not appear in the text.

See also \hy-13{426}{cite}.


\hy-10{428}{noindent:0}

Sets paragraph indentation to zero. See also \hy-13{429}{parindent}.


\hy-10{431}{normalbox:1}

Draws a box around the given paragraph in LaTeX and RTF. In HTML
and XLP formats, horizontal rules are drawn before and after the text.

For example:

\hy-14{432}{\normalbox{This should be a boxed paragraph for highlighting important
information, such as information for registering a shareware program.}
}

gives:

----------------------------------------------------------------------
This should be a boxed paragraph for highlighting important
information,such as information for registering a shareware program.
----------------------------------------------------------------------


See also \hy-13{433}{normalboxd} for double-bordered text.


\hy-10{435}{normalboxd:1}

Draws a double border around the given paragraph in LaTeX and RTF. In
HTML and XLP formats, horizontal rules are drawn before and after the
text.

For example:

\hy-14{436}{\normalboxd{This should be a boxed paragraph for highlighting important
information, such as information for registering a shareware program.}
}

gives:

----------------------------------------------------------------------
This should be a boxed paragraph for highlighting important
information,such as information for registering a shareware program.
----------------------------------------------------------------------


See also \hy-13{437}{normalbox} for single-bordered text.


\hy-10{439}{normalsize:1}

Sets the font size back to normal.


\hy-10{441}{onecolumn:0}

Sets the number of columns to one. LaTeX and linear RTF only.


\hy-10{443}{pagestyle:1}

If argument is \hy-7{444}{fancyplain} or \hy-7{445}{fancy}, Tex2RTF
separates the header from the rest of the page with a rule.
This command must be defined for headers and footers to
work properly. See also \hy-13{446}{setheader},
\hy-13{447}{setfooter}.

LaTeX and linear RTF only.


\hy-10{449}{pagenumbering:1}

The argument may be one of:



\hy-8{450}{alph}  a, b, ...
\hy-8{451}{Alph}  A, B, ...
\hy-8{452}{arabic}  1, 2, ...
\hy-8{453}{roman}  i, ii, ...
\hy-8{454}{Roman}  I, II, ...


LaTeX and linear RTF only.


\hy-10{456}{paragraph*}

Behaves as for a subsubsection.


\hy-10{458}{paragraph}

Behaves as for a subsubsection.


\hy-10{460}{param:1}

Formats a C++ type and argument pair. Should be used within the third argument
of a a \hy-13{461}{func} command.


\hy-10{463}{parindent:1}

Indents the first line of succeeding paragraphs by the given amount.


\hy-10{465}{parskip:1}

Changes the spacing between paragraphs. In fact, in RTF this will cause
two \hy-13{466}{par} commands to be output if parindent is greater
than zero.


\hy-10{468}{par:0}

Causes the paragraph to end at this point. LaTeX and Tex2RTF also
treat two consecutive newlines as a paragraph break.


\hy-10{470}{popref:2}

Similar to \hy-13{471}{helprefn}, except that in Windows Help,
the destination text is popped up in a small window to be dismissed with
a mouse click, instead of going to a separate section.

Currently this command can only refer to a labelled glossary entry; see
\hy-13{472}{gloss}.


\hy-10{474}{psboxto:2}

Identical to \hy-13{475}{image}.


\hy-10{477}{quote:1}

Indents a short quotation.


\hy-10{479}{quotation:1}

Indents a long quotation.


\hy-10{481}{ref:1}

In LaTeX and linear RTF, refers to a \hy-13{482}{label} and
causes the number of that section or figure to be printed.


\hy-10{484}{rm:1}

Causes the argument to be formatted in a plain, roman font.


\hy-10{486}{row:1}

A Tex2RTF command signifying the row of a table within the \hy-13{487}{tabular}
environment. See also \hy-13{488}{ruledrow}.


\hy-10{490}{ruledrow:1}

A Tex2RTF command signifying a ruled row of a table within the \hy-13{491}{tabular}
environment. See also \hy-13{492}{row}.


\hy-10{494}{rtfignore:1}

Ignores the argument in linear RTF.


\hy-10{496}{rtfonly:1}

Only outputs the argument in linear RTF.


\hy-10{498}{rtfsp:0}

Outputs a space in RTF. Tex2RTF tries to insert a space where one is implied
by a newline, but cannot cope where a line starts or ends with a command,
in the middle of a paragraph. Use this command to insert a space explicitly.


\hy-10{500}{sc:1}

Prints the output in small capitals.


\hy-10{502}{section*:1}

Section header, with no entry in the contents page.


\hy-10{504}{section:1}

Section header, with an entry in the contents page.


\hy-10{506}{sectionheading:1}

Like \hy-13{507}{section}, but does not increment the section
number and does not print a section number in the printed documentation
contents page, or in the section heading.


\hy-10{509}{setfooter:6}

Tex2RTF has a non-standard way of setting headers and footers,
but the default macro definitions in texhelp.sty may be altered
to your current method.

The arguments are as follows:



\hy-8{510}{1.}  Left footer, even pages
\hy-8{511}{2.}  Centre footer, even pages
\hy-8{512}{3.}  Right footer, even pages
\hy-8{513}{4.}  Left footer, odd pages
\hy-8{514}{5.}  Centre footer, odd pages
\hy-8{515}{6.}  Right footer, odd pages


For many documents, the first three arguments will be left empty.

The behaviour for first pages of a chapter, section or document
is to have a blank header, but print the footer.

For best results, define headers and footers for \hy-7{516}{each chapter or
section}.

Note that this command works only for LaTeX and linear RTF. See also
\hy-13{517}{setheader}.


\hy-10{519}{setheader:6}

Tex2RTF has a non-standard way of setting headers and footers,
but the default macro definitions in texhelp.sty may be altered
to your current method.

The arguments are as follows:



\hy-8{520}{1.}  Left header, even pages
\hy-8{521}{2.}  Centre header, even pages
\hy-8{522}{3.}  Right header, even pages
\hy-8{523}{4.}  Left header, odd pages
\hy-8{524}{5.}  Centre header, odd pages
\hy-8{525}{6.}  Right header, odd pages


For many documents, the first three arguments will be left empty.
If \hy-13{526}{pagestyle} is not plain or empty, the
header will separated from the rest of the page by a rule.

The behaviour for first pages of a chapter, section or document
is to have a blank header, but print the footer.

For best results, define headers and footers for \hy-7{527}{each chapter or
section}.

Note that this command works only for LaTeX and linear RTF. See also
\hy-13{528}{setfooter}.


\hy-10{530}{shortcite:1}

The same as \hy-13{531}{cite}.


\hy-10{533}{small:1}

Prints the argument in a small font.


\hy-10{535}{subparagraph*:1}

Behaves as for a subsubsection.


\hy-10{537}{subparagraph:1}

Behaves as for a subsubsection.


\hy-10{539}{subsection*:1}

Subsection header, with no entry in the contents page. 


\hy-10{541}{subsection:1}

Subsection header, with an entry in the contents page. 


\hy-10{543}{subsubsection*:1}

Subsubsection header, with no entry in the contents page. 


\hy-10{545}{subsubsection:1}

Subsubsection header, with an entry in the contents page. 


\hy-10{547}{tabbing:1}

Tabbing environment: doesn't work properly in RTF.


\hy-10{549}{tableofcontents:0}

Inserts the table of contents at this point.


\hy-10{551}{tabular:2}

Tabular environment: an attempt is made to output something
reasonable in RTF format, although currently only simple
tables will work. The first argument specifies the column formatting.
a pipe symbol (|) denotes a vertical border, one of \hy-7{552}{l, r, c}
signifies a normal column of default width, and \hy-7{553}{p} followed by
a dimension specifies a column of given width. It is recommended that
the \hy-7{554}{p} is used since Tex2RTF cannot deduce a column width in the
same way that LaTeX can.

Horizontal rules are achieved with \hy-13{555}{hline}; two together
signify a double rule.

Use the Tex2RTF \hy-13{556}{row} and \hy-13{557}{ruledrow} commands
for best effect.

For two-column tables that work in WinHelp files, use \hy-13{558}{twocollist} instead.

Example:

\hy-14{559}{\begin{tabular}{|l|p{8.5cm}|}\hline
\row{{\bf A.I.}&{\bf Simulation}}\hline\hline
\row{rules&constraints/methods}
\row{planning&design of experiments}
\row{diagnosis&analysis of results}
\ruledrow{learning&detection of connections}
\end{tabular}
}

This produces:

\hy-14{560}{--------------------------------------------------------------------------------
\hy-8{561}{A.I.}                \hy-8{562}{Simulation}----------------------------------------------------------------------------------------------------------------------------------------------------------------
rules                                   constraints/methods
planning                                                    design of experiments
diagnosis                                                                       analysis of results
learning                                                                                            detection of connections
}


\hy-10{564}{TeX:0}

Outputs the annoying TeX upper and lower case name.


\hy-10{566}{textwidth:1}

Sets the text width (valid for RTF only). This might be used
in conjunction with \hy-13{567}{marginpar}, for example,
to leave space for marginal notes.


\hy-10{569}{thebibliography:1}

An environment for specifying the a bibliography as a series of
\hy-13{570}{bibitem} commands; the preferred method is to use
.bib files and \hy-13{571}{bibliography} instead.


\hy-10{573}{title:1}

Sets the title, to be output when the command \hy-13{574}{maketitle}
is used.


\hy-10{576}{tiny:1}

Prints the argument in a very small font.


\hy-10{578}{today:0}

Outputs today's date.


\hy-10{580}{tt:1}

Outputs the argument in teletype font.


\hy-10{582}{typeout:1}

Outputs the text on the Tex2RTF text window.


\hy-10{584}{twocolitem:2}

Used to specify a row for a two column list, a Tex2RTF
extension to optimize two-column lists for different
file formats.  See \hy-13{585}{twocollist},
\hy-13{586}{twocolitemruled}.


\hy-10{588}{twocolitemruled:2}

Used to specify a ruled row for a two column list, a Tex2RTF
extension to optimize two-column lists for different
file formats.  See \hy-13{589}{twocollist},
\hy-13{590}{twocolitem}.


\hy-10{592}{twocollist:1}

A Tex2RTF environment for specifying a table of two columns, often
used in manuals and help files (for example, for listing commands and
their meanings). The first column should be one line only, and
the second can be an arbitrary number of paragraphs.

The reason that a normal tabular environment cannot be used is that
WinHelp does not allow borders in table cells, so a different method
must be employed if any of the rows are to be ruled. In LaTeX, a table
is used to implement this environment. In RTF, indentation is used instead.

Use this environment in conjunction with \hy-13{593}{twocolitem} and
\hy-13{594}{twocolitemruled}. To set the widths of the first
and second column, use \hy-13{595}{twocolwidtha} and
\hy-13{596}{twocolwidthb}.

Example:

\hy-14{597}{\htmlignore{\begin{twocollist}}
\twocolitemruled{{\bf Command}}{{\bf Description}}
\twocolitem{File}{The file menu is used to select various file-related
operations, such as saving, loading, exporting, importing, saving as
and various other bits and pieces.}
\twocolitem{Edit}{The Edit menu is used for selection, copying, pasting
and various other bits and pieces.}
\end{twocollist}
}

This produces:


\hy-8{598}{Command}\hy-8{599}{Description}
FileThe file menu is used to select various file-related
operations, such as saving, loading, exporting, importing, saving as
and various other bits and pieces.
EditThe Edit menu is used for selection, copying, pasting
and various other bits and pieces.



\hy-10{601}{twocolwidtha:1}

Sets the width of the first column in a two column list to the given
dimension. See also \hy-13{602}{twocollist} and \hy-13{603}{twocolwidthb}.


\hy-10{605}{twocolwidthb:1}

Sets the width of the second column in a two column list to the given
dimension. See also \hy-13{606}{twocollist} and \hy-13{607}{twocolwidtha}.


\hy-10{609}{twocolumn:0}

Sets the number of columns to two. LaTeX and linear RTF only.


\hy-10{611}{underline:1}

Underlines the argument.
  

\hy-10{613}{verbatiminput:1}

Include the given file as if it were within a \hy-13{614}{verbatim}
environment. The command must not be preceded by any whitespace,
and spurious whitespace between elements of the command will also
trip up Tex2RTF.


\hy-10{616}{verbatim:1}

Uses a fixed-width font to format the argument without interpreting
any LaTeX commands.


\hy-10{618}{verb}

The \hy-7{619}{verb} command is like the \hy-13{620}{verbatim} environment,
but for small amounts of text. The syntax is:

\hy-14{621}{\verb<char><text><char>
}

The character \hy-7{622}{char} is used as a delimiter; it may be any character
not ocurring in the following text, except asterisk.

For example, \verb$\thing%^&$ produces \thing%^&.


\hy-10{624}{winhelpignore:1}

Ignores the argument in WinHelp RTF.


\hy-10{626}{winhelponly:1}

Only outputs the argument in WinHelp RTF.


\hy-10{628}{xlpignore:1}

Ignores the argument in XLP mode (wxHelp files).


\hy-10{630}{xlponly:1}

Only outputs the argument in XLP mode (wxHelp files).


\hy-10{644}{Macro not found}

This error indicates that Tex2RTF has not implemented a standard
LaTeX macro, or that a local macro package is being used that
Tex2RTF does not know about. It can cause spurious secondary
errors, such as not recognising the end document command.

You can get round this by defining a macro file (default name \hy-14{645}{tex2rtf.ini})
containing command definitions, such as:

\hy-14{646}{\crazy      [2]{{\bf #2} is crazy but #1 is not}
\something  [0]{}
\julian     [0]{Julian Smart}
}

New commands may be defined in LaTeX files, but custom macro files
will have to be defined when local style files are being used. See
\hy-13{647}{Initialisation file syntax} for further details.

The `Macro not found' error can also be caused by a syntax error such as
an unbalanced brace or passing the wrong number of arguments to a macro,
so look in the vicinity of the reported error for the real cause.


\hy-10{649}{Unresolved references}

References and citations are usually resolved on a second pass of
Tex2RTF. If this doesn't work, then a missing label or bibliographical
entry is to blame.


\hyindex{
"Tex2RTF Manual"
4 5
6 7
12 13
17 18
21 22
26 27
31 32
49 50
51 52
56 57
60 61
64 65
68 69
71 72
111 112
118 119
120 121
129 130
134 135
138 139
142 143
154 155
163 164
170 171
173 174
176 177
183 184
187 188
192 193
198 199
200 201
202 203
204 205
207 208
209 210
211 212
216 217
218 219
221 222
225 226
227 228
229 230
231 232
233 234
235 236
237 238
241 242
243 244
245 246
247 248
249 250
251 252
253 254
256 257
259 260
262 263
267 268
269 270
271 272
274 275
276 277
278 279
280 281
284 285
289 290
292 293
295 296
303 304
306 307
308 309
310 311
312 313
314 315
316 317
321 322
324 325
328 329
331 332
333 334
335 336
337 338
340 341
343 344
345 346
348 349
350 351
355 356
360 361
362 363
370 371
372 373
374 375
376 377
378 379
381 382
384 385
386 387
388 389
390 391
392 393
397 398
399 400
403 404
406 407
413 414
415 416
417 418
422 423
424 425
427 428
430 431
434 435
438 439
440 441
442 443
448 449
455 456
457 458
459 460
462 463
464 465
467 468
469 470
473 474
476 477
478 479
480 481
483 484
485 486
489 490
493 494
495 496
497 498
499 500
501 502
503 504
505 506
508 509
518 519
529 530
532 533
534 535
536 537
538 539
540 541
542 543
544 545
546 547
548 549
550 551
563 564
565 566
568 569
572 573
575 576
577 578
579 580
581 582
583 584
587 588
591 592
600 601
604 605
608 609
610 611
612 613
615 616
617 618
623 624
625 626
627 628
629 630
631 632
639 640
641 642
643 644
648 649
650 651
664 665
676 677
678 679
680 681
682 683
684 685
686 687
688 689
690 691
692 693
694 695
8 683
8 683
9 689
9 689
11 693
11 693
19 691
19 691
20 681
20 681
42 52
42 52
43 375
43 375
44 317
44 317
45 322
45 322
46 470
46 470
48 155
48 155
55 468
55 468
114 317
114 317
115 375
115 375
123 219
123 219
131 304
131 304
132 296
132 296
133 470
133 470
137 371
137 371
149 644
149 644
214 569
214 569
215 219
215 219
220 121
220 121
223 275
223 275
224 375
224 375
239 236
239 236
240 130
240 130
255 248
255 248
258 393
258 393
261 356
261 356
265 236
265 236
266 504
266 504
273 356
273 356
282 285
282 285
283 470
283 470
286 281
286 281
287 281
287 281
288 470
288 470
291 293
291 293
294 290
294 290
297 356
297 356
298 260
298 260
299 502
299 502
300 317
300 317
301 470
301 470
305 296
305 296
318 322
318 322
323 317
323 317
326 551
326 551
327 490
327 490
339 336
339 336
342 338
342 338
352 356
352 356
354 361
354 361
357 351
357 351
358 260
358 260
359 272
359 272
380 377
380 377
383 379
383 379
394 573
394 573
395 205
395 205
396 257
396 257
401 407
401 407
402 404
402 404
405 407
405 407
411 566
411 566
412 398
412 398
421 644
421 644
426 244
426 244
429 463
429 463
433 435
433 435
437 431
437 431
446 519
446 519
447 509
447 509
461 293
461 293
466 468
466 468
471 322
471 322
472 296
472 296
475 363
475 363
482 375
482 375
487 551
487 551
488 490
488 490
491 551
491 551
492 486
492 486
507 504
507 504
517 519
517 519
526 443
526 443
528 509
528 509
531 244
531 244
555 325
555 325
556 486
556 486
557 490
557 490
558 592
558 592
567 400
567 400
570 212
570 212
571 219
571 219
574 393
574 393
585 592
585 592
586 588
586 588
589 592
589 592
590 584
590 584
593 584
593 584
594 588
594 588
595 601
595 601
596 605
596 605
602 592
602 592
603 605
603 605
606 592
606 592
607 601
607 601
614 616
614 616
620 616
620 616
647 155
647 155
8 683
8 683
9 689
9 689
11 693
11 693
19 691
19 691
20 681
20 681
42 52
42 52
43 375
43 375
44 317
44 317
45 322
45 322
46 470
46 470
48 155
48 155
55 468
55 468
114 317
114 317
115 375
115 375
123 219
123 219
131 304
131 304
132 296
132 296
133 470
133 470
137 371
137 371
149 644
149 644
214 569
214 569
215 219
215 219
220 121
220 121
223 275
223 275
224 375
224 375
239 236
239 236
240 130
240 130
255 248
255 248
258 393
258 393
261 356
261 356
265 236
265 236
266 504
266 504
273 356
273 356
282 285
282 285
283 470
283 470
286 281
286 281
287 281
287 281
288 470
288 470
291 293
291 293
294 290
294 290
297 356
297 356
298 260
298 260
299 502
299 502
300 317
300 317
301 470
301 470
305 296
305 296
318 322
318 322
323 317
323 317
326 551
326 551
327 490
327 490
339 336
339 336
342 338
342 338
352 356
352 356
354 361
354 361
357 351
357 351
358 260
358 260
359 272
359 272
380 377
380 377
383 379
383 379
394 573
394 573
395 205
395 205
396 257
396 257
401 407
401 407
402 404
402 404
405 407
405 407
411 566
411 566
412 398
412 398
421 644
421 644
426 244
426 244
429 463
429 463
433 435
433 435
437 431
437 431
446 519
446 519
447 509
447 509
461 293
461 293
466 468
466 468
471 322
471 322
472 296
472 296
475 363
475 363
482 375
482 375
487 551
487 551
488 490
488 490
491 551
491 551
492 486
492 486
507 504
507 504
517 519
517 519
526 443
526 443
528 509
528 509
531 244
531 244
555 325
555 325
556 486
556 486
557 490
557 490
558 592
558 592
567 400
567 400
570 212
570 212
571 219
571 219
574 393
574 393
585 592
585 592
586 588
586 588
589 592
589 592
590 584
590 584
593 584
593 584
594 588
594 588
595 601
595 601
596 605
596 605
602 592
602 592
603 605
603 605
606 592
606 592
607 601
607 601
614 616
614 616
620 616
620 616
647 155
647 155
}
