2 Installation

2.1 The home of Windvi

Windvi is part of the fpTeX distribution, which is itself based on teTeX and Web2C.

You will find the whole fpTeX distribution on any CTAN archive, for example:

ftp://ftp.tex.ac.uk/pub/tex/systems/win32/fptex

Beta versions of fpTeX and other tools are available from:

ftp://ftp.ese-metz.fr/pub/tex/win32-beta

If you want to retrieve only the windvi distribution, you should get:

ftp://ftp.tex.ac.uk/pub/tex/systems/win32/fptex/windvi.zip for the standalone released version;

ftp://ftp.ese-metz.fr/pub/tex/win32-beta/windvixx.zip for beta versions, xx being always as high as possible.

Announcements of beta version are made through the fptex mailing-list. Subscriptions can be sent to mailto:majordomo@tug.org. Send a message whose body is 'subscribe fptex' to subscribe. The list address is 'fptex@tug.org'.

2.2 Unpacking

Assuming you have retrieved one of the windvixx.zip files, you will have to unpack it at the <root> of some TDS conformant texmf tree like this one:

• owindvi.exe, windvi.exe, mktex*.exe and gsftopk.exe go to bin/win32
• render.ps (used by gsftopk) goes to texmf/dvips
• texmf.cnf and mktex.cnf go to texmf/web2c.

In order not to overwrite the texmf.cnf and mktex.cnf files of people who are already using Web2C for win32, those files are distributed as texmf.xam and mktex.xam. You must rename them if you don't already have .cnf files.

Next, add <root>\bin\win32 to your PATH. This is done by modifying autoexec.bat under Windows 9x or the Control Panel/System under NT/W2K.

2.3 Configuration

If you have respected the previous layout for the tree, ie the relative position of windvi.exe with respect to the texmf directory, you should not have anything more to configure than update your PATH environment variable.

If you want to use windvi.exe in another context, you may need to set the TEXMFMAIN and / or TEXMFCNF environment variable. TEXMFMAIN must point to the texmf directory and TEXMFCNF to the directory containing texmf.cnf.

2.4 Generation of PK files

The generation of PK files is under control of the kpathsea library through the use of mktexpk.exe. You can choose the destination for generated files — the scheme is explained in detail in the kpathsea documentation.

The main points are:

• any generated file will go in the same texmf tree as the one in which the font source has been found,
• if the source directory is not writable, the directory named by VARTEXFONTS will be used, so you had better set this variable to something meaningful in texmf.cnf
• MT_FEATURES can be set either in mktex.cnf or in your environment to control the naming of generated files: you can add 'dosnames', 'nomode', 'stripsupplier', 'striptypeface', 'fontmaps' and 'varfonts' to the features. Feel free to experiment with them by setting MT_FEATURES in the environment and checking with 'mktexnam cmr10' for the result you want.

2.5 Type1 fonts

In order to use gsftopk.exe to generate PK files for Type1 fonts, you will need to install Ghostscript. Ghostscript is used in the background for computing the bitmaps. See section 5 about Ghostscript installation.

After that, Windvi should be able to generate PK files for your Type1 fonts, providing you have the corresponding vf and tfm files. It is however wise to try mktexnam.exe on some of your fonts ('mktexnam ptmr8r' for example) to check that the fonts will be put at the right place.

2.6 PostScript inclusions

Windvi is able to display some PostScript inclusions, thanks to Ghostscript. What is understood :

• graphics bundle from LaTeX2e,
• psfig inclusions,
• some raw PostScript like the pspicture package.

The bop / eop mechanism is not (yet) supported, so do not expect the draft package to display anything. Also, not all material is processed by Ghostscript, so rotated text will not appear so when displayed.

For performance reasons, the magnifying glass will not render your ps inclusions.

See section 5 about Ghostscript installation.