[next part][previous part][end][TOC]
I’ll be glad to try to help you debug the installation, if you can’t get it to work. Here’s what you need to do. Please do not run this using the TeXConverter: it must be done in a DOS session.
where xxx is the full command you ran in step 3. Aside from the TrueTeX compiler running you should not see any output. If you get a message saying The VDM redirector is already loaded then repeat the command including the full path to redir (eg c:\mydir\redir -o viton.txt -eo xxx).
This creates the file viton.txt which contains (most of) the output generated by Tex4ht and its helper applications.
At this point, take a look at viton.txt: you may be able to spot the error and fix it for yourself (for example, the Out of Environment Space problem under Win 95/98 is something you can easily fix). Otherwise, make a zip archive of all the files in this directory, and send it to me, together with a brief description of what’s going wrong.
Some common problems are relatively easily solved on their own: here are some tips.
If ImageMagick crashes, or doesn’t make the Gif images correctly, check that you’re using the right version of the transparent / transparency switch. See section F for a description of the problem and the fix. This should not affect you if you’ve just installed ImageMagick — it applies only to older versions.
There is a problem when SWP graphics are used in a document which loads the Babel package (or at least the francais option of Babel). See the Updates section for October 10, 2001 for solutions.
If you get what looks like unformatted text in your HTML file, then it is overwhelmingly likely that you are explicitly including the swpht package in your source and that you forgot to change the option no to yes. This occurs surprisingly often.
Under Windows 95/98/ME there may be a problem connected with the number of environment variables which need to be set (this will never happen under NT/Win2k/XP). If you see a message from the system to the effect that it is “Out of Environment Space” you will need to run TeX4ht in a DOS session with a larger environment. To increase the environment size in a DOS session:
If the TrueTeX formatter stops in the middle of a run, you need to determine whether the problem is with the underlying document, any TeX4ht configuration files, or with TeX4ht itself.
First, if the error message is
then you are probably using elements from myconfig.cfx without having specified the option html. If that doesn’t work try option fonts.
Otherwise, try the following:
SWP3 introduced the Times option — the ability to have both text and mathematics rendered in Times Roman fonts. From a TeX4ht perspective, this part of the SWP implementation is the least robust part. Do you really need the Times option at all for your HTML? Your main document font (in HTML) is typically governed by the way the user’s browser is set up; and as often as not this will be Times. In other words, your readers will like as not see your document in Times no matter what you do. The only advantage to retaining the Times option when you generate HTML is that the symbols come out using Times-like fonts — but on-screen there’s very little difference between Times and Computer Modern.
Note that any problems with the Times option should lead to bad HTML — wrong or missing glyphs — and not to LaTeX errors. If things start to go wrong with the Times option enabled, the first thing to do is to disable it — comment out the relevant \usepackage statement. Just remember to un-comment it before you do any more typesetting.
This section explains what you need to change if you upgrade any parts of the system. Again, it is mostly automated.
Earlier versions of Tex4ht/SWP included an elaborate upgrade facility; but this was becoming very complicated, and I’m no longer supporting it. In general, the preferred way to upgrade TeX4ht when you upgrade SWP is to re-install from scratch. Since you’ll have GhostScript and ImageMagick already in place, this should be a fairly painless process. You will need to re-retrieve swp-ht.zip from my website, plus the files from Eitan Gurari’s website; but that’s straightforward. Then proceed as in section 7.
There is one setting, though, in which this is not necessary. If the new SWP system overwrites the old one (for example, you have SWP40 and SWP41 is released, meant to be installed in place of 40), then there’s no need to do anything. Upgrading SWP generally requires you to uninstall your old SWP system; but when this is done, your TeX4ht files will still be in place: just do not manually delete any folders left in place by the SWP uninstll procedure. When you install the new SWP to the same directory, TeX4ht will still be there.
Eitan Gurari distributes two kinds of upgrade files: newt4ht.zip containing upgrades to the LaTeX interface (*.4ht files, and possibly tex4ht.sty), and possibly upgraded executables; and htf.zip containing upgrades to the hypertext fonts. You will rarely need to upgrade the hypertext fonts; nevertheless, either or both may be processed as follows:
If you upgrade ImageMagick and you over-write the existing files, there’s nothing to do. Otherwise, follow the instructions for upgrading GhostScript, below.
New GhostScript versions typically get installed in new directories, so you will need to re-make all the batch files as well as tex4htx.env, the TeX4ht control file. The distribution now includes a utility, updateprog.bat, which will allow you to do this fairly painlessly. This program will update exactly one string in all these files. This means that if you upgrade both GhostScript and ImageMagick (say) at the same time, you will need to run it twice, once for each change.
To perform an upgrade:
upgradeprog has its own HTML file, which you can read for more information.