<!–Converted with LaTeX2HTML 2022 (Released January 1, 2022) –> <HTML lang="en"> <HEAD> <TITLE>Contents of Macro not found</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="node194_mn.html"> <LINK REL="previous" HREF="node192_mn.html"> <LINK REL="up" HREF="node192_mn.html"> <LINK REL="next" HREF="node194_mn.html"> </HEAD>
<BODY bgcolor="#ffffff" text="#000000" link="#9944EE" vlink="#0000ff" alink="#00ff00">
<H2><A ID="SECTION00921000000000000000"></A><A ID="macronotfound"></A> <BR> Macro not found </H2>
<P> This error may indicate that Tex2RTF has not implemented a standard <SUP><SMALL>A</SMALL></SUP>T<SMALL>E</SMALL>X 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.
<P> You can get round this by defining a macro file (default name <TT>tex2rtf.ini</TT>) containing command definitions, such as:
<P> <PRE> [2]#2 is crazy but #1 is not [0] [0]Julian Smart </PRE>
<P> New commands may be defined in L<SUP><SMALL>A</SMALL></SUP>T<SMALL>E</SMALL>X files, but custom macro files will have to be defined when local style files are being used. See Initialisation file syntaxinifile for further details.
<P> 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.
<P> Here is one obscure situation that causes this error:
<P> <PRE>
<P> The problem is too many curly brackets. This should be rewritten as:
<P> <PRE>
<P>
<HR>
</BODY> </HTML>