Here are the conventions you need to observe to satisfy the Tex2RTF parser.
Space
Command arguments
Avoid the setlength command
Units
Labels
Tables
Within a paragraph, you need to be careful about commands \rtfsp{\it that begin at the start of a line.}As normal with LaTeX, two newlines represents a paragraph break, although \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.
\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 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.
The braces that start command arguments must not be separated from the other arguments by whitespace. For example, the following produces an error:
\image{5cm;0cm} {picture.eps}and should be replaced by
\image{5cm;0cm}{picture.eps}
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 0ptinstead of
\setlength{\parindent}{0pt}