You can choose between two ways to do the installation of the required tools: either go the convenient way and install binary distributions (no compilation required, just install out of the box), or get and compile a source code distribution. You will stick to the latter in case you have a special kind of operating system or want to make customisations prior to compilation such as applying source level patches. Windows users will probably want to read the section about installation on Windows.
In case you find one of the URLs below broken, use the search engine on the TUG home page http://ctan.tug.org/ctan/ in order to locate the tool. Other Web-searching facilities such as Altavista or FTP search will also do the job.
For the best use of LATEX2HTML you want to get the latest
versions of all the utilities that it uses. (It will still work
with earlier versions, but some special effects may not be possible.
The specific requirements are discussed below.)
perl -v
);
More specific requirements for using LATEX2HTML
depend on the kind of translation you would like to perform, as follows:
Warning 1: You really do need Perl 5.
Versions of LATEX2HTML up to V96.1h work
both with Perl 4 at patch level 36 and Perl 5,
though some of the packages may only work with Perl 5.
Warning 2: Various aspects of Perl, which are used by LATEX2HTML, assume
certain system commands to be provided by the operating system shell.
If csh or tcsh is used to invoke LATEX2HTML
then everything should work properly.
Perl 5 eliminates this requirement on the shell.
Note: Some systems lack any DBM support. Perl 5 comes with its own database system SDBM, but it is sometimes not part of some Perl distributions.
The installation script install-test will check that for you. If no database system is found, you will have to install Perl properly.
Several of the filters in those libraries are used during the PostScript to GIF conversion.
If Ghostscript or the netpbm library are not available, it is still possible to use the translator with the -no_images option.
If you intend to use any of the special features of the translator then you have to include the html.sty file in any LATEX documents that use them.
Since by default the translator makes use of inlined images in the final HTML output, it would be better to have a viewer which supports the <IMG> tag, such as NCSA Mosaicor Netscape Navigator. Any browser which claims to be compatible with HTML 3.2 should meet this requirement.
If only a character-based browser, such as lynx, is available, or if you want the generated documents to be more portable, then the translator can be used with the -ascii_mode option.