1I'm pleased to be able to report that Luc's arm is healing nicely.
2Unless otherwise stated, I use “SWP” to
include both Scientific Word and Scientific Notebook.
References to SWP 3.5 are to the unreleased test versions of all systems.
3Note to SWP 2.5 [Mac] users: the Objective Caml compiler is also available
for the Mac. Thus Hevea is available also for that SWP version, but you will
need the (free) Objective Caml compiler and the source distribution of Hevea
plus hevea-sw.zip from here. If you need support for the \today macro you will need to recompile xdate.c and/or xxdate.cpp.
4As with non-Style-Editor documents, Reports are treated like Books, so
sereport.bat refers to book.hva.
5The reason is that we need to parse the filename, and the \FRAME macro does just that. If you look at the
definition of \includegraphics in swp.hva you'll see that it calls \FRAME with
seven dummy arguments and one real one, in single quotes.
6In this connection, I recommend Graphics Workshop for Windows from Image
Alchemy. There is a downloadable full-featured evaluation version available
on the Web at http://www.mindworkshop.com/alchemy/gww.html. Another
possibility is to use Ghostscript (http://www.cs.wisc.edu/~ghost/) and ImageMagick (http://www.wizards.dupont.com/cristy/).
7And only one produced by Hevea: Hacha will not work on an arbitrary
HTML file. The reason is that Hacha uses comments placed in the HTML file by
Hevea.
8This was borne in on me very forcibly when (in the Tutorial) I was fixing
the overline in text problem (see section 19.7). Only when
I read Hevea's original definition of this macrodid I realize that I'd
forgotten that \overline could also occur in
display math, and my re-definition was about to cancel all the display-math
support.
9This explains the -exec %heveadir%\xxdate.exe on the command line of the batch programs.
10The difficulty is not (as you might think) the fact that the argument
appears on the next line. TEX doesn't care about lines at all (except for
the two blank lines which indicate a new paragraph). The problem would be
exactly the same if the macro appeared as \QTP{preface} Preface.
11There is also a Hevea mailing list, which you may want to subscribe
to if you make extensive use of Hevea: it is a low-traffic list; see the
Hevea home page for subscription instructions.
12The QTR macro takes whatever's
given by its argument and converts it to a LaTeX command: so, in this case
\QTR{NoteLeadin} expands into \NoteLeadin. In other words, \QTR takes its argument, puts a backslash in front of it — this
is done by the \csname ... \endcsname construct — and then re-interprets
(expands) the result.
13Note that this is the \QTR macro, which gives
no problems, and not the \QTP macro,
whose difficulties are discussed in section 17.2.
14The original had \textoverline for the
\else part of the definition, which is what
generated the warning.
15If you search for \preface in szabo.tex you won't find it. The reason is that it is formed from the
\QTP macro: you will see the following near
the top of the document:
- \QTP{preface}
- Preface
and the instructions for handling \QTP cause it to form \preface from its
argument.
16It might be a good idea to create a dummy personal configuration file now,
so you don't have to re-configure the TEX-Converter later. To do this,
place a file in Hevea's html and text subdirectories: this
file should contain just the macro \relax.
When you come to add “real” material to the files, delete the \relax.