MiKTeX is an implementation of TeX and friends for Windows 95 and Windows NT.
The MiKTeX distribution contains the following applications:
http://www.ens.fr/omega, for more information.
Most of the programs that come with MiKTeX are command line oriented, i.e., you will miss a graphical user interface.
MiKTeX does not run under Windows 3.1.
MiKTeX is archived in the
CTAN(1)
directory systems/win32/miktex.
Currently there are three participating CTAN nodes:
ftp.dante.de ftp.tex.ac.uk tug2.cs.umb.edu
Visit the MiKTeX Project Page at http://www.snafu.de/~cschenk/miktex
for information about new releases, patches and so on.
Claus Ekstroem from Denmark has created a discussion list for MiKTeX. To join this list, send an e-mail to miktex-request@dsts.dk which contains the word subscribe as the first line in the message body.
This list is for announcements regarding new versions, bugs, etc. It is a low traffic list (max. 1 message in a week). It's not a discussion list.
To join the list, fill out the form on the MiKTeX Project Page.
The Local Guide (which you are reading right now) concentrates on documenting MiKTeX implementation details.
There are other sources of information available:
doc\miktex\yap.hlp
doc\miktex\running.pdf
doc\latex\help\latex2e.hlp
ps2pk)
9g opens TeX page 9)
MiKTeX is now distributed in the form of four independent self-extracting setup utilities:
ps2pk, see below).
Plain TeX only loads the the standard hyphenation patterns (hyphen.tex),
i.e. it does not consult language.dat.
initexmf.exe
(formerly configure.exe).
--find-lambda-input
--find-latex-input
--find-metafont-input
--find-metapost-input
--find-omega-input
--find-pdflatex-input
--find-pdftex-input
--find-tex-input
--mkpsres
psres.dpr).
--local-root
--report
makepk now invokes ps2pk when a Type 1 outline font is available.
ps2pk converts Type 1 outline fonts into PK files.
This utility is used by makepk.
gif2png converts GIF files into PNG files.
c:\texmf.
This directory receives the files of the MiKTeX distribution.
c:\localtexmf.
Benefits that a local tree provides include the following:
e:,
then it is possible to include e:\texmf in the MiKTeX search path.
You should now inspect the Dvips configuration file. You have to modify it, because it probably doesn't match your printer and paper size. See section Configuring Dvips, for more information.
When you have installed MiKTeX, the TEXMF root directory
(usually c:\texmf) contains the following sub-directories:
bibtex
doc
dvips
fonts
makeindex
metafont
metapost
miktex
omega
pdftex
source
tex
Read A Directory Structure for TeX Files
(c:\texmf\doc\general\tds.dvi) by the TUG Working Group on a
TeX Directory Structure, for more information about the standard
TeX directory hierarchy.
The MiKTeX directory (usually c:\texmf\miktex) is reserved for
implementation dependend files.
It contains five subdirectories:
base
.base (METAFONT base) files.
bin
bin directory).
config
miktex.ini and
the filename databases.
Furthermore, this directory contains the filename databases
texmf*.fndb.
fmt
.fmt (TeX format) files.
mem
.mem (MetaPost Memory) files.
bin directory
All MiKTeX executables are located in the directory
miktex\bin relative to the TEXMF root directory.
afm2tfm.exe
bigtex.exe
tex.exe --mem-max=6000000.
bibtex.exe
bibtex8.exe
ctl3d32.dll
yap.exe.
dvi.dll
yap.exe.
dvicopy.exe
dvips.exe
dvitomp.exe
dvitype.exe
epsffit.exe
extractres.cmd
perl.exe.
fixdlsrps.cmd
perl.exe.
fixfmps.cmd
perl.exe.
fixmacps.cmd
perl.exe.
fixpsditps.cmd
perl.exe.
fixpspps.cmd
perl.exe.
fixscribeps.cmd
perl.exe.
fixtpps.cmd
perl.exe.
fixwfwps.cmd
perl.exe.
fixwpps.cmd
perl.exe.
fixwwps.cmd
perl.exe.
gftodvi.exe
gftopk.exe
gftype.exe
gif2png.exe
hugetex.exe
tex.exe --mem-max=20000000.
includeres.cmd
perl.exe.
inimf.exe
mf.exe --ini.
inimp.exe
mp.exe --ini.
iniomega.exe
omega.exe --ini.
inipdftex.exe
pdftex.exe --ini.
initex.exe
tex.exe --ini.
initexmf.exe
lambda.exe
omega.exe "&lambda".
latex.exe
tex.exe "&latex".
makebase.exe
.base file.
makefmt.exe
.fmt file.
makeindex.exe
makeinfo.exe
http://www.snafu.de/~cschenk/makeinfo for more
information. ]
makemem.exe
.mem file.
makempx.exe
makepk.exe
MakeTeXFMT.exe
makefmt.exe.
MakeTeXPK.exe
makepk.exe.
MakeTeXTFM.exe
maketfm.exe.
maketfm.exe
mf.exe
mfc42.dll
yap.exe.
mft.exe
miktex.dll
mkpsres.exe
mp.exe
mpost.exe
mp.exe
mptotex.exe
msvcrt.dll
odvicopy.exe
dvicopy.exe.
odvips.exe
dvips.exe.
ofm2opl.exe
omega.exe
opl2ofm.exe
ovf2ovp.exe
ovp2ovf.exe
pdflatex.exe
pdftex.exe "&latex".
pdftex.exe
pltotf.exe
png.dll
pooltype.exe
ps2pk.exe
psbook.exe
psmerge.cmd
perl.exe.
psnup.exe
psres.dll
ps2pk.
psresize.exe
psselect.exe
pstops.exe
ps2pk.exe
tangle.exe
tex.exe
texindex.exe
tftopl.exe
tie.exe
ttf2afm.exe
vftovp.exe
virmf.exe
mf.exe.
virmp.exe
mp.exe.
viromega.exe
omega.exe.
virpdftex.exe
pdftex.exe.
virtex.exe
tex.exe.
vptovf.exe
weave.exe
yap.exe
zlib.dll
MiKTeX configuration parameters are stored in two configurarion files:
miktex.ini.
It is located in the directory miktex\config relative to the
installation root directory (usually c:\texmf).
initexmf (see section Personal Configuration Files).
Personal configuration settings override global settings.
A MiKTeX configuration file is divided into several named sections. Each section contains configuration entries for a specific application or feature.
The section [MiKTeX] contains general configuration settings:
Bin Directories
makepk.exe) to
locate other MiKTeX utilities (e.g. mf.exe).
Standard value is %R\miktex\bin.
Trace
notrace
fndb
filesearch
access
The section [TeX] contains TeX-related configuration settings:
Editor
e in the error menu.
Standard value is notepad %f.
You can use the following placeholders:
%f
%h
%l
%m
%t
winedt %f -G(1,%l,0) -S(12,+1,0).
Font Metric Dirs
.tfm (TeX Font
Metric) files.
Standard is .;%R\fonts\tfm//.
Font Metric Temp Dir
.tfm files will be installed.
It must be in the .tfm search domain.
The specifiation may include special character sequences which are
replaced at search-time:
%s
public).
%t
cm).
%R\fonts\tfm\%s\%t.
Admin note: MiKTeX users must have permission
to add files to the specified directory.
Format Dirs
%R\miktex\fmt//.
Input Dirs
.;%R\tex//.
The section [LaTeX] contains LaTeX related configuration settings:
Input Dirs
.;%R\tex\latex//;%R\tex\generic//.
The section [Omega] contains Omega related configuration settings:
Font Metric Dirs
.;%R\fonts\ofm//;%R\fonts\tfm//.
Input Dirs
.;%R\omega//;%R\tex//.
OCP Files
.;%R\omega\ocp//.
The section [Lambda] contains Lambda related configuration settings:
Input Dirs
.;%R\omega\latex//;%R\tex\latex//;%R\omega\generic//;%R\tex\generic//.
The section [pdfTeX] contains pdfTeX related configuration settings:
Input Dirs
.;%R\pdftex//;%R\tex//.
T1 Font Dirs
.;%R\fonts\type1//.
TeX PS Header Dirs
.;%R\pdftex\base//.
TrueType Font Dirs
.;%R\fonts\truetype//
The section [pdfLaTeX] contains pdfLaTeX related configuration
settings:
Input Dirs
.;%R\pdftex//;%R\tex\latex//;%R\tex\generic//.
The section [METAFONT] contains METAFONT related configuration
settings:
Base Dirs
.base (METAFONT Base) files.
Standard value is .;%R\miktex\base//.
Base Temp Dir
Base Dirs.
More than one directory can be specified; MiKTeX picks the first
directory that is writable.
Standard value is %R\miktex\base.
Input Dirs
.;%R\fonts\source//;%R\metafont//.
The section [MetaPost] contains MetaPost related configuration
settings:
Input Dirs
.;%R\metapost//.
Mem Dirs
.;%R\miktex\mem//.
Mem Temp dir
Mem Dirs.
More than one directory can be specified; MiKTeX picks the
first directory that is writable.
Standard value is %R\miktex\mem.
The section [MakeTeXPK] contains configuration settings that are
related to the auto-creation of packed raster fonts.
PK File Name
%f
cmr10).
%d
%f.pk.
PK Temp Dir
%m
%d
%s
public).
%t
cm).
typeface.map.
%R\fonts\pk\%m\%s\%t\dpi%d.
Admin note: All MiKTeX users must have permission
to create files in the specified directory.
The section [ps2pk] contains configuration settings for the
ps2pk utility
PSResPath
%R\miktex\config.
The section [Dvips] contains dvips related configuration
settings:
DVIPSHEADERS
.pfb files).
Standard value is .;%R\dvips//;%R\fonts\type1//.
OVFFONTS
.;%R\fonts\ovf//.
TEXCONFIG
config.ps).
Standard value is .;%R\dvips//.
TEXFONTS
.tfm files.
This should be the same as [TeX]Font Metric Dirs.
TEXINPUTS
.;%R\dvips//.
TEXPKS
.pk files.
The specifiation may include the following placeholders:
%m
%d
%R\fonts\pk\%m//dpi%d.
VFONTS
.vf (Virtual Font) files.
Standard value is .;%R\fonts\vf//.
The section [MakeIndex] contains MakeIndex related configuration
settings:
INDEXSTYLE
.;%R\makeindex//.
The section [BibTeX] contains BibTeX related configuration
settings:
Input Dirs
.;%R\bibtex//.
min_crossrefs
cite_list inclusion.
The section [Magic] contains memory relaed configuration values.
These values are used by TeX, pdfTeX and Omega for the dynamic
allocation of certain data structures.
The following parameters can be changed at run time to extend or reduce
TeX's capacity.
They may have different values in INITEX and in production
versions of TeX.
mem_min
mem array; must be 0 or more;
must be equal to mem_bot in INITEX, otherwise <=mem_bot.
mem_max
mem array; must be strictly
less than 1073741823.
buf_size
\csname and \endcsname; must not exceed 1073741823.
error_line
half_error_line
error_line - 15).
max_print_line
stack_size
max_in_open
font_max
font_mem_size
font_info for all fonts.
param_size
nest_size
max_strings
string_vacancies
pool_size
string_vacancies by the total
length of TeX's own strings, which is currently about 23000.
save_size
trie_size
INITEX than it is in production versions of TeX.
trie_op_size
Like the preceding parameters, the following quantities can be changed
at run time to extend or reduce TeX's capacity.
But if they are changed, it is necessary to rerun the initialization
program INITEX to generate new tables for the
production TeX program.
One can't simply make helter-skelter changes to the following constants,
since certain rather complex initialization
numbers are computed from them.
mem_bot
INITEX;
must not be less than mem_min.
mem_top
INITEX; must be substantially
larger than 0 and not greater than mem_max.
Search paths are used by MiKTeX to find special files (such as TeX input files) within a comprehensive directory hierarchy.
A search path is a list of directory paths, which are
separated by semicolons (;).
In a directory path, the following character seqeuences have a
special meaning:
%R
//
Search paths are processed from left to right.
Assuming that c:\texmf;\\myserver\texmf is the list of TEXMF
root directories, the search path .;%R\tex\latex//;%R\tex\generic//
causes LaTeX to search its input files in the following locations:
.).
c:\texmf\tex\latex and in all directories below it.
\\myserver\texmf\tex\latex and in all
directories below it.
c:\texmf\tex\generic and in all directories below it
\\myserver\texmf\tex\generic and in all
directories below it.
You can use the configuration utility initexmf to test whether
an input file can be found via the current search path.
For example, the command
initexmf --find-latex-input a4.sty
searches for the LaTeX input file a4.sty.
The full pathname is printed if the file was found.
initexmf.exe is the MiKTeX configuration utility.
You use initexmf.exe to
plain.fmt and friends)
MiKTeX allows you to use several TEXMF directory trees.
You define these directories by using the command line switch
--root-directories.
This switch takes as argument a semicolon-separated list
of root directory names:
initexmf --root-directories TEXMF1;TEXMF2;...
The most common use is the incorporation of an existing TEXMF tree. This tree might be located on a CD-ROM or on a remote network drive.
Example: you have installed MiKTeX locally on you workstation and you
know, that your system administrator has exported a comprehensive TEXMF
directory tree.
The local TEXMF tree is rooted at c:\texmf.
The share name of the remote TEXMF tree is \\server\texmf.
You then would start initexmf.exe in this way:
initexmf --root-directories c:\texmf;\\server\texmf
It probably is a good idea to build a complete filename-database once you have defined several TEXMF roots (see section Maintaining the filename database).
When MiKTeX creates new fonts and the like, then it installs the new files
in the so called Local TEXMF Tree.
By default, this is the first tree that was specified after `--root-directories'.
You can override the default by using the option `--local-root'.
For example, the following invocation of initexmf will define
two TEXMF trees of which the second shall be the local one:
initexmf --root-directories c:\texmf;c:\ltexmf --local-root c:\ltexmf
To speed up file search, MiKTeX makes use of a list of known file names. This list is called the filename database (fndb). The fndb is spread over several fndb files, one for each TEXMF root directory.
The fndb file for the first TEXMF tree is called texmf0.fndb.
For the second tree it is called texmf1.fndb.
And so on.
It is strongly recommended that you update the fndb whenever files are added to or removed from one of the TEXMF trees.
You update all fndb files by invoking initexmf.exe with
the command line switch --update-fndb:
initexmf --update-fndb
You can update a certain fndb file by specifying the TEXMF root. For example,
initexmf --update-fndb=c:\texmf
will update the fndb file for the tree rooted at c:\texmf.
The PostScript resource database (PSres) is used by some utilities in order to locate PostScript resources (font outlines/metrics/encodings).
The database is located in the MiKTeX config directory (usually `c:\texmf\config'). The name of the database file is `dpres.dpr'. It is a text file, so you can view it with a text editor (e.g. wordpad).
It is strongly recommended that you update the database whenever PostScript resources (`*.pfb;*.afm;*.enc') are added to or removed from one of the TEXMF trees.
You update the database files by invoking initexmf.exe with
the command line switch --mkpsres:
initexmf --mkpsres
It is possible to add non-MiKTeX font directories to the resource database.
The --mkpsres switch accepts as an optional argument the name of
an external font directory.
You can use several --mkpsres switches with on invocation of
initexmf.
By specifying the command line flag --search, you can cause
initexmf to automatically search your workstation for third party
PS resource files (e.g. Acrobat Reader Fonts):
initexmf --mkpsres --search
Some programs initialize itself by reading parts of the memory from an external file. For the TeX family of programs, such a file is called a Format File.
You create new format files by invoking initexmf with the
command line switch --dump.
This switch takes an optional argument, which is the name of the program
for which a new format file is to be created:
initexmf --dump[=program]
If program is ommited, then all format files will be rebuilt. Otherwise, program must be one of the following names:
tex
plain.fmt which is used by tex.exe.
latex
latex.fmt which is used by
latex.exe.
pdftex
pdftex.fmt which is used by
pdftex.exe.
pdflatex
pdflatex.fmt which is used by
pdflatex.exe.
metafont
plain.base which is used by
mf.exe (METAFONT).
metapost
plain.mem which is used by
mpost.exe (MetaPost).
omega
omega.fmt which is used by
omega.exe.
lambda
lambda.fmt which is used by
lambda.exe.
You can control the loading of hyphenation patterns by modifying the
file language.dat, which is located in the directory
tex\generic\hyphen\local relative to the TEXMF root directory.
As distributed with MiKTeX, language.dat has the following
contents:
% File : language.dat % Purpose : specify which hypenation patterns to load % while running iniTeX english ushyphen.tex %ukenglish ukhyphen.tex german ghyph31.tex %italian ithyph.tex %dutch nehyph2.tex %finnish fihyph.tex %norwegian nohyph.tex %french f8hyph.tex
Lines starting with % are comments.
The only uncommented lines in the example are english ushyphen.tex
and german ghyph31.tex.
That is, only hyphenation patterns for U.S. English and German
will be loaded by TeX.
To load other hyphenation patterns, you have to uncomment the
corresponding lines.
After modifying language.dat, you have to create new LaTeX format files
(see section Making Format Files).
You can cause MiKTeX to read a personal configuration file (in
addition to the global one) by using the command line switch
--personal:
initexmf --personal[=FILENAME]
If specified, FILENAME must be the name of an existing configuration file. If FILENAME is ommitted, then MiKTeX will not use a personal configuration file.
Values read from FILENAME will override those values that were read from the global configuration file.
For example, consider the case that you have some private LaTeX style
files in you home directory (say c:\users\me).
You could write a private configuration file (say miktex.ini) and
place it in your home directory.
The configuration file should look like this:
[LaTeX] Input Dirs=.;c:\users\me//;%R\tex\latex//;%R\tex\generic//
Then you had to announce the configuration file this way:
initexmf --personal=c:\users\me\miktex.ini
Here is a summary of all initexmf.exe command line switches:
--dump
*.fmt *.base *.mem).
--dump=program
*.fmt *.base *.mem)
related to a specific compiler.
program must be one of:
lambda,
latex,
metafont,
metapost,
omega,
pdflatex,
pdftex,
tex.
--find-lambda-input FILE
--find-latex-input FILE
"--find-metafont-input FILE
--find-metapost-input FILE
--find-omega-input FILE
--find-pdflatex-input FILE
--find-pdftex-input FILE
--find-tex-input FILE
--local-root root
--mkpsres
--search (see below).
--mkpsres=`dir'
--personal
-p
--personal=FILENAME
-pFILENAME
--print-only
-n
--report
--root-directories dirlist
-r dirlist
--search
--mkpsres).
--update-fndb
-u
--update-fndb=root
-uroot
--verbose
-v
--version
-V
As distributed with MiKTeX, Dvips is configured as follows:
ljfour (HP
Laserjet 4).
You probably have to change some of theses settings for your site.
To do so, open the Dvips configuration file
c:\texmf\dvips\config\local\config.ps with your favourite text
editor.
The line starting with M specifies the METAFONT mode which Dvips
uses for the generation of new raster fonts.
Enter a suitable mode here.
If you don't know the mode for your output device, then take a
look at metafont\misc\modes.mf.
This file contains an annotated list of METAFONT modes.
The line starting with D specifies the resolution.
Enter a value that matches your printer.
See the Dvips manual, for more information about configuring Dvips.
In this chapter you will find basic information for some of the programs.
The usual way to start TeX is as follows:
tex options firstinputline
firstinputline, if supplied, specifies the first input line. This is usually the name of an input file.
For example, the command
tex hello.tex
causes TeX to produce the DVI file hello.dvi from the input
file hello.tex.
You can specify the input file without the .tex extension:
tex hello
You must specify the .tex extension if the filename contains more
than one dot (.). For example, it does not work to say
tex foo.bar
You have to say
tex foo.bar.tex.
instead.
Please note: you cannot specify file names that contain space characters, even if the file system allows such names.
Besides the common switches (see section Common Command Line Switches), TeX supports these command line switches:
--font-max=n
font_max to n.
font_max is the maximum internal font number;
must not exceed 5000.
initex
tex --ini.
virtex
tex.
latex
tex "&latex".
bigtex
tex --mem-max=6000000.
hugetex
tex --mem-max=20000000.
biglatex
tex "&latex" --mem-max=6000000.
hugelatex
tex "&latex" --mem-max=20000000.
To run LaTeX, you must run TeX (see section How to run TeX) with an
instruction to load the LaTeX format file latex.fmt.
For example, you would type
tex "&latex" mydoc
to process the input file mydoc.tex.
For your convenience, there exists an alias named latex.exe:
latex mydoc
is equivalent to the first example.
The usual way to start pdfTeX is as follows:
pdftex options firstinputline
firstinputline, if supplied, specifies the first input line. This is usually the name of an input file.
For example, the command
pdftex hello.tex
causes pdfTeX to produce the PDF file hello.pdf from the input
file hello.tex.
You can specify the input file without the .tex extension:
pdftex hello
You must specify the .tex extension if the filename contains more
than one dot (.). For example, it does not work to say
pdftex foo.bar
You have to say
pdftex foo.bar.tex.
instead.
Please note: you cannot specify file names that contain space characters, even if the file system allows such names.
Besides the common switches (see section Common Command Line Switches), pdfTeX supports these command line switches:
--font-max=n
font_max to n.
font_max is the maximum internal font number;
must not exceed 5000.
inipdftex
pdftex --ini.
virpdftex
pdftex.
pdflatex
pdftex "&pdflatex".
To run pdfLaTeX, you must run pdfTeX (see section How to run pdfTeX) with an
instruction to load the pdfLaTeX format file pdflatex.fmt.
For example, you would type
pdftex "&pdflatex" mydoc
to process the input file mydoc.tex.
For your convenience, there exists an alias named pdflatex.exe:
pdflatex mydoc
is equivalent to the first example.
The usual way to start Omega is as follows:
omega options firstinputline
firstinputline, if supplied, specifies the first input line. This is usually the name of an input file.
For example, the command
omega hello.tex
causes Omega to produce the DVI file hello.dvi from the input
file hello.tex.
You can specify the input file without the .tex extension:
omega hello
You must specify the .tex extension if the filename contains more
than one dot (.). For example, it does not work to say
omega foo.bar
You have to say
omega foo.bar.tex.
instead.
Please note: you cannot specify file names that contain space characters, even if the file system allows such names.
Omega supports the common switches (see section Common Command Line Switches).
iniomega
omega --ini.
viromega
omega.
lambda
omega "&lambda".
To run Lambda, you must run Omega (see section How to run Omega) with an
instruction to load the Lambda format file lambda.fmt.
For example, you would type
omega "&lambda" mydoc
to process the input file mydoc.tex.
For your convenience, there exists an alias named lambda.exe:
lambda mydoc
is equivalent to the first example.
The following command line switches are commonly supported by TeX, pdfTeX and Omega:
--buf-size=n
buf_size to n.
buf_size is the maximum number of characters simultaneously present in
current lines of open files and in control sequences between
\csname and \endcsname; must not exceed 1073741823.
--c-style-errors
\scrollmode.
--error-line=n
error_line to n.
error_line us the width of context lines on terminal error messages.
--half-error-line=n
half_error_line to n.
half_error_line is the width of first lines of contexts in
terminal error messages;
should be between 30 and (error_line - 15).
--initialize
\dumped
to a format file.
--help
--max-in-open=n
max_in_open to n.
max_in_open is the maximum number of input files and error insertions
that can be going on simultaneously.
--max-print-line=n
max-print-line to n.
max-print-line is the width of longest text lines output;
should be at least 60.
--max-strings=n
max_strings to n.
max_strings is the maximum number of strings;
must not exceed 1073741823.
--mem-bot=n
mem_bot to n.
mem_bot is the smallest index in the code array dumped by
INITEX (INIOMEGA, INIPDFTEX);
must not be less than mem_min.
--mem-max=n
mem_max to n.
mem_max is the greatest index in the internal mem array;
must be strictly less than 1073741823.
--mem-min=n
mem_min to n.
mem_min is the smallest index in the internal mem array;
must be 0 or more; must be equal to mem_bot in
INITEX (INIOMEGA, INIPDFTEX),
otherwise <= mem_bot.
--mem-top=n
mem_top to n.
mem_top is the largest index in the mem array dumped by
INITEX (INIOMEGA, INIPDFTEX); must be substantially
larger than 0 and not greater than mem_max.
--nest-size=n
nest_size to n.
nest_size is the maximum number of semantic levels
simultaneously active.
--param-size=n
param_size to n.
param_size is the maximum number of simultaneous macro parameters.
--pool-size=n
pool-size to n.
pool_size is the maximum number of characters in strings, including all
error messages and help texts, and the names of all fonts and
control sequences; must exceed string_vacancies by the total
length of the program's own strings, which is currently about 30000.
--save-size=n
save_size to n.
save_size is the amount of space for saving values outside
of current group; must be at most 1073741823.
--stack-size=n
stack_size to n.
stack_size is the maximum number of simultaneous input sources.
--string-vacancies=n
string_vacancies to n.
string_vacancies is the minimum number of characters that should be
available for the user's control sequences and font names,
after the program's own error messages are stored.
--trie-size=n
trie_size to n.
trie_size is the amount of space for hyphenation patterns;
should be larger for INITEX (INIOMEGA, INIPDFTEX) than it
is in production versions of the program.
--trie-op-size=n
trie_op_size to n.
trie_op_size is the amount of space for "opcodes" in the
hyphenation patterns.
--version
The general command line syntax is
mp [OPTION...] [filename]
--initialize
--help
--tex=texprogram
tex when compiling text labels.
This flag overrides the environment variable TEX.
--version
The following aliases are available
mpost
mp.
virmp
mp.
inimp
mp --ini.
[ This following paragraph is borrowed from the dvips manual. ]
The program dvips takes a DVI file produced by TeX (or by some other
processor such as GFtoDVI) and converts it to PostScript, normally
sending the result directly to the laserprinter. The DVI file may be
specified without the .dvi extension. Fonts used may either be
resident in the printer or defined as bitmaps in PK files, or a
`virtual' combination of both. dvips will automatically invoke METAFONT
to generate fonts that don't already exist.
For more information, see the manual dvips.dvi in the
doc\dvips directory.
[ This section is borrowed from the dvips manual. ]
The usual way to start dvips is as follows
dvips options dvifile
dvifile may be specified without the .dvi extension.
-a
.dvi file instead
of two and only loading those characters actually used. Generally only
useful on machines with a very limited amount of memory, like some PCs.
-A
-b num
-B
-c num
-C option below.)
-C num
-c option, but easier on the
hands, and faster than resubmitting the same PostScript file multiple
times.
-D num
-Z flag should probably also be used.
-e num
-E
-f
.dvi file from standard input and write the PostScript
to standard output. The standard input must be seekable, so it cannot
be a pipe. If you must use a pipe, write a shell script that copies the
pipe output to a temporary file and then points dvips at this file.
This option also disables the automatic reading of the PRINTER
environment variable, and turns off the automatic sending of control D
if it was turned on with the -F option or in the configuration
file; use -F after this option if you want both.
-h name
- suppress all header files from the output.)
This header file gets added to the PostScript `userdict'.
-i
-S option which sets the maximum section
length in pages. For instance, some phototypesetters cannot print more
than ten or so consecutive pages before running out of steam; these
options can be used to automatically split a book into ten-page
sections, each to its own file.
-k
-T
option) by a half inch in each dimension. It translates each page by a
quarter inch and draws cross-style crop marks. It is mostly useful with
typesetters that can set the page size automatically.
-K
%%Page comments, when left in, often cause difficulties. Use
of this flag can cause some included graphics to fail, since the
PostScript header macros from some software packages read portions of
the input stream line by line, searching for a particular comment. This
option has been turned off by default because PostScript previewers and
spoolers have been getting better.
-l num
-p option) is
treated as a sequence number, rather than a value to compare with
char92 count0 values. Thus, using -l =9 will end
with the ninth page of the document, no matter what the pages are
actually numbered.
-m
-M
missfont.log
in the current directory; this file can then be
executed and deleted to create the missing fonts.
-n num
-N
-o name
file.ps where the .dvi file was called
file.dvi; if this option isn't given, any default in the
configuration file is used. If the first character of the supplied
output file name is an exclamation mark, then the remainder will be used
as an argument to popen; thus, specifying !lpr as the
output file will automatically queue the file for printing. This option
also disables the automatic reading of the PRINTER environment
variable, and turns off the automatic sending of control D if it was
turned on with the -F option or in the configuration file; use
-F after this option if you want both.
-O offset
.1in,-.3cm (in the
same syntax used in the papersize special). The origin of the
page is shifted from the default position (of one inch down, one inch to
the right from the upper left corner of the paper) by this amount.
-p num
-l option) is
treated as a sequence number, rather than a value to compare with
char92 count0 values. Thus, using -p =3 will start
with the third page of the document, no matter what the pages are
actually numbered.
-pp pagelist
-pp options may be
specified or all pages and page ranges can be specified with one
-pp option.
-P printername
config.printername, which can then set the output pipe
(as in, !lpr -Pprintername as well as the font paths and any
other config.ps defaults for that printer only. Note that
config.ps is read before config.printername In addition,
another file called ~/.dvipsrc is searched for immediately after
config.ps; this file is intended for user defaults. If no
-P command is given, the environment variable PRINTER is
checked. If that variable exists, and a corresponding configuration
file exists, that configuration file is read in.
-q
-r
-s
-S num
-i
option; see that documentation above for more information.
-t papertype
letter,
legal, ledger, a4, a3). You can also specify
-t landscape, which rotates a document by 90 degrees. To rotate
a document whose size is not letter, you can use the -t option
twice, once for the page size, and once for landscape. The upper left
corner of each page in the .dvi file is placed one inch from the
left and one inch from the top. Use of this option is highly dependent
on the configuration file. Note that executing the letter or
a4 or other PostScript operators cause the document to be
nonconforming and can cause it not to print on certain printers, so the
paper size should not execute such an operator if at all possible.
-T offset
-O.
It overrides any paper size special in the dvi file.
-U
-x num
.dvi file.
Must be between 10 and 100000.
-X num
-Y num
-Z
MakeIndex is a program for making an index in a document generated with
LaTeX.
See doc\makeindex\makeindex.dvi for more information.
[ This section is borrowed from the MakeIndex manual. ]
The usual way to invoke MakeIndex is as follows:
makeindex options [idx0 idx1 idx2...]
-c
-g
-i
-o is
not, output is written to stdout.
-l
-o ind
.ind
to the base name of the first input file (idx0).
-p num
any
odd
even
.log to the base name of the first input file (idx0).
-q
-r
-s sty
INDEXSTYLE defines the path where the style file should
be found.
-t log
.ilg to the base name of the first
input file (idx0).
You use BibTeX in conjunction with LaTeX to compose
bibliographies. MiKTeX comes with two BibTeX implementations: an
`traditional' BibTeX 0.99c implementation called bibtex.exe
and an 8-bit-enhanced implementation called bibtex8.exe. I
recommend using the enhanced version since it has a larger processing
capacity.
Documentation for the enhanced BibTeX is in c:\texmf\doc\bibtex8.
The usual way to start the traditional BibTeX is as follows:
bibtex inputfilename
inputfilename must be specified without the extension.
.bst (BibTeX style files) are located in the directory
c:\texmf\bibtex\bst.
.bib (BibTeX databases) are located in the directory
c:\texmf\bibtex\bib.
YAP is a DVI previewer, i.e. it allows you to view your TeXed documents before you send them to the printer.
The usual way to start YAP is as follows:
yap document.dvi
This opens the file document.dvi and displays its first
page.
See the YAP User's Manual (`yap.dvi') for more information.
CTAN: Comprehensive TeX Archive Network
This document was generated on 16 August 1998 using the texi2html translator version 1.51a.