D Changes in release 1.6

In this release Star2HTML has been upgraded to use LATEX2HTML version 2000.2 exclusively (this is also part of the Starlink release). The old compatibility version of LATEX2HTML has been removed as has version 98.2. Tests have shown that the new system is largely compatible with 98.2, so documents updated to work with that should continue to work, however, all documents that used the compatibility version of LATEX2HTML will now need to be updated, so you must follow one of the routes described in the next subsection.

D.1 Incompatibilities with previous documents

Unfortunately changes in LATEX2HTML version 98.2 and 2002.2 mean that several major incompatibilities with previous versions of Star2HTML documents continue.

To correct old documents you and take full advantage of the new facilities you’ll need to modify your documents so that they use the current templates provided. You may also need to slightly modify any media sensitive commands that you have added.

The simplest way to update your document is to change it to use the appropriate new template (e.g. sun.tex) and to use the new version of sst.tex, if appropriate. Another change you must make is to modify any \latexonly{} commands to use the equivalent \latex{} command. Note that \latexonly as an environment (\begin{latexonly} \end{latexonly}) can continue to be used, this is just a change to the command form.

Note that if you are using sst.tex then it must now be included in the document prologue, not in the text. Now if you have not made any other changes to differentiate your on-line and paper documents, then you should be able to convert it.

If you have added customized \providecommands to your document then you will also need to change any commands that look like:

to:

This is especially important if you have any section control commands in the redefinitions (\providecommand and \renewcommand are now dealt with at different stages in the conversion process). In general if your \renewcommand is just a replacement command then you should now use \providecommand.

If your document is very customized and you do not want to change the whole prologue, or the effort seems too great, then try the following sequence of changes:

• Move the %\end{rawtex} line to the end of the “debugging” section (all commands visible in your document now override any that LATEX2HTML may know about in any fashion, i.e. builtins, from style files etc., so must be hidden). Now rename %\end{rawtex} to %end{latexonly} and %\begin{rawtex} to %begin{latexonly}.
• Move your sst.tex definitions into the prologue.
• Change any \renewcommands in htmlonly environments to \providecommands (this includes the SST definitions).
• Change any \latexonly{} commands to \latex{} (leave your latexonly environments as they are).
• Modify the font declaration in the SST definitions to:
      \latex{\newfont{\ssttt}{cmtt10 scaled 1095}}
      \html{\providecommand{\ssttt}{\tt}}

  Removing any other such definitions and adding a command:

      \providecommand{\html}[1]{}

  To the standard part of the prologue.

• An additional space issue means you also need to change:
      \stardoccategory \stardocnumber \\

  to:

      \stardoccategory\ \stardocnumber \\
• And finally add the following definition to the standard part of the prologue.
     \providecommand{\latexhtml}[2]{#1}

If all this doesn’t work then you’ll have to do the conversion properly.