Contents Up Previous Next


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.
Using the \setlength command doesn't work, since its first argument looks like a command with the wrong number of arguments. Use an alternative form instead, e.g. \parindent 0pt instead of \setlength{parindent}{0pt}.
Newcommand bug.
Environments in a command definition confuse Tex2RTF. Use the command form instead (e.g. \flushleft{...} instead of \begin{flushleft} ... \end{flushleft}.
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!
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).
Indexes and glossaries.
Not completely supported.
Crashes may be due to an input file exceeding the fixed-size buffer used for converting command arguments, especially for the \verbatim command. Use the -bufsize switch to increase the buffer size.
Verbatiminput files which do not end with a blank line can trip up following commands.