TeX2page is invoked in much the same way as plain TeX
or LaTeX.1 Recall how
these programs are called: Given a TeX source file
with the relative or full pathname
jobname is the basename of the file
.ext is its extension, you type either
at the operating-system command line. You do not need
to mention the extension
.ext if it is
This creates the output DVI file,
in the working directory.
TeX2page is called analogously. To create the HTML
version of the same file
.ext is optional if it is
jobname.html in the working directory.
To try this out, copy into your working directory the
story.tex provided in all TeX
Call TeX2page on it:
This is TeX2page, Version 20050501 (MzScheme 351, unix) (story.tex) ! Missing \end inserted.  Output written on story.html (1 page).
TeX2page is now done, and the result of its labors
is the HTML file
The log file
contains a copy of the above log, and is useful
if you didn’t or couldn’t keep track of the console
(perhaps because the log was too long).
The log says that
story.tex lacked a
document-ending command such as
and that TeX2page assumed one anyway. Also, only
one HTML page was created, and its name is
story.html. TeX2page could in some cases produce
auxiliary HTML pages in addition to
the main HTML page
for larger documents). The auxiliary HTML pages
are reachable from
by navigation links (section 3.1). As each
auxiliary HTML page is completed, the log will show the
, etc. The
in this log refers to the only HTML file created, viz.,
All this is of course almost exactly analogous to the
way you type
tex story to get
story.tex, with the log going into
This is TeX, Version 3.14159 (Web2C 7.3.1) (format=tex 2002.10.21) 16 NOV 2002 18:29 **story (story.tex ) *\end Output written on story.dvi (1 page, 668 bytes).
The only real difference is
that TeX will not add the missing
\end on its
own, but instead waits for the user to supply it
explicitly from the console.2 Note that the bracketed numbers now refer
to physical pages.
Thus, from one TeX source file, you can get both a printable
.dvi and a
.html document, using the same calling
When TeX encounters a filename
searches for it
in a standard list of
directories, which can be modified by the user via the
f.tex is tried before
f itself is tried. In most modern TeXs, the
search is performed using the
By default, TeX2page will look for files using the same
mechanism as TeX. However, it is possible to supply a
different list of search directories via the environment
It may be useful to have
TIIPINPUTS shadow files from
TEXINPUTS, because the latter are not really
HTML-specific, and can thus be unsuitable for
HTML-minded parsing by TeX2page.
In TeXs without the
TIIPINPUTS is the only way to get TeX2page to
automatically access files outside the working
directory. Note that
TIIPINPUTS should be a
simple list of directory names, colon-separated in Unix
and semicolon-separated in Windows. It cannot use the
enhanced syntax (viz.,
//) that is
typically permitted for
Error recovery in TeX2page is also exactly analogous to TeX, but we will postpone that discussion to section 11.
Like most recent versions of TeX, TeX2page also
supports the standard self-identification
arguments elicit help only if there isn’t an input file
--help.tex) that could match them.
TeX2page called without an argument displays a help message and exits. Unlike TeX, TeX2page will not try to conjure up an input document based purely on console chitchat with an increasingly befuddled user.
In all these cases, the help displayed on the console
is also saved in the specially named log file
(require (lib "tex2page.ss" "tex2page")) (tex2page filename)
You can call the procedure
tex2page several times from the same Scheme
session, on the same file or on different files.
By default, TeX2page generates the output HTML files and other auxiliary files (section A) in the current working directory. You can tell TeX2page to place its output and auxiliary files in a different directory and thus avoid cluttering up your working directory.
The files used for specifying the target directory are:
jobname.hdir in the working directory,
.tex2page.hdir in the working directory, and
.tex2page.hdir in the user’s
The first line of the first of these files that exists
is taken to be the name of the target directory.
If none of the files exists, the current working
directory is the target directory.
For example, if
story.hdir contains the filename
story as its first line, the HTML and aux files are
created in a subdirectory
story of the
The filename may contain the TeX control sequence
\jobname, which expands to the basename of
the TeX document. To always use an auxiliary
subdirectory with the same name as the basename of the
TeX document, have
~/.tex2page.hdir contain the
\jobname” (without quotes).