<!–Converted with LaTeX2HTML 2022 (Released January 1, 2022) –> <HTML lang="en"> <HEAD> <TITLE>Contents of Bugs</TITLE>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"> <META NAME="viewport" CONTENT="width=device-width, initial-scale=1.0"> <META NAME="Generator" CONTENT="LaTeX2HTML v2022">
<LINK REL="STYLESHEET" HREF="TEX2RTF.css">
<LINK REL="next" HREF="node192_mn.html"> <LINK REL="previous" HREF="node190_mn.html"> <LINK REL="up" HREF="node190_mn.html"> <LINK REL="next" HREF="node192_mn.html"> </HEAD>
<BODY bgcolor="#ffffff" text="#000000" link="#9944EE" vlink="#0000ff" alink="#00ff00">
<H1><A ID="SECTION00910000000000000000"> Bugs</A> </H1>
<P> <DL> <DT><STRONG>Command parsing.</STRONG></DT> <DD>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. </DD> <DT><STRONG>Setlength.</STRONG></DT> <DD>Using the <!– MATH \ –> \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. <code></code> instead of <code> </code>. </DD> <DT><STRONG>Newcommand bug.</STRONG></DT> <DD>Environments in a command definition confuse Tex2RTF. Use the command form instead (e.g. <!– MATH \ –> \flushleft... instead of <!– MATH \ –> \beginflushleft ... <!– MATH \ –> \endflushleft. </DD> <DT><STRONG>Bibliography.</STRONG></DT> <DD>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! </DD> <DT><STRONG>Tables.</STRONG></DT> <DD>Tables can't handle all L<SUP><SMALL>A</SMALL></SUP>T<SMALL>E</SMALL>X syntax, and require the Tex2RTF <code></code> commands for decent formatting. Still, it's better than it was (RTF only). </DD> <DT><STRONG>Indexes and glossaries.</STRONG></DT> <DD>Not completely supported. </DD> <DT><STRONG>Crashes.</STRONG></DT> <DD>Crashes may be due to an input file exceeding the fixed-size buffer used for converting command arguments, especially for the <I>verbatim</I> command. Use the <B>-bufsize</B> switch to increase the buffer size. </DD> <DT><STRONG>Verbatiminput.</STRONG></DT> <DD>Verbatiminput files which do not end with a blank line can trip up following commands. </DD> </DL>
<P>
<HR>
</BODY> </HTML>