10 Some No-No's
The TeXpider is capable of handling majority of LATEX documents without user interventions. Nevertheless, there are cases when you may have to modify your source to accomodate the TeXpider. Below are a few examples picked up from various sources we tried the TeXpider upon. Most of them came from the AMSLATEX.TEX documentation.
Things may go slightly (or very) wrong if you redefine LATEX commands or enviroments within your document. For example, the AMSLATEX.TEX documentation file redefines the verbatim environment after it has been intercepted by export.sty. This leads to extra spaces at the beginning of all verbatim blocks. The right way (if you really must redefine a standard environment) is to put the redefinition into a style file and load this style before export.sty is loaded.
Do not use math mode to center tables and other non-math materials. This substantially increases the file size of the output since math is rendered into .GIF's. This is another glitch in the AMSLATEX.TEX documentation.
Do not use math symbols within text when it is not necessary. For example, the \P, \S, and \copyright definitions in ``normal'' TEX refer to math characters. In export.sty these were changed to refer to HTML characters. However, the AMSLATEX.TEX file also uses the math \langle and \rangle characters within text. This looks bad; usual less or greater symbols would have looked much nicer.
Ensure that math boxes are large enough to contain all their material. For example, do not use contracts like ``&\!\!=\!\!&'' within an aligned equation. Since the TeXpider will cut off anything that does not fit into the math box, the result of the above expression will be an equal sign deteriorated into a colon.