• Troubleshooting

 
Here are some of the problems that were known to exist with previous versions of L^ATEX2HTML. Most of those that were real errors are either fixed completely in the current version (V97.1), or are much less likely to occur within correct L^ATEX source. (Some are not really errors but indications of poor style in the user's choices among various ways to organise their source code.)
Several are indeed limitations inherent in the way L^ATEX2HTML currently performs its processing.

Correctness and Efficiency: 

The translator cannot be guaranteed to perform as expected. Several aspects of the implementation need optimisation and improvement. Apart from possible bugs the translator may place heavy demands on your resources.
^97.1
The current version works much more efficiently than previous versions; many subtle bugs have been identified and eliminated.
^97.1

Unrecognised Commands and Environments: 

Unrecognised commands are ignored and any arguments are left in the text. Unrecognised environments are passed to L^ATEX and the result is included in the document as one or more inlined images.
^97.1
There are very few standard L^ATEX commands that are not recognised. Many common TEX commands are recognised also, even though not explicitly mentioned in the L^ATEX blue book. Any aberrant commands should be reported to the L^ATEX2HTML mailing list.
^97.1

Cross-references: 

References in environments that are passed to L^ATEX for processing (e.g. a \cite, or a \ref command), are not processed correctly. \label commands are handled correctly.
^97.1
All citation, reference and label commands should work correctly now. Report any problems to the L^ATEX2HTML mailing list.
^97.1

Order-Sensitive Commands:

Commands which affect global parameters during the translation, and are sensitive to the order in which they are processed may not be handled correctly. In particular, counter manipulation (e.g. \newcounter, \setcounter, \stepcounter, etc.) commands may cause problems.
^97.1
Counter commands now work correctly; dependencies are also implemented.
^97.1

 

Index:

The translator generates its own index by saving the arguments of the \index command. The contents of the theindex environment are ignored.
^97.1
This remains true. When using the makeidx package, very sophisticated Indexes can be built automatically. The Index for this manual is a good example.
^97.1

New Definitions: 

New definitions (\newcommand, \newenvironment, \newtheorem and \def), will not work as expected if they are defined more than once. Only the last definition will be used throughout the document.
^97.1
This remains true. Stylistically it is bad to declare new environments or theorems outside of the document preamble, so these should cause no problems anyway.
Changes to commands using \def or \renewcommand should usually be made only locally, within special environments, to set a needed parameter; e.g. a basic length in a picture environment. But when such environments force an image to be generated, then L^ATEX will make the correct redefinition.
^97.1

Scope of declarations and environments:

If the scope of a declaration or environment crosses section boundaries, then the output may not be as expected, because each section is processed independently.
^97.1
This is inherent to the way L^ATEX2HTML does its processing. It will not be fixed until later versions change this strategy; e.g. when L^ATEX2HTML-NG becomes fully integrated.
^97.1

Math-mode font-size changes:

Math-mode font changes made outside the math-mode are not honoured. Thus the two equations in $a_b$ and {\LARGE $a_b$} would come out looking the same. The trick is to write $a_b and $\mbox{\LARGE $a_b$}$.
^97.1
This remains. The work-around is effective.
^97.1