{
"mode": "info",
"parameter": "web2c",
"section": "",
"url": "https://www.chedong.com/phpMan.php/info/web2c/json",
"generated": "2026-11-15T14:35:17Z",
"sections": {
"File: web2c.info, Node: Top, Next: Introduction, Up: (dir)": {
"content": "",
"subsections": []
},
"Web2c": {
"content": "",
"subsections": []
},
"This document describes how to install and use the programs in the Web2c": {
"content": "implementation of the TeX system, especially for Unix systems. It\ncorresponds to Web2c version 2023, released in February 2022.\n\n* Menu:\n\n* Introduction:: A brief introduction.\n* Installation:: How to compile and install Web2c.\n* Commonalities:: Option syntax, standard options, memory dumps.\n* Three programs:: TeX, Metafont, MetaPost have much in common.\n* TeX:: Typesetting.\n* Metafont:: Typeface design.\n* MetaPost:: Technical illustrations.\n* BibTeX:: Reusable bibliographies.\n* WEB:: Literate programming.\n* DVI utilities:: DVI expansion.\n* Font utilities:: Font format conversion.\n* Legalisms:: Blah blah blah.\n* References:: Books and such.\n* Index:: General index.\n",
"subsections": []
},
"File: web2c.info, Node: Introduction, Next: Installation, Prev: Top, Up: Top": {
"content": "",
"subsections": []
},
"1 Introduction": {
"content": "",
"subsections": []
},
"This manual corresponds to version 2023 of Web2c, released in February": {
"content": "2022.\n\n\"Web2c\" (also spelled Web2C) is the name of a TeX implementation,\noriginally for Unix, but now also running under Windows and other\noperating systems. By \"TeX implementation\", we mean all of the standard\nprograms developed by the Stanford TeX project led by Donald E. Knuth:\nMetafont, DVItype, GFtoDVI, BibTeX, Tangle, etc., as well as TeX itself.",
"subsections": []
},
"Other programs are also included: DVIcopy, written by Peter": {
"content": "",
"subsections": []
},
"Breitenlohner, MetaPost and its utilities (derived from Metafont), by": {
"content": "John Hobby, and many more.\n\nGeneral strategy: Web2c works, as its name implies, by translating\nthe WEB source in which TeX is written into C source code. Its output\nis not self-contained, however; it makes extensive use of many macros\nand functions in a library (the 'web2c/lib' directory in the sources).\nTherefore, it will not work without change on an arbitrary WEB program.\n\nAvailability: All of Web2c is freely available--\"free\" both in the\nsense of no cost (free ice cream) and of having the source code to\nmodify and/or redistribute (free speech). *Note\n(kpathsea)unixtex.ftp::, for the practical details of how to obtain\nWeb2c.\n\nDifferent parts of the Web2c distribution have different licensing\nterms, however, reflecting the different circumstances of their\ncreation; consult each source file for exact details. The main\npractical implication for redistributors of Web2c is that most of the\nexecutables are covered by the GNU General Public License or GNU Lesser",
"subsections": []
},
"General Public License, and therefore anyone who gets a binary": {
"content": "distribution must also be able to get the sources, as explained by the\nterms of the GPL (). The GPL covers the",
"subsections": []
},
"Web2c executables, including 'tex', because the Free Software Foundation": {
"content": "sponsored the initial development of the Kpathsea library that Web2c\nuses. The basic source files from Stanford, however, have their own\ncopyright terms or are in the public domain, and are not covered by the\nGPL.\n\nHistory: Tomas Rokicki originated the TeX-to-C system in 1987,\nworking from the first change files for TeX under Unix, which were done\nprimarily by Howard Trickey and Pavel Curtis. Tim Morgan then took over\ndevelopment and maintenance for a number of years; the name changed to\nWeb-to-C somewhere in there. In 1990, Karl Berry became the maintainer.",
"subsections": []
},
"He made many changes to the original sources, and started using the": {
"content": "shorter name Web2c. In 1997, Olaf Weber took over, and then in 2006,",
"subsections": []
},
"Karl started taking care of it again. No significant development or": {
"content": "changes have been needed for many years, though dozens of other people\nhave contributed in many ways; their names are listed in the 'ChangeLog'\nfiles.\n\nOriginally, Web2c was distributed as its own package, alongside the\noriginal web programs from Stanford and other components. It was also\nthe basis for the teTeX distribution (now discontinued). Around 2004,\nthe packaging focus shifted entirely to the TeX Live distribution\n(), though the same Web2c is at the heart of\nthe release.\n\nOther acknowledgements by Karl: The University of Massachusetts at",
"subsections": []
},
"Boston (particularly Rick Martin and Bob Morris) provided computers and": {
"content": "ftp access to me for many years. Richard Stallman at the Free Software",
"subsections": []
},
"Foundation employed me while I wrote the original path searching library": {
"content": "(for the GNU font utilities). (rms also gave us Emacs, GDB, and GCC,\nwithout which I cannot imagine developing Web2c.) And, of course, TeX\nwould not exist in the first place without Donald E. Knuth.\n\nFurther reading: *Note References::.\n",
"subsections": []
},
"File: web2c.info, Node: Installation, Next: Commonalities, Prev: Introduction, Up: Top": {
"content": "",
"subsections": []
},
"2 Installation": {
"content": "(A copy of this chapter is in the distribution file 'web2c/INSTALL'.)\n\nInstalling Web2c is mostly the same as installing any other",
"subsections": []
},
"Kpathsea-using program. Therefore, for the basic steps involved, see": {
"content": "*note (kpathsea)Installation::. (A copy is in the file\n'kpathsea/INSTALL'.)\n\nOne peculiarity to Web2c is that the source distribution comes in two\nfiles: 'web.tar.gz' and 'web2c.tar.gz'. You must retrieve and unpack\nthem both. (We have two because the former archive contains the very\nlarge and seldom-changing original WEB source files.) *Note\n(kpathsea)unixtex.ftp::.\n\nAnother peculiarity is the MetaPost program. Although it has been\ninstalled previously as 'mp', as of Web2c 7.0 the installed name is now\n'mpost', to avoid conflict with the 'mp' program that does\nprettyprinting. This approach was recommended by the MetaPost author,",
"subsections": []
},
"John Hobby. If you as the TeX administrator wish to make it available": {
"content": "under its shorter name as well, you will have to set up a link or some\nsuch yourself. And of course individual users can do the same.\n\nFor solutions to common installation problems and information on how\nto report a bug, see the file 'kpathsea/BUGS' (*note (kpathsea)Bugs::).\nSee also the Web2c home page, .\n\nPoints worth repeating:\n\n* Before starting the standard compilation and installation you must\ninstall the basic fonts, macros, and other library files. *Note\n(kpathsea)Installation::.\n\n* If you do not wish to use the standard file locations, see *note\n(kpathsea)Changing search paths::.\n\n* Some Web2c features are enabled or disabled at 'configure' time, as\ndescribed in the first section below.\n\n* Menu:\n\n* configure options:: Especially -with and -enable.\n* Compile-time options:: Unusual -D's.\n* Additional targets::\t\tBreaking down the task.\n* Triptrap:: Running the torture tests.\n",
"subsections": []
},
"File: web2c.info, Node: configure options, Next: Compile-time options, Up: Installation": {
"content": "",
"subsections": [
{
"name": "2.1 'configure' options",
"content": ""
}
]
},
"This section gives pointers to descriptions of the '--with' and": {
"content": "'--enable' 'configure' arguments that Web2c accepts. Some are specific\nto Web2c, others are generic to all Kpathsea-using programs.\n\nFor a list of all the options 'configure' accepts, run 'configure\n--help'. The generic options are listed first, and the package-specific\noptions come last.\n\nFor a description of the generic options (which mainly allow you to\nspecify installation directories) and basic 'configure' usage, see *note",
"subsections": []
},
"Running 'configure' scripts: (autoconf)Invoking configure, a copy is in": {
"content": "the file 'kpathsea/CONFIGURE'.\n\n'--disable-dump-share'\nDo not make fmt/base/mem files sharable across different endian\narchitectures. *Note Hardware and memory dumps::.\n\n'--without-maketexmf-default'\n'--without-maketexpk-default'\n'--without-maketextfm-default'\n'--with-maketextex-default'\nEnable or disable the dynamic generation programs. *Note\n(kpathsea)mktex configuration::. The defaults are the inverse of\nthe options, i.e., everything is enabled except 'mktextex'.\n\n'--enable-shared'\nBuild Kpathsea as a shared library. *Note (kpathsea)Shared\nlibrary::.\n\n'--with-editor=CMD'\nChange the default editor invoked by the 'e' interactive command.\n*Note Editor invocation::.\n\n'--with-epsfwin'\n'--with-hp2627win'\n'--with-mftalkwin'\n'--with-nextwin'\n'--with-regiswin'\n'--with-suntoolswin'\n'--with-tektronixwin'\n'--with-unitermwin'\n'--with-x'\n'--with-x-toolkit=KIT'\n'--with-x11win'\n'--with-x11'\nDefine Metafont graphics support; by default, no graphics support\nis enabled. *Note Online Metafont graphics::.\n\n'--x-includes=DIR'\n'--x-libraries=DIR'\nDefine the locations of the X11 include files and libraries; by\ndefault, 'configure' does its best to guess). *Note\n(autoconf)Optional Features::. A copy is in 'kpathsea/CONFIGURE'.\n",
"subsections": []
},
"File: web2c.info, Node: Compile-time options, Next: Additional targets, Prev: configure options, Up: Installation": {
"content": "",
"subsections": [
{
"name": "2.2 Compile-time options",
"content": ""
}
]
},
"In addition to the 'configure' options listed in the previous section,": {
"content": "there are a few things that can be affected at compile-time with C\ndefinitions, rather than with 'configure'. Using any of these is\nunusual.\n\nTo specify extra compiler flags ('-DNAME' in this case), the simplest\nthing to do is:\nmake XCFLAGS=\"CCOPTIONS\"",
"subsections": []
},
"You can also set the 'CFLAGS' environment variable before running": {
"content": "'configure'. *Note (kpathsea)configure environment::.\n\nAnyway, here are the possibilities:\n\n'-DFIXPT'\n'-DNOMFASM'\nUse the original WEB fixed-point routines for Metafont and MetaPost\narithmetic calculations regarding fractions. By default,\nassembly-language routines are used on x86 hardware with GNU C\n(unless 'NOMFASM' is defined), and floating-point routines are\nused otherwise.\n\n'-DIPCDEBUG'\nReport on various interprocess communication activities. *Note IPC\nand TeX: IPC and TeX.\n",
"subsections": []
},
"File: web2c.info, Node: Additional targets, Next: Triptrap, Prev: Compile-time options, Up: Installation": {
"content": "",
"subsections": [
{
"name": "2.3 Additional targets",
"content": ""
}
]
},
"Web2c has several Make targets besides the standard ones. You can": {
"content": "invoke these either in the top level directory of the source\ndistribution (the one containing 'kpathsea/' and 'web2c/'), or in the\n'web2c/' directory.\n\n'c-sources'\nMake only the C files, translated from the Web sources, presumably\nbecause you want to take them to a non-Unix machine.\n\n'formats'\n'install-formats'\nMake or install all the memory dumps (*note Memory dumps::). By\ndefault, the standard plain formats plus 'latex.fmt' are made. You\ncan add other formats by redefining the 'fmts', 'bases', and 'mems'\nvariables. See the top of 'web2c/Makefile' for the possibilities.\n\n'fmts'\n'install-fmts'\nMake or install the TeX '.fmt' files. *Note Initial TeX::.\n\n'bases'\n'install-bases'\n\nMake or install the Metafont '.base' files. *Note Initial\nMetafont::.\n\n'mems'\n'install-mems'\nMake or install the MetaPost '.mem' files. *Note Initial\nMetaPost::.\n\n'triptrap'\n'trip'\n'trap'\n'mptrap'\nTo run the torture tests for TeX, Metafont, and MetaPost\n(respectively). See the next section.\n",
"subsections": []
},
"File: web2c.info, Node: Triptrap, Prev: Additional targets, Up: Installation": {
"content": "",
"subsections": [
{
"name": "2.4 Trip, trap, and mptrap: Torture tests",
"content": ""
}
]
},
"To validate your TeX, Metafont, and MetaPost executables, run 'make": {
"content": "triptrap'. This runs the trip, trap, and mptrap \"torture tests\". See\nthe files 'triptrap/tripman.tex', 'triptrap/trapman.tex', and\n'triptrap/mptrap.readme' for detailed information and background on the\ntests.\n\nThe differences between your executables' behavior and the standard\nvalues will show up on your terminal. The usual differences (these are\nall acceptable) are:\n\n* string usage and table sizes;\n* glue set ratios;\n* 'down4', 'right4', and 'y4' commands in DVItype output;\n* dates and times.\n",
"subsections": []
},
"Any other differences are trouble. The most common culprit in the past": {
"content": "has been compiler bugs, especially when optimizing. *Note TeX or\nMetafont failing: (kpathsea)TeX or Metafont failing.\n\nThe files 'trip.diffs', 'mftrap.diffs', and 'mptrap.diffs' in the\n'triptrap' directory show the standard diffs against the original\noutput. If you diff your diffs against these files, you should come up\nclean. For example\nmake trip >&mytrip.diffs\ndiff triptrap/trip.diffs mytrip.diffs\n\nTo run the tests separately, use the targets 'trip', 'trap', and\n'mptrap'.\n\nTo run simple tests for all the programs as well as the torture\ntests, run 'make check'. You can compare the output to the distributed\nfile 'tests/check.log' if you like.\n",
"subsections": []
},
"File: web2c.info, Node: Commonalities, Next: Three programs, Prev: Installation, Up: Top": {
"content": "",
"subsections": []
},
"3 Commonalities": {
"content": "",
"subsections": []
},
"Many aspects of the TeX system are the same among more than one program,": {
"content": "so we describe those pieces together, here.\n\nAnother kind of commonality is the extensions to TeX that are\navailable across all the engines; *note TeX extensions::.\n\n* Menu:\n\n* Option conventions:: - or -, = or ' ' for values.\n* Common options:: -help -version -verbose, and TeX/MF/MP options.\n* Path searching:: Features of the common path searching library.\n* Output file location:: TEXMFOUTPUT allows output in places other than '.'.\n",
"subsections": []
},
"File: web2c.info, Node: Option conventions, Next: Common options, Up: Commonalities": {
"content": "",
"subsections": [
{
"name": "3.1 Option conventions",
"content": ""
}
]
},
"To provide a clean and consistent behavior, we chose to have all these": {
"content": "programs use the GNU function 'getoptlongonly' to parse command lines.",
"subsections": []
},
"However, we do use in a restricted mode, where all the options have to": {
"content": "come before the rest of the arguments.\n\nAs a result, you can:\n* use '-' or '--' to start an option name;\n\n* use any unambiguous abbreviation for an option name;\n\n* separate option names and values with either '=' or one or more\nspaces;\n\n* use filenames that would otherwise look like options by putting\nthem after an option '--'.\n\nBy convention, non-option arguments, if specified, generally define\nthe name of an input file, as documented for each program.\n\nIf a particular option with a value is given more than once, it is\nthe last value that counts.\n\nFor example, the following command line specifies the options 'foo',\n'bar', and 'verbose'; gives the value 'baz' to the 'abc' option, and the\nvalue 'xyz' to the 'quux' option; and specifies the filename '-myfile-'.\n\n-foo --bar -verb -abc=baz -quux karl --quux xyz -- -myfile-\n",
"subsections": []
},
"File: web2c.info, Node: Common options, Next: Path searching, Prev: Option conventions, Up: Commonalities": {
"content": "",
"subsections": [
{
"name": "3.2 Common options",
"content": ""
}
]
},
"All of these programs accept the standard GNU '--help' and '--version'": {
"content": "options, and several programs accept '--verbose'. Rather than writing\nidentical descriptions for every program, they are described here.\n\n'--help'\nPrint a usage message listing basic usage and all available options\nto standard output, then exit successfully.\n\n'--verbose'\nPrint progress reports to standard output.\n\n'--version'\nPrint the version number to standard output, then exit\nsuccessfully.\n\nTeX, Metafont, and MetaPost have a number of additional options in\ncommon:\n\n'-cnf-line=STR'\nParse STR as if it were a line in the 'texmf.cnf' configuration\nfile, overriding all other settings. *Note (kpathsea)Path\nsearching options::.\n\n'-file-line-error'\n'-no-file-line-error'\nChange (or do not change) the way error messages are printed. The\nalternate style looks like error messages from many compilers and\nis easier to parse for some editors that invoke TeX. This option\nused to be called '-file-line-error-style'.\n\n'-fmt=DUMPNAME'\n'-base=DUMPNAME'\n'-mem=DUMPNAME'\nUse DUMPNAME instead of the program name or a '%&' line to\ndetermine the name of the memory dump file read ('fmt' for TeX,\n'base' for Metafont, 'mem' for MetaPost). *Note Memory dumps::.\nAlso sets the program name to DUMPNAME if no '-progname' option was\ngiven.\n\n'-halt-on-error'\nStop processing and exit when an error occurs, as opposed to the\nnormal process of trying to recover and continue.\n\n'-ini'\nEnable the \"initial\" form of the program (*note Initial and\nvirgin::). This is implicitly set if the program name is 'initex'\nresp. 'inimf'.\n\n'-interaction=STRING'\nSet the interaction mode from the command line. The STRING must be\none of 'batchmode', 'nonstopmode', 'scrollmode', or\n'errorstopmode'.\n\n'-jobname=STRING'\nSet the job name to STRING, instead of deriving it from the name of\nthe input file.\n\n'-kpathsea-debug=NUMBER'\nSet path searching debugging flags according to the bits of NUMBER\n(*note (kpathsea)Debugging::). You can also specify this in\n'KPATHSEADEBUG' environment variable (for all Web2c programs).\n(The command line value overrides.) The most useful value is '-1',\nto get all available output.\n\n'-output-directory=DIRNAME'\nSpecify the directory DIRNAME to which output files are written.\nAlso look for input files in DIRNAME first, before looking along\nthe normal search path. *Note Output file location::.\n\n'-parse-first-line'\n'-no-parse-first-line'\nCheck or disable checking whether the first line of the main input\nfile starts with '%&', and parse it if it does. This line can be\nused specify the format and/or a TCX file.\n\n'-progname=STRING'\nSet program (and memory dump) name to STRING. This may affect the\nsearch paths and other values used (*note (kpathsea)Config\nfiles::). Using this option is equivalent to making a link named\nSTRING to the binary and then invoking the binary under that name.\n*Note Memory dumps::.\n\n'-recorder'\nEnable the filename recorder. This makes the program save a list\nof the opened files into a file with (by default) extension '.fls'.\nFor Aleph, this option is always on, and the file has extension\n'.ofl'.\n\nOrdinarily, the '.fls' file is written to the same location as the\n'.log' file, for example, respecting '-output-directory' if it is\ngiven (*note Output file location::). However, if TeX processing\nis done on the command line (or in response to the '' prompt),\nthe '.fls' might be written to the current directory, or include an\ninteger (the current pid), as in 'texput1234.fls'. You can use\n'-jobname' to explicitly set the basename.\n\n'-translate-file=TCXFILE'\nUse TCXFILE to define which characters are printable and\ntranslations between the internal and external character sets.\nMoreover, TCXFILE can be explicitly declared in the first line of\nthe main input file '%& -translate-file=TCXFILE'. This is the\nrecommended method for portability reasons. *Note TCX files::.\n\n'-8bit'\nThis option specifies that by default all characters should be\nconsidered printable. If '-translate-file' was given as well, then\nthe TCX file may mark characters as non-printable. This is a no-op\nin engines natively supporting Unicode.\n",
"subsections": []
},
"File: web2c.info, Node: Path searching, Next: Output file location, Prev: Common options, Up: Commonalities": {
"content": "",
"subsections": [
{
"name": "3.3 Path searching",
"content": ""
}
]
},
"All of the Web2c programs, including TeX, which do path searching use": {
"content": "the Kpathsea routines to do so. The precise names of the environment\nand configuration file variables which get searched for particular file\nformatted are therefore documented in the Kpathsea manual (*note\n(kpathsea)Supported file formats::). Reading 'texmf.cnf' (*note\n(kpathsea)Config files::), invoking 'mktex...' scripts (*note\n(kpathsea)mktex scripts::), and so on are all handled by Kpathsea.\n\nThe programs which read fonts make use of another Kpathsea feature:\n'texfonts.map', which allows arbitrary aliases for the actual names of\nfont files; for example, 'Times-Roman' for 'ptmr8r.tfm'. The\ndistributed (and installed by default) 'texfonts.map' includes aliases\nfor many widely available PostScript fonts by their PostScript names.\n",
"subsections": []
},
"File: web2c.info, Node: Output file location, Prev: Path searching, Up: Commonalities": {
"content": "",
"subsections": [
{
"name": "3.4 Output file location",
"content": "All the programs generally follow the usual convention for output files."
}
]
},
"Namely, they are placed in the directory current when the program is": {
"content": "run, regardless of any input file location; or, in a few cases, output\nis to standard output.\n\nFor example, if you run 'tex /tmp/foo', for example, the output will\nbe in './foo.dvi' and './foo.log', not '/tmp/foo.dvi' and\n'/tmp/foo.log'.\n\nYou can use the '-output-directory' option to cause all output files\nthat would normally be written in the current directory to be written in\nthe specified directory instead. *Note Common options::.\n\nIf the current directory is not writable, and '-output-directory' is\nnot specified, the main programs (TeX, Metafont, MetaPost, and BibTeX)\nmake an exception: if the config file or environment variable value\n'TEXMFOUTPUT' is set (it is not by default), output files are written to\nthe directory specified.\n\n'TEXMFOUTPUT' is also checked for input files, as TeX often generates\nfiles that need to be subsequently read; for input, no suffixes (such as\n'.tex') are added by default and no exhaustive path searching is done,\nthe input name is simply checked as given.\n",
"subsections": []
},
"File: web2c.info, Node: Three programs, Next: TeX, Prev: Commonalities, Up: Top": {
"content": "",
"subsections": []
},
"4 Three programs: Metafont, MetaPost, and TeX": {
"content": "TeX, Metafont, and MetaPost have a number of features in common.",
"subsections": []
},
"Besides the ones here, command-line options and other commonalities are": {
"content": "described in the previous section.\n\n* Menu:\n\n* Runtime options:: The 'texmf.cnf' configuration file.\n* Initial and virgin:: Making memory dumps vs. production runs.\n* Memory dumps:: .fmt/.base files for fast startup.\n* Editor invocation:: The 'e' response at errors.\n* \\input filenames:: Filename delimiters and Kpathsea expansion.\n",
"subsections": []
},
"File: web2c.info, Node: Runtime options, Next: Initial and virgin, Up: Three programs": {
"content": "",
"subsections": [
{
"name": "4.1 Runtime options",
"content": ""
}
]
},
"Besides the configure- and compile-time options described in the": {
"content": "installation section (*note Installation::), you can control a number of\nparameters in the 'texmf.cnf' runtime file read by Kpathsea (*note\n(kpathsea)Config files::).\n\nThe main purpose of 'texmf.cnf' is to specify search paths, but array\nsizes and other options are also set there. Most are rather obscure.\nHere are a few of the more interesting values:\n\n'mainmemory'\nTotal words of memory available, for TeX, Metafont, and MetaPost.\nMust remake the format file after changing.\n\n'extramembot'\nExtra space for \"large\" TeX data structures (default 0): boxes,\nglue, breakpoints, et al. If you use PiCTeX, you may well want to\nset this.\n\n'expanddepth'\nLimit on recursive expansion calls before TeX aborts (default\n10000). If a TeX program does an unterminated recursive expansion,\nTeX will dutifully expand macros until the system's runtime stack\noverflows, typically with a segmentation fault (SIGSEGV). This\nparameter was introduced to minimize the chance of that unpleasant\n(though not dangerous) crash, instead allowing TeX to quit with a\nmore informative message.\n\nThe crash can still happen, though, if the system has an\nexceptionally small memory allocation for its stack. There is no\nquantitative way to determine the limit, and it does not seem worth\nimplementing system-dependent heuristics to guess at the number,\nsince it's highly improbable that any real TeX code will ever need\nmore than 10000 recursive expansions (it has never happened). For\nthe same reason, using the libsigsegv library\n() does not seem worth the effort.\n\n'texmfcasefoldsearch'\n*Note (kpathsea)Casefolding search::.\n\nIdeally all arrays would be dynamically expanded as necessary, so the\nonly limiting factor would be the amount of swap space available, or\nsome configurable limit much larger than can currently be supported.\n\nUnfortunately, implementing this is extremely difficult, as the fixed\nsize of arrays is assumed in many places throughout the source code.",
"subsections": []
},
"These runtime limits are a practical compromise between the compile-time": {
"content": "limits in previous versions, and truly dynamic arrays. (On the other\nhand, the Web2c BibTeX implementation does do true dynamic reallocation\nof some arrays.)\n\nNowadays there is rarely a reason to modify the values. But if you\ndo wish to modify 'texmf.cnf', in TeX Live the best approach is to put\nyour changes, and only your changes at the top of the TL installation\ntree. That is, if the system 'texmf.cnf' is installed in\n'/some/path/to/texlive/YYYY/texmf-dist/web2c/texmf.cnf' is put your\ncustom settings in '/some/path/to/texlive/YYY/texmf.cnf', where YYYY is\nthe year of installation (if you use that subdirectory; it's the\ndefault). That way, unrelated changes to the system 'texmf.cnf' can\nhappen with normal updates, without affecting your local values.\n",
"subsections": []
},
"File: web2c.info, Node: Initial and virgin, Next: Memory dumps, Prev: Runtime options, Up: Three programs": {
"content": "",
"subsections": [
{
"name": "4.2 Initial and virgin",
"content": ""
}
]
},
"The TeX and Metafont programs each have two main variants, called": {
"content": "\"initial\" and \"virgin\". MetaPost no longer makes this distinction.\n\nThe initial form is enabled if:\n1. the '-ini' option was specified; or\n2. the program name is 'initex' resp. 'inimf'; or\n3. the first line of the main input file is '%&ini';\notherwise, the virgin form is used.\n\nThe \"virgin\" form is the one generally invoked for production use.\nThe first thing it does is read a memory dump (*note Determining the\nmemory dump to use::), and then proceeds on with the main job.\n\nThe \"initial\" form is generally used only to create memory dumps (see\nthe next section). It starts up more slowly than the virgin form,\nbecause it must do lengthy initializations that are encapsulated in the\nmemory dump file.\n",
"subsections": []
},
"File: web2c.info, Node: Memory dumps, Next: Editor invocation, Prev: Initial and virgin, Up: Three programs": {
"content": "",
"subsections": [
{
"name": "4.3 Memory dumps",
"content": ""
}
]
},
"In typical use, TeX and Metafont require a large number of macros to be": {
"content": "predefined; therefore, they support \"memory dump\" files, which can be\nread much more efficiently than ordinary source code.\n\n* Menu:\n\n* Creating memory dumps::\n* Determining the memory dump to use::\n* Hardware and memory dumps::\n",
"subsections": []
},
"File: web2c.info, Node: Creating memory dumps, Next: Determining the memory dump to use, Up: Memory dumps": {
"content": "",
"subsections": []
},
"The programs all create memory dumps in slightly idiosyncratic (thought": {
"content": "substantially similar) way, so we describe the details in separate\nsections (references below). The basic idea is to run the initial\nversion of the program (*note Initial and virgin::), read the source\nfile to define the macros, and then execute the '\\dump' primitive.\n\nAlso, each program uses a different filename extension for its memory\ndumps, since although they are completely analogous they are not\ninterchangeable (TeX cannot read a Metafont memory dump, for example).\n\nHere is a list of filename extensions with references to examples of\ncreating memory dumps:\n",
"subsections": []
},
"TeX": {
"content": "('.fmt') *Note Initial TeX: Initial TeX.\n",
"subsections": []
},
"Metafont": {
"content": "('.base') *Note Initial Metafont::.\n\nWhen making memory dumps, the programs read environment variables and\nconfiguration files for path searching and other values as usual. If\nyou are making a new installation and have environment variables\npointing to an old one, for example, you will probably run into\ndifficulties.\n",
"subsections": []
},
"File: web2c.info, Node: Determining the memory dump to use, Next: Hardware and memory dumps, Prev: Creating memory dumps, Up: Memory dumps": {
"content": "The virgin form (*note Initial and virgin::) of each program always\nreads a memory dump before processing normal source input. All three\nprograms determine the memory dump to use in the same way:\n\n1. If the first non-option command-line argument begins with '&', the\nprogram uses the remainder of that argument as the memory dump\nname. For example, running 'tex \\&super' reads 'super.fmt'. (The\nbackslash protects the '&' against interpretation by the shell.)\n\n2. If the '-fmt' resp. '-base' option is specified, its value is used.\n\n3. If the '-progname' option is specified, its value is used.\n\n4. If the first line of the main input file (which must be specified\non the command line, not in response to '') is '%&DUMP', and DUMP\nis an existing memory dump of the appropriate type, DUMP is used.\n\nThe first line of the main input file can also specify which\ncharacter translation file is to be used:\n'%&-translate-file=TCXFILE' (*note TCX files::).\n\nThese two roles can be combined: '%&DUMP -translate-file=TCXFILE'.\nIf this is done, the name of the dump must be given first.\n\n5. Otherwise, the program uses the program invocation name, most\ncommonly 'tex' resp. 'mf'. For example, if 'latex' is a link to\n'tex', and the user runs 'latex foo', 'latex.fmt' will be used.\n",
"subsections": []
},
"File: web2c.info, Node: Hardware and memory dumps, Prev: Determining the memory dump to use, Up: Memory dumps": {
"content": "",
"subsections": []
},
"By default, memory dump files are sharable between architectures of": {
"content": "different types; specifically, on machines of different endianness\n(*note (libc)Byte order::) and with different word sizes (4-byte 'long'\nvs. 8-byte 'long'). This is a feature of the Web2c implementation, and\nis not true of all TeX implementations.\n\nThe script 'tl-check-fmtshare' in the TeX Live source tree\n('Master/tlpkg/bin') provides a relatively easy way to test that a\n'.fmt' built on the local host can be loaded by a TeX engine built on\nsome remote host.\n\nIf you specify '--disable-dump-share' to 'configure', however, memory\ndumps will be endian-dependent. The reason to do this is speed. To\nachieve endian-independence, the reading of memory dumps on LittleEndian\narchitectures, such as PC's and DEC architectures, is somewhat slowed\n(all the multibyte values have to be swapped). Usually, this is not\nnoticeable, and the advantage of being able to share memory dumps across\nall platforms at a site far outweighs the speed loss. But if you're\ntrying to squeeze out every possible bit of performance, you may wish to\ndo this.\n\nTeXnically, even without '--disable-dump-share', sharing of '.fmt'\nfiles cannot be guaranteed to work. Floating-point values are always\nwritten in native format, and hence will generally not be readable\nacross platforms. Fortunately, TeX uses floating point only to\nrepresent glue ratios, and none of the common formats (plain, LaTeX,\nAMSTeX, ...) do any glue setting at '.fmt'-creation time. Metafont does\nnot use floating point in any dumped value at all.\n\nIncidentally, different memory dump files will never compare equal\nbyte-for-byte, because the programs dump the current date and time. So\ndon't be alarmed by a few bytes difference.\n\nIf you don't know what endianness your machine is, and you're\ncurious, here is a little C program to tell you. (The 'configure'\nscript contains a similar program.) This is from the book 'C: A\nReference Manual', by Samuel P. Harbison and Guy L. Steele Jr. (*note\nReferences::).\n\nmain ()\n{\n/* Are we little or big endian? From Harbison&Steele. */\nunion\n{\nlong l;\nchar c[sizeof (long)];\n} u;\nu.l = 1;\nif (u.c[0] == 1)\nprintf (\"LittleEndian\\n\");\nelse if (u.c[sizeof (long) - 1] == 1)\nprintf (\"BigEndian\\n\");\nelse\nprintf (\"unknownEndian\");\n\nexit (u.c[sizeof (long) - 1] == 1);\n}\n\nYou can add 'printf(\"long %d\\n\", sizeof(long));' to see the size of\nthe 'long' data type.\n\nFile: web2c.info, Node: Editor invocation, Next: \\input filenames, Prev: Memory dumps, Up: Three programs\n",
"subsections": [
{
"name": "4.4 Editor invocation",
"content": ""
}
]
},
"TeX, Metafont, and MetaPost all (by default) stop and ask for user": {
"content": "intervention at an error. If the input came from a file, and the user\nresponds with 'e' or 'E', the program invokes an editor.\n\nSpecifying '--with-editor=CMD' to 'configure' sets the default editor\ncommand string to CMD. The environment variables/configuration values\n'TEXEDIT', 'MFEDIT', and 'MPEDIT' (respectively) override this. If\n'--with-editor' is not specified, the default is 'vi +%d %s' on Unix,\nand an invocation of the TeXworks editor on Windows. (See 'texmf.cnf'\nfor the precise values.)\n\nIn this string, '%d' is replaced by the line number of the error, and\n'%s' is replaced by the name of the current input file.\n\nFile: web2c.info, Node: \\input filenames, Prev: Editor invocation, Up: Three programs\n",
"subsections": [
{
"name": "4.5 '\\input' filenames",
"content": ""
}
]
},
"TeX, Metafont, and MetaPost source programs can all read other source": {
"content": "files with the '\\input' (TeX) and 'input' (MF and MP) primitives:\n\\input NAME % in TeX\n\nThe file NAME can always be terminated with whitespace; for Metafont\nand MetaPost, the statement terminator ';' also works. (LaTeX and other\nmacro packages provide other interfaces to '\\input' that allow different\nnotation; here we are concerned only with the primitive operation.)\n\nAs (allowed) extensions to standard TeX, Web2c also supports\nspecifying the filename in double quotes ('\"some name\"') and in braces\n('{some name}'), which is convenient for filenames containing spaces or\nother special characters, as described in the sections below.\n\nIn all cases, space tokens are ignored after the filename is read.\n\nAlso, double quote ('\"') characters are ignored within the filename;\nthere is no way to read files whose names contain a '\"'.\n\nHowever, for maximal portability of your document across systems, use\nonly the characters 'a'-'z', '0'-'9', and at most one '.'. Do not use\nanything but simple filenames, since directory separators vary among\nsystems; instead, add the necessary directories to the appropriate\nsearch path.\n\n* Menu:\n\n* Quotes: \\input quoted filename. \\input \"some name\"\n* Braces: \\input braced filename. \\input {some name}\n* Caveats: \\input filename caveats. Tokenization, nulls, Kpathsea expansion.\n\nFile: web2c.info, Node: \\input quoted filename, Next: \\input braced filename, Up: \\input filenames\n\n",
"subsections": []
},
"As of Web2c version 7.5.3 (2004), double-quote characters can be used to": {
"content": "include spaces or other special characters. In typical use, the '\"'\ncharacters surround the entire filename:\n\\input \"filename with spaces\"\n\nTechnically, the quote characters can be used inside the name, and\ncan enclose any characters, as in:\n\\input filename\" \"with\" \"spaces\n\nOne more point. In LaTeX, the quotes are needed inside the braces of\nits '\\input' macro, thus:\n\\input{a b} % fails\n\\input{\"a b\"} % ok\n\nThere is no way to quote the quote character.\n\nFile: web2c.info, Node: \\input braced filename, Next: \\input filename caveats, Prev: \\input quoted filename, Up: \\input filenames\n\n\nAs of Web2c 2020, '\\input' filenames in TeX engines (this does not apply\nin Metafont and MetaPost) can also be specified within a TeX group,\ntypically curly braces. For example:\n\\input{filename with spaces}\n\nAs always with TeX, the brace characters are not hardwired; what\ncounts is the category code: the first token after the '\\input' must be\nof catcode 1 (begin group), and it is matched with the next character of\ncatcode 2 (end group).\n\nWithin the group-delimited filename, braces are treated as normal\ncharacters.\n\nAs with all forms of filenames, following spaces are ignored (after\nthe end group), and double quote ('\"') characters are ignored within the\nfilename.\n\nFile: web2c.info, Node: \\input filename caveats, Prev: \\input braced filename, Up: \\input filenames\n\n",
"subsections": []
},
"The quoting mechanisms just described come into play after TeX has": {
"content": "tokenized and expanded the input. So, multiple spaces and tabs will\ngenerally be seen as a single space, active characters such as '~' are\nexpanded first (generally causing an error), and so on. More examples\nbelow.\n\nOn the other hand, various C library routines and Unix itself use the\nnull byte (character code zero, ASCII NUL) to terminate strings. So\nfilenames in Web2c cannot contain nulls, even though TeX itself does not\ntreat NUL specially.\n\nFinally, the present Web2c implementation does '~' and '$' expansion\non NAME, unlike Knuth's original implementation. Thus:\n\\input ~jsmith/$foo.bar\nwill dereference the environment variable or Kpathsea config file\nvalue 'foo' and read that file, extended with '.bar', in user 'jsmith''s\nhome directory. You can also use braces in the variable expansion, as\nin '${foo}bar', if you want to follow the variable name with a letter,\nnumeral, or ''.\n\n(So another way to get a program to read a filename containing\nwhitespace is to define an environment variable and dereference it.)\n\nIn all the common TeX formats (plain TeX, LaTeX, ConTeXt, AMSTeX,\n...), the characters '~' and '$' have special category codes, so to\nactually use these in a document you have to change their catcodes or\nuse '\\string'.\n",
"subsections": []
},
"File: web2c.info, Node: TeX, Next: Metafont, Prev: Three programs, Up: Top": {
"content": "",
"subsections": []
},
"5 TeX: Typesetting": {
"content": "",
"subsections": []
},
"TeX is a typesetting system: it was especially designed to handle": {
"content": "complex mathematics, as well as most ordinary text typesetting.\n\nTeX is a batch language, like C or Pascal, and not an interactive\n\"word processor\": you compile a TeX input file into a corresponding\ndevice-independent (DVI) file (and then translate the DVI file to the\ncommands for a particular output device). This approach has both\nconsiderable disadvantages and considerable advantages. For a complete\ndescription of the TeX language, see 'The TeXbook' (*note References::).\nMany other books on TeX, introductory and otherwise, are available.\n\n* Menu:\n\n* tex invocation:: Invoking TeX.\n* Initial TeX:: Making format files.\n* Formats:: Major TeX macro packages.\n* Languages and hyphenation:: TeX supports many human languages.\n* Shell escapes:: Running subprograms from TeX.\n* IPC and TeX:: DVI output to a socket.\n* TeX extensions:: Additional engines with additional features.\n",
"subsections": []
},
"File: web2c.info, Node: tex invocation, Next: Initial TeX, Up: TeX": {
"content": "",
"subsections": [
{
"name": "5.1 'tex' invocation",
"content": ""
}
]
},
"TeX (usually invoked as 'tex') formats the given text and commands, and": {
"content": "outputs a corresponding device-independent representation of the typeset\ndocument. This section merely describes the options available in the",
"subsections": []
},
"Web2c implementation. For a complete description of the TeX typesetting": {
"content": "language, see 'The TeXbook' (*note References::).\n\nTeX, Metafont, and MetaPost process the command line (described here)\nand determine their memory dump (fmt) file in the same way (*note Memory\ndumps::). Synopses:\n\ntex [OPTION]... [TEXNAME[.tex]] [TEX-COMMANDS]\ntex [OPTION]... \\FIRST-LINE\ntex [OPTION]... &FMT ARGS\n\nTeX searches the usual places for the main input file TEXNAME (*note\n(kpathsea)Supported file formats::), extending TEXNAME with '.tex' if\nnecessary. To see all the relevant paths, set the environment variable\n'KPATHSEADEBUG' to '-1' before running the program.\n\nAfter TEXNAME is read, TeX processes any remaining TEX-COMMANDS on\nthe command line as regular TeX input. Also, if the first non-option\nargument begins with a TeX escape character (usually '\\'), TeX processes\nall non-option command-line arguments as a line of regular TeX input.\n\nIf no arguments or options are specified, TeX prompts for an input\nfile name with ''.\n\nTeX writes the main DVI output to the file 'BASETEXNAME.dvi', where\nBASETEXNAME is the basename of TEXNAME, or 'texput' if no input file was\nspecified. A DVI file is a device-independent binary representation of\nyour TeX document. The idea is that after running TeX, you translate\nthe DVI file using a separate program to the commands for a particular\noutput device, such as a PostScript printer (*note Introduction:\n(dvips)Top.) or an X Window System display (see xdvi(1)).\n\nTeX also reads TFM files for any fonts you load in your document with\nthe '\\font' primitive. By default, it runs an external program named\n'mktextfm' to create any nonexistent TFM files. You can disable this at\nconfigure-time or runtime (*note (kpathsea)mktex configuration::). This\nis enabled mostly for the sake of the EC fonts, which can be generated\nat any size.\n\nTeX can write output files, via the '\\openout' primitive; this opens\na security hole vulnerable to Trojan horse attack: an unwitting user\ncould run a TeX program that overwrites, say, '~/.rhosts'. (MetaPost\nhas a 'write' primitive with similar implications). To alleviate this\nand similar problems the functions 'kpathseaoutnameok' and\n'kpathseainnameok' from the Kpathsea library (*note (kpathsea)Calling\nsequence::) are used to determine if a given filename is acceptable to\nbe opened for output or input, depending on the setting of the\nconfiguration variables 'openoutany' and 'openinany': 'a' (for \"any\",\nthe default for 'openinany'), 'r' (for \"restricted\"), or 'p' (for\n\"paranoid\", the default for 'openoutany').\n\nIn any case, all '\\openout' filenames are recorded in the log file,\nexcept those opened on the first line of input, which is processed when\nthe log file has not yet been opened.\n\nThe program accepts the following options, as well as the standard\n'-help' and '-version' (*note Common options::):\n'-enc'\n'-[no]-file-line-error'\n'-fmt=FMTNAME'\n'-halt-on-error'\n'-ini'\n'-interaction=STRING'\n'-ipc'\n'-ipc-start'\n'-jobname=STRING'\n'-kpathsea-debug=NUMBER'\n'-[no]parse-first-line'\n'-output-directory'\n'-progname=STRING'\n'-recorder'\n'-translate-file=TCXFILE'\n'-8bit'\nThese options are common to TeX, Metafont, and MetaPost. *Note\nCommon options::.\n\n'-enc'\nEnable encTeX extensions, such as '\\mubyte'. This can be used to\nsupport the Unicode UTF-8 input encoding, although using an engine\nwith native Unicode support is more common nowadays.\n.\n\n'-ipc'\n'-ipc-start'\nWith either option, TeX writes its DVI output to a socket as well\nas to the usual '.dvi' file. With '-ipc-start', TeX also opens a\nserver program at the other end to read the output. *Note IPC and\nTeX: IPC and TeX.\n\nThese options are available only if the '--enable-ipc' option was\nspecified to 'configure' during installation of Web2c.\n\n'-mktex=FILETYPE'\n'-no-mktex=FILETYPE'\nTurn on or off the 'mktex' script associated with FILETYPE. For\nTeX proper, FILETYPE can only be 'tex' and 'tfm', but for pdfTeX\nand luaTeX, it can also be 'pk'.\n\n'-mltex'\nIf we are 'INITEX' (*note Initial and virgin::), enable MLTeX\nextensions such as '\\charsubdef'. Implicitly set if the program\nname is 'mltex'. *Note MLTeX: MLTeX.\n\n'-output-comment=STRING'\nUse STRING as the DVI file comment. Ordinarily, this comment\nrecords the date and time of the TeX run, but if you are doing\nregression testing, you may not want the DVI file to have this\nspurious difference. This is also taken from the environment\nvariable and config file value 'outputcomment'.\n\n'-shell-escape'\n'-no-shell-escape'\n'-shell-restricted'\nEnable, or disable, or enable with restrictions the\n'\\write18{SHELL-COMMAND}' feature for external executing shell\ncommands. *Note Shell escapes::.\n\n'-enable-write18'\n'-disable-write18'\nSynonyms for '-shell-escape' and '-no-shell-escape', for\ncompatibility with MiKTeX. (MiKTeX also accepts both pairs of\noptions.) *Note Shell escapes::.\n\n'-src-specials'\n'-src-specials=STRING'\nThis option makes TeX output specific source information using\n'\\special' commands in the DVI file. These '\\special' track the\ncurrent file name and line number.\n\nUsing the first form of this option, the '\\special' commands are\ninserted automatically.\n\nIn the second form of the option, STRING is a comma separated list\nof the following values: 'cr', 'display', 'hbox', 'math', 'par',\n'parend', 'vbox'. You can use this list to specify where you want\nTeX to output such commands. For example, '-src-specials=cr,math'\nwill output source information every line and every math formula.\n\nThese commands can be used with the appropriate DVI viewer and text\neditor to switch from the current position in the editor to the\nsame position in the viewer and back from the viewer to the editor.\n\nThis option works by inserting '\\special' commands into the token\nstream, and thus in principle these additional tokens can be\nrecovered or seen by the tricky-enough macros. If you run across a\ncase, let us know, because this counts as a bug. However, such\nbugs are very hard to fix, requiring significant changes to TeX, so\nplease don't count on it.\n\nRedefining '\\special' will not affect the functioning of this\noption. The commands inserted into the token stream are hard-coded\nto always use the '\\special' primitive.\n\nTeX does not pass the trip test when this option is enabled.\n",
"subsections": []
},
"File: web2c.info, Node: Initial TeX, Next: Formats, Prev: tex invocation, Up: TeX": {
"content": "",
"subsections": [
{
"name": "5.2 Initial TeX",
"content": "The \"initial\" form of TeX is invoked by 'tex -ini'. It does lengthy\ninitializations avoided by the \"virgin\" ('vir') form, so as to be\ncapable of dumping '.fmt' files (*note Memory dumps::). For a detailed\ncomparison of virgin and initial forms, *note Initial and virgin::.\n\nFor a list of options and other information, *note tex invocation::.\n\nUnlike Metafont and MetaPost, many format files are commonly used\nwith TeX. The standard one implementing the features described in the\n'TeXbook' is 'plain.fmt', also known as 'tex.fmt' (again, *note Memory\ndumps::). It is created by default during installation, but you can\nalso do so by hand if necessary (e.g., if an update to 'plain.tex' is\nissued):\ntex -ini '\\input plain \\dump'\n(The quotes prevent interpretation of the backslashes from the shell.)\nThen install the resulting 'plain.fmt' in '$(fmtdir)'\n('/usr/local/share/texmf/web2c' by default), and link 'tex.fmt' to it.\n\nThe necessary invocation for generating a format file differs for\neach format, so instructions that come with the format should explain."
}
]
},
"The top-level 'web2c' Makefile has targets for making most common": {
"content": "formats: plain latex amstex texinfo eplain. *Note Formats::, for more\ndetails on TeX formats.\n",
"subsections": []
},
"File: web2c.info, Node: Formats, Next: Languages and hyphenation, Prev: Initial TeX, Up: TeX": {
"content": "",
"subsections": [
{
"name": "5.3 Formats",
"content": "TeX \"formats\" are large collections of macros, often dumped into a\n'.fmt' file (*note Memory dumps::) by 'tex -ini' (*note Initial TeX::).\nA number of formats are in reasonably widespread use, and the Web2c"
}
]
},
"Makefile has targets to make the versions current at the time of": {
"content": "release. You can change which formats are automatically built by\nsetting the 'fmts' Make variable; by default, only the 'plain' and\n'latex' formats are made.\n\nNowadays, the formats are generally installed and updated as part of\na larger TeX distribution, such as TeX Live ().\n\nlatex\nThe most widely used format. The current release is named\n'LaTeX2e'; new versions are released approximately every six\nmonths, with patches issued as needed. The old release was called\n'LaTeX 2.09', and is no longer maintained or supported. LaTeX\nattempts to provide generic markup instructions, such as\n\"emphasize\", instead of specific typesetting instructions, such as\n\"use the 10pt Computer Modern italic font\". The LaTeX home page:\n.\n\ncontext\nConTeXt is an independent macro package which has a basic document\nstructuring approach similar to LaTeX. It also supports creating\ninteractive PDF files and has integrated MetaPost support, among\nmany other interesting features. The ConTeXt home page:\n.\n\namstex\nThe official typesetting system of the American Mathematical\nSociety. Like LaTeX, it encourages generic markup commands. The\nAMS also provides many LaTeX packages for authors who prefer LaTeX.\nTaken together, they are used to produce nearly all AMS\npublications, e.g., 'Mathematical Reviews'. The AMSTeX home page:\n.\n\ntexinfo\nThe documentation system developed and maintained by the Free\nSoftware Foundation for their software manuals. It can be\nautomatically converted into plain text, a machine-readable on-line\nformat called 'info', HTML, etc. The Texinfo home page:\n.\n\neplain\nThe \"expanded plain\" format provides various common features (e.g.,\nsymbolic cross-referencing, tables of contents, indexing, citations\nusing BibTeX), for those authors who prefer to handle their own\nhigh-level formatting. The Eplain home page:\n.\n\nslitex\nAn obsolete LaTeX 2.09 format for making slides. It is replaced by\nthe 'slides' document class, although the 'beamer' package is the\nmost commonly method for making slides nowadays. The Beamer page\non CTAN: .\n",
"subsections": []
},
"File: web2c.info, Node: Languages and hyphenation, Next: Shell escapes, Prev: Formats, Up: TeX": {
"content": "",
"subsections": [
{
"name": "5.4 Languages and hyphenation",
"content": "TeX supports most natural languages. See also *note TeX extensions: TeX\nextensions.\n\n* Menu:\n\n* MLTeX:: Multi-lingual TeX.\n* TCX files:: Support for different character sets & fonts.\n* patgen invocation:: Creating hyphenation patterns.\n"
}
]
},
"File: web2c.info, Node: MLTeX, Next: TCX files, Up: Languages and hyphenation": {
"content": "",
"subsections": []
},
"Multi-lingual TeX ('mltex') is an extension of TeX originally written by": {
"content": "",
"subsections": []
},
"Michael Ferguson and now updated and maintained by Bernd Raichle. With": {
"content": "the advent of Unicode, it has become obsolete, though it is still\nsupported in Web2c in the event of bugs or compilation bugs.\n\nMLTeX allows the use of non-existing glyphs in a font by declaring\nglyph substitutions. These are restricted to substitutions of an\naccented character glyph, which need not be defined in the current font,\nby its appropriate '\\accent' construction using a base and accent\ncharacter glyph, which do have to exist in the current font. This\nsubstitution is automatically done behind the scenes, if necessary, and\nthus MLTeX additionally supports hyphenation of words containing an\naccented character glyph for fonts missing this glyph (e.g., Computer\nModern). Standard TeX suppresses hyphenation in this case.\n\nMLTeX works at '.fmt'-creation time: the basic idea is to specify the\n'-mltex' option to TeX when you '\\dump' a format. Then, when you\nsubsequently invoke TeX and read that '.fmt' file, the MLTeX features\ndescribed below will be enabled.\n\nGenerally, you use special macro files to create an MLTeX '.fmt'\nfile.\n\nThe sections below describe the two new primitives that MLTeX\ndefines. Aside from these, MLTeX is completely compatible with standard\nTeX.\n\n* Menu:\n\n* \\charsubdef:: Character substitution definitions.\n* \\tracingcharsubdef:: Tracing substitutions.\n\nFile: web2c.info, Node: \\charsubdef, Next: \\tracingcharsubdef, Up: MLTeX\n\n5.4.1.1 '\\charsubdef': Character substitutions\n..............................................\n\nThe most important primitive MLTeX adds is '\\charsubdef', used in a way\nreminiscent of '\\chardef':\n\\charsubdef COMPOSITE [=] ACCENT BASE\n\nEach of COMPOSITE, ACCENT, and BASE are font glyph numbers, expressed\nin the usual TeX syntax: `\\e symbolically, '145 for octal, \"65 for hex,\n101 for decimal.\n\nMLTeX's '\\charsubdef' declares how to construct an accented character\nglyph (not necessarily existing in the current font) using two character\nglyphs (that do exist). Thus it defines whether a character glyph code,\neither typed as a single character or using the '\\char' primitive, will\nbe mapped to a font glyph or to an '\\accent' glyph construction.\n\nFor example, if you assume glyph code 138 (decimal) for an\ne-circumflex and you are using the Computer Modern fonts, which have the\ncircumflex accent in position 18 and lowercase 'e' in the usual ASCII\nposition 101 decimal, you would use '\\charsubdef' as follows:\n\n\\charsubdef 138 = 18 101\n\nFor the plain TeX format to make use of this substitution, you have\nto redefine the circumflex accent macro '\\^' in such a way that if its\nargument is character 'e' the expansion '\\char138 ' is used instead of\n'\\accent18 e'. Similar '\\charsubdef' declaration and macro\nredefinitions have to be done for all other accented characters.\n\nTo disable a previous '\\charsubdef C', redefine C as a pair of zeros.\nFor example:\n\\charsubdef '321 = 0 0 % disable N tilde\n(Octal '321 is the ISO Latin-1 value for the Spanish N tilde.)\n\n'\\charsubdef' commands should only be given once. Although in\nprinciple you can use '\\charsubdef' at any time, the result is\nunspecified. If '\\charsubdef' declarations are changed, usually either\nincorrect character dimensions will be used or MLTeX will output missing\ncharacter warnings. (The substitution of a '\\charsubdef' is used by TeX\nwhen appending the character node to the current horizontal list, to\ncompute the width of a horizontal box when the box gets packed, and when\nbuilding the '\\accent' construction at '\\shipout'-time. In summary, the\nsubstitution is accessed often, so changing it is not desirable, nor\ngenerally useful.)\n\nFile: web2c.info, Node: \\tracingcharsubdef, Prev: \\charsubdef, Up: MLTeX\n\n5.4.1.2 '\\tracingcharsubdef': Substitution diagnostics\n......................................................\n\nTo help diagnose problems with '\\charsubdef', MLTeX provides a new\nprimitive parameter, '\\tracingcharsubdef'. If positive, every use of\n'\\charsubdef' will be reported. This can help track down when a\ncharacter is redefined.\n\nIn addition, if the TeX parameter '\\tracinglostchars' is 100 or more,\nthe character substitutions actually performed at '\\shipout'-time will\nbe recorded.\n",
"subsections": []
},
"File: web2c.info, Node: TCX files, Next: patgen invocation, Prev: MLTeX, Up: Languages and hyphenation": {
"content": "TCX (TeX character translation) files help TeX support direct input of\n8-bit international characters if fonts containing those characters are\nbeing used. Specifically, they map an input (keyboard) character code\nto the internal TeX character code (a superset of ASCII).\n\nOf the various proposals for handling more than one input encoding,\nTCX files were chosen because they follow Knuth's original ideas for the\nuse of the 'xchr' and 'xord' tables. He ventured that these would be\nchanged in the WEB source in order to adjust the actual version to a\ngiven environment. It turns out, however, that recompiling the WEB\nsources is not as simple a task as Knuth may have imagined; therefore,\nTCX files, providing the possibility of changing of the conversion\ntables on on-the-fly, have been implemented instead.\n\nThis approach limits the portability of TeX documents, as some\nimplementations do not support it (or use a different method for\ninput-internal reencoding). It may also be problematic to determine the\nencoding to use for a TeX document of unknown provenance; in the worst\ncase, failure to do so correctly may result in subtle errors in the\ntypeset output. But we feel the benefits outweigh these disadvantages.\n\nThis is entirely independent of the MLTeX extension (*note MLTeX::):\nwhereas a TCX file defines how an input keyboard character is mapped to",
"subsections": []
},
"TeX's internal code, MLTeX defines substitutions for a non-existing": {
"content": "character glyph in a font with a '\\accent' construction made out of two\nseparate character glyphs. TCX files involve no new primitives; it is\nnot possible to specify that an input (keyboard) character maps to more\nthan one character.\n\nInformation on specifying TCX files:\n\n* The best way to specify a TCX file is to list it explicitly in the\nfirst line of the main document:\n%& -translate-file=TCXFILE\n\n* You can also specify a TCX file to be used on a particular TeX run\nwith the command-line option '-translate-file=TCXFILE'.\n\n* TCX files are searched for along the 'WEB2C' path.\n\n* Initial TeX (*note Initial TeX: Initial TeX.) ignores TCX files.\n\nThe Web2c distribution comes with a number of TCX files. Two\nimportant ones are 'il1-t1.tcx' and 'il2-t1.tcx', which support ISO",
"subsections": []
},
"Latin 1 and ISO Latin 2, respectively, with Cork-encoded fonts": {
"content": "(a.k.a. the LaTeX T1 encoding). TCX files for Czech, Polish, and Slovak\nare also provided.\n\nOne other notable TCX file is 'empty.tcx', which is, well, empty.",
"subsections": []
},
"Its purpose is to reset Web2C's behavior to the default (only visible": {
"content": "ASCII being printable, as described below) when a format was dumped with\nanother TCX being active--which is in fact the case for everything but\nplain TeX in the TeX Live and other distributions. Thus:\n\nlatex somefile8.tex\n=> terminal etc. output with 8-bit chars\nlatex --translate-file=empty.tcx somefile8.tex\n=> terminal etc. output with ^^ notation\n\nSyntax of TCX files:\n1. Line-oriented. Blank lines are ignored.\n\n2. Whitespace is ignored except as a separator.\n\n3. Comments start with '%' and continue to the end of the line.\n\n4. Otherwise, a line consists of one or two character codes,\noptionally followed by 0 or 1. The last number indicates whether\nDEST is considered printable.\nSRC [DEST [PRNT]]\n\n5. Each character code may be specified in octal with a leading '0',\nhexadecimal with a leading '0x', or decimal otherwise. Values must\nbe between 0 and 255, inclusive (decimal).\n\n6. If the DEST code is not specified, it is taken to be the same as\nSRC.\n\n7. If the same SRC code is specified more than once, it is the last\ndefinition that counts.\n\nFinally, here's what happens: when TeX sees an input character with\ncode SRC, it 1) changes SRC to DEST; and 2) makes the DEST code\n\"printable\", i.e., printed as-is in diagnostics and the log file rather\nthan in '^^' notation.\n\nBy default, no characters are translated, and character codes between\n32 and 126 inclusive (decimal) are printable.\n\nSpecifying translations for the printable ASCII characters (codes\n32-127) will yield unpredictable results. Additionally you shouldn't\nmake the following characters printable: '^^I' (TAB), '^^J' (line feed),\n'^^M' (carriage return), and '^^?' (delete), since TeX uses them in\nvarious ways.\n\nThus, the idea is to specify the input (keyboard) character code for\nSRC, and the output (font) character code for DEST.\n\nBy default, only the printable ASCII characters are considered\nprintable by TeX. If you specify the '-8bit' option, all characters are\nconsidered printable by default. If you specify both the '-8bit' option\nand a TCX file, then the TCX can set specific characters to be\nnon-printable.\n\nBoth the specified TCX encoding and whether characters are printable\nare saved in the dump files (like 'tex.fmt'). So by giving these\noptions in combination with '-ini', you control the defaults seen by\nanyone who uses the resulting dump file.\n\nWhen loading a dump, if the '-8bit' option was given, then all\ncharacters become printable by default.\n\nWhen loading a dump, if a TCX file was specified, then the TCX data\nfrom the dump is ignored and the data from the file used instead.\n",
"subsections": []
},
"File: web2c.info, Node: patgen invocation, Prev: TCX files, Up: Languages and hyphenation": {
"content": "",
"subsections": []
},
"Patgen creates hyphenation patterns from dictionary files for use with": {
"content": "TeX. Synopsis:\n\npatgen DICTIONARY PATTERNS OUTPUT TRANSLATE\n\nEach argument is a filename. No path searching is done. The output\nis written to the file OUTPUT.\n\nIn addition, Patgen prompts interactively for other values.\n\nFor more information, see 'Word hy-phen-a-tion by com-put-er' by\nFrank Liang (*note References::), and also the 'patgen.web' source file.\n\nThe only options are '-help' and '-version' (*note Common options::).\n",
"subsections": []
},
"File: web2c.info, Node: Shell escapes, Next: IPC and TeX, Prev: Languages and hyphenation, Up: TeX": {
"content": "",
"subsections": [
{
"name": "5.5 Shell escapes",
"content": "TeX can execute \"shell escapes\", that is, arbitrary shell commands."
}
]
},
"Although tremendously useful, this also has obvious security": {
"content": "implications. Therefore, as of TeX Live 2009, a \"restricted\" mode for\nshell escapes is the default mode of operation, which allows executing\nonly certain commands, as specified in the 'texmf.cnf' configuration\nfile.\n\n* Unrestricted shell escapes are allowed if the option\n'--shell-escape' is specified, or if the environment variable or\nconfig file value 'shellescape' is set to 't' or 'y' and '1'.\n\n* Restricted shell escapes are allowed if 'shellescape' is set to\n'p'. This is the default.\n\n* Shell escapes are completely disabled if '--no-shell-escape' is\nspecified, or if 'shellescape' is set to anything else.\n\nWhen enabled, the TeX construct to execute a system command is\n'\\write18{SHELL-COMMAND}'; for example:\n\n\\write18{echo \"hello, world\"}\n\nFrom TeX's point of view, this is a normal '\\write' command, and is\ntherefore subject to the usual TeX expansions. Also, the system call\neither happens during the '\\output' routine or right away, according to\nthe absence or presence of the '\\immediate' prefix, as usual for\n'\\write'.\n\nThe SHELL-COMMAND string is passed to the command shell (via the C\nlibrary function 'system'). The output of SHELL-COMMAND is not diverted\nanywhere, so it will not appear in the log file, or anywhere but the\nterminal output. The exit status of the system call is also not\navailable to TeX.\n\nIn unrestricted mode, the argument is simply passed straight to\n'system' unaltered.\n\nIn restricted mode, ASCII double quote characters (\") should always\nbe used in the argument to '\\write18' where quoting of arguments is\nneeded, as in the example above. This is to achieve some measure of\nsystem independence. On Unix systems, these are replaced with single\nquote (') characters to avoid insecure further expansion. Care is also\ntaken on Windows to avoid additional expansions (from, e.g., `...`).",
"subsections": []
},
"Mismatched quotation marks in the command string result in a diagnostic": {
"content": "message in the log file; no execution is performed.\n\nAfter quotation processing, if the first word (delimited by a space\nor tab) of the command is in the list specified by the\n'shellescapecommands' configuration value, the command is executed.\nOtherwise it is not. In any case, a message is written to the log file.\n\nThe 'shellescapecommands' value is a comma-separated list of words.",
"subsections": []
},
"Whitespace is significant, and typically should not be present. The": {
"content": "default definition in 'texmf.cnf' looks like this, but with more\ncommands included:\n\nshellescapecommands = bibtex,kpsewhich,repstopdf,...\n\npdfTeX and luaTeX support reading (via '\\input' and '\\openin') and\nwriting (via '\\openout') from pipes if the first character is '|'. The\nfollowing command is then treated exactly the same as the argument to\n'\\write18'. In these engines, the primitive variable '\\pdfshellescape'\nis set to 0 if shell escapes are disabled, 1 if they are enabled, and 2\nif they are enabled with restrictions.\n\nThe purpose of this feature is to make it possible for TeX documents\nto perform useful external actions in the common case of an individual\nuser running a known document on his or her own machine. In such\nenvironments as CGI scripts or wikis where the input has to be\nconsidered untrustworthy, shell escapes should be completely disabled.\n",
"subsections": []
},
"File: web2c.info, Node: IPC and TeX, Next: TeX extensions, Prev: Shell escapes, Up: TeX": {
"content": "",
"subsections": [
{
"name": "5.6 IPC and TeX",
"content": "(If anyone uses this feature and needs documentation, write\n.)\n\nThis functionality is available only if the '--enable-ipc' option was\nspecified to 'configure' during installation of Web2c (*note\nInstallation::).\n\nIf you define 'IPCDEBUG' before compilation (e.g., with 'make\nXCFLAGS=-DIPCDEBUG'), TeX will print messages to standard error about\nits socket operations. This may be helpful if you are, well, debugging.\n"
}
]
},
"File: web2c.info, Node: TeX extensions, Prev: IPC and TeX, Up: TeX": {
"content": "",
"subsections": [
{
"name": "5.7 Extended TeX engines",
"content": "The base TeX program has been extended in many ways.\n\nThere has been a substantial effort to make a set of extended\nfunctionality available across all actively-updated engines, so that\nformats, notably LaTeX, can rely on it. A list of this common extended\nfunctionality is in a 'LaTeX News' article,\n. For\nengines in TeX Live, the detailed documentation for these primitives is\nmostly in the pdfTeX manual ().\n\nIn addition, each engine (naturally) has its own particular features,\ndescribed in its own manual. Here's a partial list of the engines.\n\ne-TeX\nAdds many new primitives, including right-to-left typesetting and\nmore registers. Now frozen. More info:\n.\n"
}
]
},
"Aleph": {
"content": "This adds Unicode support, right-to-left typesetting, and more,\nbased on the Omega engine, with the e-TeX and other extensions.\nAleph is maintained only for serious bug fixes and does not include\nthe common functionality mentioned above. More info:\n, .\n\npdfTeX\nCan produce PDF as well as DVI files. It also incorporates the\ne-TeX extensions, new primitives for hypertext and\nmicro-typography, reading/writing from pipes, and much more. In\nTeX Live, the command 'etex' invokes pdfTeX to make all these\nadditions available with DVI output. Home page:\n.\n",
"subsections": []
},
"LuaTeX": {
"content": "Embeds the Lua programming language () and opens up\nthe TeX typesetting engine to control from Lua, starting from the\npdfTeX capabilities as a base. Also natively supports UTF-8 input,\nthe OpenType and TrueType font formats, and use of system fonts.\nHome page: .\n",
"subsections": []
},
"XeTeX": {
"content": "Combines support for Unicode input, the OpenType and TrueType font\nformats, and use of system fonts with the capabilities of pdfTeX,\nwith the exception of the font expansion part of micro-typography.\nHome page: .\n\nhiTeX\nOutputs its own HINT format, which is designed for reading\ntechnical documents on mobile devices. More info:\n.\n\npTeX\nupTeX\nWith additional support for Japanese; pTeX was the original engine,\nand upTeX has native Unicode support and thus is more useful for\nChinese and Korean. More info: ,\n.\n\nepTeX\neupTeX\nFurther extends pTeX and upTeX with the e-TeX extensions. More\ninfo: , .\n",
"subsections": []
},
"File: web2c.info, Node: Metafont, Next: MetaPost, Prev: TeX, Up: Top": {
"content": "",
"subsections": []
},
"6 Metafont: Creating typeface families": {
"content": "",
"subsections": []
},
"Metafont is a system for producing shapes; it was designed for producing": {
"content": "complete typeface families, but it can also produce geometric designs,\ndingbats, etc. And it has considerable mathematical and\nequation-solving capabilities which can be useful entirely on their own.\n\nMetafont is a batch language, like C or Pascal: you compile a",
"subsections": []
},
"Metafont program into a corresponding font, rather than interactively": {
"content": "drawing lines or curves. This approach has both considerable\ndisadvantages (people unfamiliar with conventional programming languages\nwill be unlikely to find it usable) and considerable advantages (you can\nmake your design intentions specific and parameterizable). For a\ncomplete description of the Metafont language, see 'The METAFONTbook'\n(*note References::).\n\n* Menu:\n\n* mf invocation:: Invoking Metafont.\n* Initial Metafont:: Making bases.\n* Modes:: Device definitions for Metafont.\n* Online Metafont graphics:: Seeing MF output online.\n* gftodvi invocation:: Making proofsheets for fonts.\n* mft invocation:: Prettyprinting Metafont sources.\n",
"subsections": []
},
"File: web2c.info, Node: mf invocation, Next: Initial Metafont, Up: Metafont": {
"content": "",
"subsections": [
{
"name": "6.1 'mf' invocation",
"content": ""
}
]
},
"Metafont (usually invoked as 'mf') reads character definitions specified": {
"content": "in the Metafont programming language, and outputs the corresponding\nfont. This section merely describes the options available in the Web2c\nimplementation. For a complete description of the Metafont language,\nsee 'The Metafontbook' (*note References::).\n\nMetafont processes its command line and determines its memory dump\n(base) file in a way exactly analogous to MetaPost and TeX (*note tex\ninvocation::, and *note Memory dumps::). Synopses:\n\nmf [OPTION]... [MFNAME[.mf]] [MF-COMMANDS]\nmf [OPTION]... \\FIRST-LINE\nmf [OPTION]... &BASE ARGS\n\nMost commonly, a Metafont invocation looks like this:\nmf '\\mode:=MODE; mag:=MAGNIFICATION; input MFNAME'\n(The single quotes avoid unwanted interpretation by the shell.)\n\nMetafont searches the usual places for the main input file MFNAME\n(*note (kpathsea)Supported file formats::), extending MFNAME with '.mf'\nif necessary. To see all the relevant paths, set the environment\nvariable 'KPATHSEADEBUG' to '-1' before running the program. By\ndefault, Metafont runs an external program named 'mktexmf' to create any\nnonexistent Metafont source files you input. You can disable this at\nconfigure-time or runtime (*note (kpathsea)mktex configuration::). This\nis mostly for the sake of the EC fonts, which can be generated at any\nsize.\n\nMetafont writes the main GF output to the file 'BASEMFNAME.NNNgf',\nwhere NNN is the font resolution in pixels per inch, and BASEMFNAME is\nthe basename of MFNAME, or 'mfput' if no input file was specified. A GF\nfile contains bitmaps of the actual character shapes. Usually GF files\nare converted immediately to PK files with GFtoPK (*note gftopk\ninvocation::), since PK files contain equivalent information, but are\nmore compact. (Metafont output in GF format rather than PK for only\nhistorical reasons.)\n\nMetafont also usually writes a metric file in TFM format to\n'BASEMFNAME.tfm'. A TFM file contains character dimensions, kerns, and\nligatures, and spacing parameters. TeX reads only this .tfm file, not\nthe GF file.\n\nThe MODE in the example command above is a name referring to a device\ndefinition (*note Modes::); for example, 'localfont' or 'ljfour'. These\ndevice definitions must generally be precompiled into the base file. If\nyou leave this out, the default is 'proof' mode, as stated in 'The",
"subsections": []
},
"Metafontbook', in which Metafont outputs at a resolution of 2602dpi;": {
"content": "this is usually not what you want. The remedy is simply to assign a\ndifferent mode--'localfont', for example.\n\nThe MAGNIFICATION assignment in the example command above is a\nmagnification factor; for example, if the device is 600dpi and you\nspecify 'mag:=2', Metafont will produce output at 1200dpi. Very often,\nthe MAGNIFICATION is an expression such as 'magstep(.5)', corresponding\nto a TeX \"magstep\", which are factors of 1.2 * sqrt(2).\n\nAfter running Metafont, you can use the font in a TeX document as\nusual. For example:\n\\font\\myfont = newfont\n\\myfont Now I am typesetting in my new font (minimum hamburgers).\n\nThe program accepts the following options, as well as the standard\n'-help' and '-version' (*note Common options::):\n'-[no]-file-line-error'\n'-fmt=FMTNAME'\n'-halt-on-error'\n'-ini'\n'-interaction=STRING'\n'-jobname=STRING'\n'-kpathsea-debug=NUMBER'\n'-[no]parse-first-line'\n'-output-directory'\n'-progname=STRING'\n'-recorder'\n'-translate-file=TCXFILE'\n'-8bit'\nThese options are common to TeX, Metafont, and MetaPost. *Note\nCommon options::.\n\n'-mktex=FILETYPE'\n'-no-mktex=FILETYPE'\nTurn on or off the 'mktex' script associated with FILETYPE. The\nonly value that makes sense for FILETYPE is 'mf'.\n",
"subsections": []
},
"File: web2c.info, Node: Initial Metafont, Next: Modes, Prev: mf invocation, Up: Metafont": {
"content": "",
"subsections": [
{
"name": "6.2 Initial Metafont",
"content": "'inimf' is the \"initial\" form of Metafont, which does lengthy\ninitializations avoided by the \"virgin\" ('vir') form, so as to be\ncapable of dumping '.base' files (*note Memory dumps::). For a detailed\ncomparison of virgin and initial forms, see *note Initial and virgin::.\n\nFor a list of options and other information, see *note mf\ninvocation::.\n\nThe only memory dump file commonly used with Metafont is the default\n'plain.base', also known as 'mf.base' (again, *note Memory dumps::). It\nis created by default during installation, but you can also do so by\nhand if necessary (e.g., if a Metafont update is issued):\nmf -ini '\\input plain; input modes; dump'\n(The quotes prevent interpretation of the backslashes from the shell.)\nThen install the resulting 'plain.base' in '$(basedir)'\n('/usr/local/share/texmf/web2c' by default), and link 'mf.base' to it.\n\nFor an explanation of the additional 'modes.mf' file, see *note\nModes::. This file has no counterpart in TeX or MetaPost.\n\nIn the past, it was sometimes useful to create a base file\n'cmmf.base' (a.k.a. 'cm.base'), with the Computer Modern macros also\nincluded in the base file. Nowadays, however, the additional time\nrequired to read 'cmbase.mf' is exceedingly small, usually not enough to\nbe worth the administrative hassle of updating the 'cmmf.base' file when\nyou install a new version of 'modes.mf'. People actually working on a\ntypeface may still find it worthwhile to create their own base file, of\ncourse.\n"
}
]
},
"File: web2c.info, Node: Modes, Next: Online Metafont graphics, Prev: Initial Metafont, Up: Metafont": {
"content": "",
"subsections": [
{
"name": "6.3 Modes: Device definitions for Metafont",
"content": ""
}
]
},
"Running Metafont and creating Metafont base files requires information": {
"content": "that TeX and MetaPost do not: \"mode\" definitions which specify device\ncharacteristics, so Metafont can properly rasterize the shapes.\n\nWhen making a base file, a file containing modes for\nlocally-available devices should be input after 'plain.mf'. One\ncommonly used file is ; it includes all\nknown definitions.\n\nIf, however, for some reason you have decreased the memory available\nin your Metafont, you may need to copy 'modes.mf' and remove the\ndefinitions irrelevant to you (probably most of them) instead of using\nit directly. (Or, if you're a Metafont hacker, maybe you can suggest a\nway to redefine 'modedef' and/or 'modesetup'; right now, the amount of\nmemory used is approximately four times the total length of the\n'modedef' names, and that's a lot.)\n\nIf you have a device not included in 'modes.mf', please see comments\nin that file for how to create the new definition, and please send the\ndefinition to to get it included in the next\nrelease of 'modes.mf'.\n\nUsually, when you run Metafont you must supply the name of a mode\nthat was dumped in the base file. But you can also define the mode\ncharacteristics dynamically, by invoking Metafont with an assignment to\n'smode' instead of 'mode', like this:\nmf '\\smode:=\"newmode.mf\"; mag:=MAGNIFICATION; input MFNAME'",
"subsections": []
},
"This is most useful when you are working on the definition of a new": {
"content": "mode.\n\nThe MAGNIFICATION and MFNAME arguments are explained in *note mf\ninvocation::. In the file 'newmode.mf', you should have the following\n(with no 'modedef' or 'enddef'), if you are using 'modes.mf'\nconventions:\nmodeparam (pixelsperinch, DPI);\nmodeparam (blacker, B);\nmodeparam (fillin, F);\nmodeparam (ocorrection, O);\nmodecommonsetup;\n(Of course, you should use real numbers for DPI, B, F, and O.)\n\nFor more information on the use of 'smode', or if you are not using\n'modes.mf', see page 269 of 'The Metafontbook'.\n",
"subsections": []
},
"File: web2c.info, Node: Online Metafont graphics, Next: gftodvi invocation, Prev: Modes, Up: Metafont": {
"content": "",
"subsections": [
{
"name": "6.4 Online Metafont graphics",
"content": ""
}
]
},
"The Web2c implementation of Metafont can do online graphics with a": {
"content": "number of devices. (See the Metafont manual for more information about\nhow to draw on your screen.) By default, no graphics support is\nenabled.\n\nMetafont examines the 'MFTERM' environment variable or config file\nvalue at runtime, or the 'TERM' environment variable if 'MFTERM' is not\nset, to determine the device support to use. Naturally, only the\ndevices for which support has been compiled in can be selected.\n\nHere is a table of the possibilities, showing the 'MFTERM' value and\nthe corresponding 'configure' option(s) in parentheses.\n\n'epsf'\n('--enable-epsfwin') Pseudo-window server for Encapsulated\nPostScript (see 'web2c/window/epsf.c'). This device produces an\nEPS file containing the graphics which would be displayed online on\nother devices. The name of the EPS file defaults to metafont.eps\nbut can be changed by setting the MFEPSF environment variable to\nthe new filename. Contributed by Mathias Herberts.\n\n'hp2627'\n('--enable-hp2627win') HP2627a color graphics terminals.\n\n'mftalk'\n('--enable-mftalkwin') Generic window server (see\n'web2c/window/mftalk.c').\n\n'next'\n('--enable-next') NeXT window system. This requires a separate\nprogram, called 'DrawingServant', available separately. See the\n'web2c/window/next.c'.\n\n'regis'\n('--enable-regiswin') Regis terminals.\n\n'sun'\n('--enable-suntoolswin') The old Suntools (not any flavor of X)\nwindow system. (You can get the even older SunWindows 'gfx' system\nby using 'sun-gfx.c'.)\n\n'tek'\n('--enable-tektronixwin') Tektronix terminals.\n\n'uniterm'\n('--enable-unitermwin') Uniterm, Simon Poole's emulator of a smart\nTektronix 4014 terminal. This may work with regular Tektronix\nterminals as well; it's faster than the driver\n'--enable-tektronixwin' selects.\n\n'xterm'\n'--with-x' The X window system (version 11).\n\nThere are two variants of the X11 support, one that works with the\nXt toolkit, and another that works directly with Xlib. The Xt\nsupport is more efficient and has more functionality, so it is the\ndefault. If you must use the Xlib support, use 'configure --with-x\n--with-kf-x-toolkit=no'.\n\nSpecify '--disable-mf-nowin' in order not to build a separate\nnon-windows-capable Metafont executable 'mf-nowin' (or\n'mf-nowin.exe').\n\nYou cannot specify any of the usual X options (e.g., '-geometry')\non the Metafont command line, but you can specify X resources in\nyour '~/.Xdefaults' or '~/.Xresources' file. The class name is\n'Metafont'. If you're using the Xt support, all the usual X\ntoolkit resources are supported. If you're using the Xlib support,\nonly the 'geometry' resource is supported.\n\nYou specify the X display to which Metafont connects in the\n'DISPLAY' environment variable, as usual.\n\nWriting support for a new device is straightforward. Aside from\ndefining the basic drawing routines that Metafont uses (see 'mf.web'),\nyou only have to add another entry to the tables on the last page of\n'web2c/lib/texmfmp.c'. Or you can write an independent program and use\nMFtalk (see 'web2c/window/mftalk.c').\n",
"subsections": []
},
"File: web2c.info, Node: gftodvi invocation, Next: mft invocation, Prev: Online Metafont graphics, Up: Metafont": {
"content": "",
"subsections": [
{
"name": "6.5 GFtoDVI: Character proofs of fonts",
"content": "GFtoDVI makes \"proof sheets\" from a GF bitmap file as output by, for\nexample, Metafont (*note Metafont::). This is an indispensable aid for\nfont designers or Metafont hackers. Synopsis:\n\ngftodvi [OPTION]... GFNAME[gf]\n\nThe font GFNAME is searched for in the usual places (*note\n(kpathsea)Glyph lookup::). To see all the relevant paths, set the\nenvironment variable 'KPATHSEADEBUG' to '-1' before running the\nprogram.\n\nThe suffix 'gf' is supplied if not already present. This suffix is\nnot an extension, no '.' precedes it; for instance, 'cmr10.600gf'.\n\nThe output filename is the basename of GFNAME extended with '.dvi',\ne.g., 'gftodvi /wherever/foo.600gf' creates './foo.dvi'.\n\nThe characters from GFNAME appear one per page in the DVI output,\nwith labels, titles, and annotations, as specified in Appendix H\n(Hardcopy Proofs) of 'The Metafontbook'.\n\nGFtoDVI uses several fonts besides GFNAME itself:\n\n* \"gray font\" (default 'gray'): for the pixels that actually make up\nthe character. Simply using black is not right, since then labels,\nkey points, and other information could not be shown.\n\n* \"title font\" (default 'cmr8'): for the header information at the\ntop of each output page.\n\n* \"label font\" (default 'cmtt10'): for the labels on key points of\nthe figure.\n\n* \"slant font\" (no default): for diagonal lines, which are otherwise\nsimulated using horizontal and vertical rules.\n\nTo change the default fonts, you must use 'special' commands in your\nMetafont source file, typically via commands like 'slantfont slantlj4'."
}
]
},
"There is no default slant font since no one printer is suitable as a": {
"content": "default. You can make your own by copying one of the existing files,\nsuch as '.../fonts/source/public/misc/slantlj4.mf' and then running 'mf'\non it.\n\nFor testing purposes, you may it useful to run 'mf-nowin rtest' (hit\nRETURN when it stops) to get a 'gf' file of a thorn glyph. Or use 'mf'\ninstead of 'mf-nowin' to have the glyph(s) displayed on the screen.",
"subsections": []
},
"After that, 'gftodvi rtest.2602gf' should produce 'rtest.dvi', which you": {
"content": "process as usual.\n\nThe program accepts the following option, as well as the standard\n'-verbose', '-help', and '-version' (*note Common options::):\n\n'-overflow-label-offset=POINTS'\nTypeset the so-called overflow labels, if any, POINTS TeX points\nfrom the right edge of the character bounding box. The default is\na little over two inches (ten million scaled points, to be\nprecise). Overflow equations are used to locate coordinates when\ntheir actual position is too crowded with other information.\n",
"subsections": []
},
"File: web2c.info, Node: mft invocation, Prev: gftodvi invocation, Up: Metafont": {
"content": "",
"subsections": [
{
"name": "6.6 MFT: Prettyprinting Metafont source",
"content": "MFT translates a Metafont program into a TeX document suitable for\ntypesetting, with the aid of TeX macros defined in the file\n'mftmac.tex'. Synopsis:\n\nmft [OPTION]... MFNAME[.mf]\n\nMFT searches the usual places for MFNAME (*note (kpathsea)Supported\nfile formats::). To see all the relevant paths, set the environment\nvariable 'KPATHSEADEBUG' to '-1' before running the program. The\noutput goes to the basename of MFNAME extended with '.tex', e.g., 'mft\n/wherever/foo.mf' creates './foo.tex'.\n\nLine breaks in the input are carried over into the output; moreover,\nblank spaces at the beginning of a line are converted to quads of\nindentation in the output. Thus, you have full control over the\nindentation and line breaks. Each line of input is translated\nindependently of the others.\n\nFurther control is allowed via Metafont comments:\n* Metafont comments following a single '%' should be valid TeX input.\nBut Metafont material can be included within vertical bars in a\ncomment; this will be translated by MFT as if it were regular\nMetafont code. For example, a comment like '% |x2r| is the tip of\nthe bowl' will be translated into the TeX '% $x{2r}$ is the ...',\ni.e., the 'x2r' is treated as an identifier.\n\n* '%%' indicates that the remainder of an input line should be copied\nverbatim to the output. This is typically used to introduce\nadditional TeX material at the beginning or an MFT job, e.g. code\nto modify the standard layout or the formatting macros defined in\n'mftmac.tex', or to add a line saying '%%\\bye' at the end of the\njob. (MFT doesn't add this automatically in order to allow\nprocessing several files produces by MFT in the same TeX job.)\n\n* '%%% TOKEN1 OTHER-TOKENS' introduces a change in MFT's formatting\nrules; all the OTHER-TOKENS will henceforth be translated according\nto the current conventions for TOKEN1. The tokens must be symbolic\n(i.e., not numeric or string tokens). For example, the input line\n%%% addto fill draw filldraw\nsays to format the 'fill', 'draw', and 'filldraw' operations of\nplain Metafont just like the primitive token 'addto', i.e., in\nboldface type. Without such reformatting commands, MFT would treat\n'fill' like an ordinary tag or variable name. In fact, you need a\n'%%%' command even to get parentheses to act like delimiters.\n\n* '%%%%' introduces an MFT comment, i.e., MFT ignores the remainder\nof such a line.\n\n* Five or more '%' signs should not be used.\n\n(The above description was edited from 'mft.web', written by\nD.E. Knuth.)\n\nThe program accepts the following options, as well as the standard\n'-help' and '-version' (*note Common options::):\n'-change=CHFILE[.ch]'\nApply the change file CHFILE as with Tangle and Weave (*note\nWEB::).\n\n'-style=MFTFILE[.mft]'\nRead MFTFILE before anything else; a MFT style file typically\ncontains only MFT directives as described above. The default style\nfile is named 'plain.mft', which defines this properly for programs\nusing plain Metafont. The MFT files is searched along the\n'MFTINPUTS' path; see *note (kpathsea)Supported file formats::.\n\nOther examples of MFT style files are 'cmbase.mft', which defines\nformatting rules for the macros defined in 'cm.base', and 'e.mft',\nwhich was used in the production of Knuth's Volume E, 'Computer\nModern Typefaces'.\n\nUsing an appropriate MFT style file, it is also possible to\nconfigure MFT for typesetting MetaPost sources. However, MFT does\nnot search the usual places for MetaPost input files.\n\nIf you use eight-bit characters in the input file, they are passed on\nverbatim to the TeX output file; it is up to you to configure TeX to\nprint these properly.\n"
}
]
},
"File: web2c.info, Node: MetaPost, Next: BibTeX, Prev: Metafont, Up: Top": {
"content": "",
"subsections": []
},
"7 MetaPost: Generating PostScript": {
"content": "MetaPost is a picture-drawing language similar to Metafont (*note\nMetafont::), but instead of outputting bitmaps in a \"font\", it outputs",
"subsections": []
},
"PostScript commands. It's primarily intended for creating technical": {
"content": "illustrations, but can also be used to create PostScript or OpenType\nfonts ().\n\nMetaPost also provides for arbitrary integration of text and graphics\nin a natural way, using any typesetter (TeX and Troff are both\nsupported) and a number of other subsidiary programs, described below.\n\n* Menu:\n\n* mpost invocation:: Invoking MetaPost.\n* Initial MetaPost:: Making mems.\n* dvitomp invocation:: DVI-to-MPX translation.\n",
"subsections": []
},
"File: web2c.info, Node: mpost invocation, Next: Initial MetaPost, Up: MetaPost": {
"content": "",
"subsections": [
{
"name": "7.1 'mpost' invocation",
"content": ""
}
]
},
"MetaPost (installed as 'mpost') reads a series of pictures specified in": {
"content": "the MetaPost programming language, and outputs corresponding PostScript\ncode. This section merely describes the options available in the Web2c\nimplementation. For a complete description of the MetaPost language,\nsee AT&T technical report CSTR-162, generally available in\n'TEXMF/doc/metapost/', where TEXMF is the root of TeX directory\nstructure. The MetaPost home page: .\n\nAlso, a standard MetaPost package for drawing graphs is documented in\nAT&T technical report CSTR-164, available as the file 'mpgraph.ps',\ngenerally stored alongside 'mpman.ps'.\n\nMetaPost processes its command line and determines its memory dump\n(mem) file in a way analogous to Metafont and TeX (*note 'tex'\ninvocation: tex invocation, and *note Memory dumps::). Synopses:\n\nmpost [OPTION]... [MPNAME[.mp]] [MP-COMMANDS]\nmpost [OPTION]... \\FIRST-LINE\nmpost [OPTION]... &MEM ARGS\n\nMetaPost searches the usual places for the main input file MPNAME\n(*note (kpathsea)Supported file formats::), extending MPNAME with '.mp'\nif necessary. To see all the relevant paths, set the environment\nvariable 'KPATHSEADEBUG' to '-1' before running the program.\n\nMetaPost writes its PostScript output to a series of files\n'BASEMPNAME.NNN' (or perhaps 'BASEMPNAME.ps', very occasionally\n'BASEMPNAME.tfm'), where NNN are the figure numbers specified in the\ninput, typically to the 'beginfig' macro, and BASEMPNAME is the basename\nof MPNAME, or 'mpout' if no input file was specified. MetaPost uses the\n'.ps' extension when the figure number is out of range, e.g., if you say\n'beginfig(-1)'.\n\nYou can use the output files as figures in a TeX document just as\nwith any other PostScript figures. For example, with this TeX command:\n\\special{psfile=\"FILENAME\"}\nor by using 'epsf.tex' (*note (dvips)EPSF macros::).\n\nThe MetaPost construct\nbtex ... TEX-INPUT ... etex\ngenerates a MetaPost picture expression corresponding to TEX-INPUT.\n\nThe construct\nverbatimtex ... TEX-INPUT ... etex\nsimply passes the TEX-INPUT through to TeX. For example, if you are\nusing LaTeX, your MetaPost input file must start with a 'verbatimtex'\nblock that gives the necessary '\\documentclass' (or '\\documentstyle')\n'\\begin{document}' command. You will also need to set the environment\nvariable 'TEX' to 'latex'.\n\nTEX-INPUT need not be specifically TeX input; it could also be Troff.",
"subsections": []
},
"In that case, you will need the '-m pictures' Troff macro package": {
"content": "(unfortunately absent from many Troff implementations), or an equivalent\nsuch as the '-m pspic' macros from GNU groff described in grops(1).\n\nNaturally, you must use fonts that are supported by the typesetter;\nspecifically, you'll probably want to use standard PostScript fonts with",
"subsections": []
},
"Troff. And only the TeX system understands Computer Modern or other": {
"content": "Metafont fonts; you can also use PostScript fonts with TeX, of course.\n\nMetaPost-generated PostScript figures which do use Computer Modern\nfonts for labels cannot be directly previewed or printed. Instead, you\nmust include them in a TeX document and run the resulting DVI file\nthrough Dvips to arrange for the downloading of the required fonts\n(*note (dvips)Fonts in figures::). To help with this, the MetaPost\ndistribution provides a small TeX file 'mproof.tex' which is typically\ncalled as:\ntex mproof MP-OUTPUT-FILES... ; dvips mproof -o\nThe resulting file 'mproof.ps' can then be printed or previewed.\n\nTo generate EPSF files, set the internal MetaPost variable\n'prologues' positive. To make the output files self-contained, use only\nstandard PostScript fonts. MetaPost reads the same 'psfonts.map' file\nas Dvips, to determine PostScript fonts that need to be downloaded\n(*note (dvips)psfonts.map::).\n\nIt is possible for pdfTeX to read MetaPost output directly; this is\nin contrast to general EPSF files, which have to be converted for use\nwith PDF output. The easiest way is to name the MetaPost output files\nwith the '.mps' extension. Then the LaTeX '\\includegraphics' command,\nfor example, will be able to read them, even when outputting PDF.\n\nMetaPost can write output files, via the 'write' primitive; this\nopens a security hole. *Note tex invocation::.\n\nThe program accepts the following options, as well as the standard\n'-help' and '-version' (*note Common options::):\n'-[no]-file-line-error'\n'-fmt=FMTNAME'\n'-halt-on-error'\n'-ini'\n'-interaction=STRING'\n'-jobname=STRING'\n'-kpathsea-debug=NUMBER'\n'-[no]parse-first-line'\n'-output-directory'\n'-progname=STRING'\n'-recorder'\n'-translate-file=TCXFILE'\n'-8bit'\nThese options are common to TeX, Metafont, and MetaPost. *Note\nCommon options::.\n\n'-T'\n'-troff'\nSet the 'prologues' internal variable to '1'.\n\n'-tex=TEXPROGRAM'\nWhen this option is given, the program TEXPROGRAM is used to\ntypeset the labels.\n",
"subsections": []
},
"File: web2c.info, Node: Initial MetaPost, Next: dvitomp invocation, Prev: mpost invocation, Up: MetaPost": {
"content": "",
"subsections": [
{
"name": "7.2 Initial MetaPost",
"content": ""
}
]
},
"As of MetaPost 1.504 (TeX Live 2011), MetaPost no longer dumps '.mem'": {
"content": "files (*note Memory dumps::) and does not distinguish virgin and initial\nforms (*note Initial and virgin::). Instead, the \"initial\" file name is\nread in its source form--that is, 'mpost.mp' when the program is invoked\nas 'mpost'.\n\nFor a list of options and other information, see *note mpost\ninvocation::.\n\nMetaPost provides a format with all the features of plain Metafont,\ncalled 'mfplain'. You can use that in the same way; just run 'mfplain'\ninstead of 'mpost'. This lets you directly process Metafont source\nfiles with MetaPost, producing character proofs (one file for each\ncharacter) similar to those produced with Metafont in proof mode and\nGFtoDVI (*note gftodvi invocation::).\n",
"subsections": []
},
"File: web2c.info, Node: dvitomp invocation, Prev: Initial MetaPost, Up: MetaPost": {
"content": "",
"subsections": [
{
"name": "7.3 DVItoMP: DVI to MPX conversion",
"content": "DVItoMP converts DVI files into low-level MetaPost commands in a\nso-called MPX file. Synopsis:\n\ndvitomp DVIFILE[.dvi] [MPXFILE[.mpx]]\n"
}
]
},
"If MPXFILE is not specified, the output goes to the basename of DVIFILE": {
"content": "extended with '.mpx', e.g., 'dvitomp /wherever/foo.dvi' creates\n'./foo.mpx'.\n\nDVItoMP supports Dvips-style color specials, such as 'color push\nNAME' and 'color pop', outputting them as 'withcolor' MetaPost commands.\n\nThe only options are '-help' and '-version' (*note Common options::).\n",
"subsections": []
},
"File: web2c.info, Node: BibTeX, Next: WEB, Prev: MetaPost, Up: Top": {
"content": "",
"subsections": []
},
"8 BibTeX: Bibliographies": {
"content": "",
"subsections": []
},
"BibTeX automates much of the job of typesetting bibliographies, and": {
"content": "makes bibliography entries reusable in many different contexts.\n\n* Menu:\n\n* bibtex invocation::\n* Basic BibTeX style files:: The standard and semi-standard styles.\n",
"subsections": []
},
"File: web2c.info, Node: bibtex invocation, Next: Basic BibTeX style files, Up: BibTeX": {
"content": "",
"subsections": [
{
"name": "8.1 BibTeX invocation",
"content": ""
}
]
},
"BibTeX creates a printable bibliography ('.bbl') file from references in": {
"content": "a '.aux' file, generally written by TeX or LaTeX. The '.bbl' file is\nthen incorporated on a subsequent run. The basic bibliographic\ninformation comes from '.bib' files, and a BibTeX style ('.bst') file\ncontrols the precise contents of the '.bbl' file. Synopsis:\n\nbibtex [OPTION]... AUXFILE[.aux]\n",
"subsections": []
},
"The output goes to the basename of AUXFILE extended with '.bbl'; for": {
"content": "example, 'bibtex /wherever/foo.aux' creates './foo.bbl'. BibTeX also\nwrites a log file to the basename of AUXFILE extended with '.blg'.\n\nThe names of the '.bib' and '.bst' files are specified in the '.aux'\nfile as well, via the '\\bibliography' and '\\bibliographystyle' (La)TeX\nmacros. BibTeX searches for '.bib' files using the 'BIBINPUTS' and\n'TEXBIB' paths, and for '.bst' files using 'BSTINPUTS' (*note\n(kpathsea)Supported file formats::). It does no path searching for\n'.aux' files.\n\nThe program accepts the following options, as well as the standard\n'-help' and '-version' (*note Common options::):\n'-terse'\nSuppress the program banner and progress reports normally output.\n\n'-min-crossrefs=N'\nIf at least N (2 by default) bibliography entries refer to another\nentry E via their 'crossref' field, include E in the .bbl file,\neven if it was not explicitly referenced in the .aux file. For\nexample, E might be a conference proceedings as a whole, with the\ncross-referencing entries being individual articles published in\nthe proceedings.\n\nIf you want to avoid these automatic inclusions altogether, make N\na sufficiently large number, and be sure to remove any previous\n.aux and .bbl files. Otherwise the option may appear to have no\neffect, since BibTeX will have added the citation for E to the\n.aux, and nothing will remove it.\n\nSee also:\n'btxdoc.tex'\nBasic LaTeXable documentation for general BibTeX users.\n\n'btxhak.tex'\nLaTeXable documentation for style designers.\n\n'btxdoc.bib'\nBibTeX database file for the two above documents.\n\n'xampl.bib'\nExample database file with all the standard entry types.\n\n''\nA very large '.bib' and '.bst' collection, including references for\nall the standard TeX books and a complete bibliography for TUGboat.\n",
"subsections": []
},
"File: web2c.info, Node: Basic BibTeX style files, Prev: bibtex invocation, Up: BibTeX": {
"content": "",
"subsections": [
{
"name": "8.2 Basic BibTeX style files",
"content": ""
}
]
},
"Here are descriptions of the four standard and four semi-standard basic": {
"content": "",
"subsections": []
},
"BibTeX styles. 'CTAN:/biblio/bibtex' contains these and many more (for": {
"content": "CTAN info, *note (kpathsea)unixtex.ftp::).\n\n'plain'\nSorts entries alphabetically, with numeric labels. Generally\nformatted according to van Leunen's 'A Handbook for Scholars'. The\nother style files listed here are based on 'plain'.\n\n'abbrv'\nFirst names, month names, and journal names are abbreviated.\n\n'acm'\nNames are printed in small caps.\n\n'alpha'\nAlphanumeric labels, e.g., 'Knu66'.\n\n'apalike'\nNo labels at all; instead, the year appears in parentheses after\nthe author. Use this in conjunction with 'apalike.tex' (plain TeX)\nor 'apalike.sty' (LaTeX), which also changes the citations in the\ntext to be '(AUTHOR, YEAR)'.\n\n'ieeetr'\nNumeric labels, entries in citation order, IEEE abbreviations,\narticle titles in quotes.\n\n'siam'\nNumeric labels, alphabetic order, 'Math. Reviews' abbreviations,\nnames in small caps.\n\n'unsrt'\nLists entries in citation order, i.e., unsorted.\n\n'btxbst.doc'\nThe template file and documentation for the standard styles.\n",
"subsections": []
},
"File: web2c.info, Node: WEB, Next: DVI utilities, Prev: BibTeX, Up: Top": {
"content": "",
"subsections": []
},
"9 WEB: Literate programming": {
"content": "\"WEB\" languages allow you to write a single source file that can produce\nboth a compilable program and a well-formatted document describing the\nprogram in as much detail as you wish to prepare. Writing in this kind\nof dual-purpose language is called \"literate programming\". (The Usenet\nnewsgroup 'comp.programming.literate' is devoted to this subject.)\n\nWEB-like languages have been implemented with many pairs of base\nlanguages: Cweb provides C and Troff (*note References::); CWEB provides\nC and TeX ('CTAN:/web/ccpp/cweb'); Spiderweb provides C, C++, Awk, Ada,\nmany others, and TeX ('CTAN:/web/spiderweb'); and, of course, the\noriginal WEB provides Pascal and TeX, the implementation languages for\nthe original TeX, Metafont, MetaPost, and related programs to come from\nthe TeX project at Stanford.\n\nThe original WEB language is documented in the file 'webman.tex',\nwhich is included in the archive (and\navailable in many other places, of course).\n\n* Menu:\n\n* tangle invocation::\n* weave invocation::\n* pooltype invocation::\n",
"subsections": []
},
"File: web2c.info, Node: tangle invocation, Next: weave invocation, Up: WEB": {
"content": "",
"subsections": [
{
"name": "9.1 Tangle: Translate WEB to Pascal",
"content": "Tangle creates a compilable Pascal program from a WEB source file (*note\nWEB::). Synopsis:\n\ntangle [OPTION]... WEBFILE[.web] [CHANGEFILE[.ch]]\n"
}
]
},
"The Pascal output is written to the basename of WEBFILE extended with": {
"content": "'.p'; for example, 'tangle /wherever/foo.web' creates './foo.p'. Tangle\napplies CHANGEFILE to WEBFILE before writing the output; by default,\nthere is no change file.\n\nIf the program makes use of the WEB string facility, Tangle writes\nthe string pool to the basename of WEBFILE extended with '.pool'.\n\nThe Pascal output is packed into lines of 72 characters or less, with\nthe only concession to readability being the termination of lines at\nsemicolons when this can be done conveniently.\n\nThe program accepts the following options, as well as the standard\n'--help' and '--version' (*note Common options::):\n\n'-length=NUMBER'\nThe number of characters that are considered significant in an\nidentifier. Whether underline characters are counted depends on\nthe '-underline' option. The default value is 32, the original\ntangle used 7, but this proved too restrictive for use by Web2c.\n\n'-lowercase'\n'-mixedcase'\n'-uppercase'\nThese options specify the case of identifiers in the output of\ntangle. If '-uppercase' ('-lowercase') is specified, tangle will\nconvert all identifiers to uppercase (lowercase). The default is\n'-mixedcase', which specifies that the case will not be changed.\n\n'-underline'\nWhen this option is given, tangle does not strip underline\ncharacters from identifiers.\n\n'-loose'\n'-strict'\nThese options specify how strict tangle must be when checking\nidentifiers for equality. The default is '-loose', which means\nthat tangle will follow the rules set by the case-smashing and\nunderline options above. If '-strict' is set, then identifiers\nwill always be stripped of underlines and converted to uppercase\nbefore checking whether they collide.\n",
"subsections": []
},
"File: web2c.info, Node: weave invocation, Next: pooltype invocation, Prev: tangle invocation, Up: WEB": {
"content": "",
"subsections": [
{
"name": "9.2 Weave: Translate WEB to TeX",
"content": "Weave creates a TeX document from a WEB source file (*note WEB::),\nassuming various macros defined in 'webmac.tex'. It takes care of\ntypographic details such as page layout, indentation, and italicizing\nidentifiers. It also automatically gathers and outputs extensive\ncross-reference information. Synopsis:\n\nweave [OPTION]... WEBFILE[.web] [CHANGEFILE[.ch]]\n"
}
]
},
"The output is to the basename of WEBFILE extended with '.tex'; for": {
"content": "example, 'weave /wherever/foo.web' creates './foo.tex'. Weave applies\nCHANGEFILE to WEBFILE before writing the output; by default, there is no\nchange file.\n\nThe program accepts the following option, as well as the standard\n'-verbose', '-help' and '-version' (*note Common options::):\n'-x'\nOmit the cross-reference information: the index, the list of WEB\nmodule names, and the table of contents (an empty 'CONTENTS.tex'\nfile will still be written when the Weave output file is processed\nby TeX using the default 'webmac.tex', though).\n\nConventionally, WEB programmers should define the TeX '\\title' macro\nat the beginning of the source file. Also, to get output of only\nchanged modules, one can say '\\let\\maybe=\\iffalse' (usually as the first\nchange in the change file).\n",
"subsections": []
},
"File: web2c.info, Node: pooltype invocation, Prev: weave invocation, Up: WEB": {
"content": "",
"subsections": [
{
"name": "9.3 Pooltype: Display WEB pool files",
"content": "Pooltype shows the so-called \"string number\" of each string in a WEB\npool file (*note WEB::), as output by Tangle (*note tangle\ninvocation::), including the first 256 strings corresponding to the\npossible input characters. Pooltype primarily serves as an example of\nWEB conventions to implementors of the TeX system. Synopsis:\n\npooltype [OPTION]... POOLFILE[.pool]\n\nNo path searching is done for POOLFILE. Output is to standard output.\n\nThe only options are '--help' and '--version' (*note Common\noptions::).\n\nAs an example of the output, here is the (edited) output for\n'tex.pool':\n0: \"^^@\"\n1: \"^^A\"\n...\n255: \"^^ff\"\n256: \"pool size\"\n...\n1314: \"Using character substitution: \"\n(23617 characters in all.)\n\nIn Metafont and MetaPost, the first 256 characters are actually\nrepresented as single bytes (i.e., themselves), not in the '^^'\nnotation. Consider Pooltype as showing the results after conversion for\noutput.\n"
}
]
},
"File: web2c.info, Node: DVI utilities, Next: Font utilities, Prev: WEB, Up: Top": {
"content": "",
"subsections": []
},
"10 DVI utilities": {
"content": "TeX outputs a file in \"DVI\" (DeVice Independent) format as a compact\nrepresentation of the original document. DVI files can be translated to\nmeet the requirements of a real physical device, such as PostScript\nprinters (*note Introduction: (dvips)Top.), PCL printers (see dvilj(1)),\nand X displays (see xdvi(1)). In fact, DVI translators are available\nfor virtually all common devices: see 'CTAN:/dviware' (for CTAN info,\n*note (kpathsea)unixtex.ftp::).\n\nFor the precise definition of the DVI file format, see (for example)\nthe source file 'web2c/dvitype.web'.\n\nThe DVI-processing programs in the Web2c distribution are not device\ndrivers; they perform generic utility functions.\n\n* Menu:\n\n* dvicopy invocation:: Expand virtual fonts.\n* dvitype invocation:: DVI to human-readable text.\n",
"subsections": []
},
"File: web2c.info, Node: dvicopy invocation, Next: dvitype invocation, Up: DVI utilities": {
"content": "",
"subsections": [
{
"name": "10.1 DVIcopy: Canonicalize virtual font references",
"content": "DVIcopy reads a DVI file, expands any references to virtual fonts (*note\n(dvips)Virtual fonts::) to base fonts, and writes the resulting DVI\nfile. Thus you can use virtual fonts even if your DVI processor does\nnot support them, by passing the documents through DVIcopy first.\nSynopsis:\n\ndvicopy [OPTION]... [INDVI[.dvi] [OUTDVI[.dvi]]]\n\nDVIcopy reads standard input if INDVI is not specified, and writes\nstandard output if OUTDVI is not specified.\n\nThe program accepts the following options, as well as the standard\n'-help' and '-version' (*note Common options::):\n'-magnification=INTEGER'\nOverride existing magnification in INDVI with INTEGER; 1000\nspecifies no magnification. This is equivalent to setting TeX's\n'\\mag' parameter.\n\n'-max-pages=N'\nProcess N pages; default is one million.\n\n'-page-start=PAGE-SPEC'\nStart at the first page matching PAGE-SPEC, which is one or more\n(signed) integers separated by periods, corresponding to TeX's\n'\\count0...9' parameters at '\\shipout' time; '*' matches anything.\nExamples: '3', '1.*.-4'.\n"
}
]
},
"File: web2c.info, Node: dvitype invocation, Prev: dvicopy invocation, Up: DVI utilities": {
"content": "",
"subsections": [
{
"name": "10.2 DVItype: Plain text transliteration of DVI files",
"content": "DVItype translates a DeVice Independent (DVI) file (as output by TeX,\nfor example) to a plain text file that humans can read. It also serves\nas a DVI-validating program, i.e., if DVItype can read a file, it's\ncorrect. Synopsis:\n\ndvitype [OPTION]... DVIFILE[.dvi]\n\nDVItype does not read any bitmap files, but it does read TFM files for\nfonts referenced in DVIFILE. The usual places are searched (*note\n(kpathsea)Supported file formats::). To see all the relevant paths, set\nthe environment variable 'KPATHSEADEBUG' to '-1' before running the\nprogram.\n\nOutput goes to standard output.\n\nThe program accepts the following options, as well as the standard\n'-help' and '-version' (*note Common options::):\n'-dpi=REAL'\nDo pixel movement calculations at REAL pixels per inch; default\n300.0.\n\n'-magnification=INTEGER'\nOverride existing magnification in INDVI with INTEGER; 1000\nspecifies no magnification. This is equivalent to setting TeX's\n'\\mag' parameter.\n\n'-max-pages=N'\nProcess N pages; default is one million.\n\n'-output-level=N'\nVerbosity level of output, from 0 to 4 (default 4):\n* 0: Global document information only.\n* 1: Most DVI commands included, and typeset characters\nsummarized.\n* 2: Character and movement commands explicitly included.\n* 3: DVI stack and current position calculations included.\n* 4: Same information as level 3, but DVItype does random\npositioning in the file, reading the DVI postamble first.\n\n'-page-start=PAGE-SPEC'\nStart at the first page matching PAGE-SPEC, which is one or more\n(signed) integers separated by periods, corresponding to TeX's\n'\\count0...9' parameters at '\\shipout' time; '*' matches anything.\nExamples: '1', '5.*.-9'.\n\n'-show-opcodes'\nShow numeric opcode values (in decimal) for DVI commands, in braces\nafter the command name. This can help in debugging DVI utilities.\nWe use decimal because in the DVI format documentation (in\n'dvitype.web', among others) the opcodes are shown in decimal.\n\n* Menu:\n\n* dvitype output example::\n"
}
]
},
"File: web2c.info, Node: dvitype output example, Up: dvitype invocation": {
"content": "",
"subsections": []
},
"As an example of the output from DVItype (see section above), here is": {
"content": "its (abridged) translation of the 'story.dvi' resulting from running the\nexample in 'The TeXbook', with '-output-level=4' and '-show-opcodes' on.\n\n...\nOptions selected:\nStarting page = *\nMaximum number of pages = 1000000\nOutput level = 4 (the works)\nResolution = 300.00000000 pixels per inch\nnumerator/denominator=25400000/473628672\nmagnification=1000; 0.00006334 pixels per DVI unit\n' TeX output 1992.05.17:0844'\nPostamble starts at byte 564.\nmaxv=43725786, maxh=30785863, maxstackdepth=3, totalpages=1\nFont 33: cmsl10---loaded at size 655360 DVI units\nFont 23: cmbx10---loaded at size 655360 DVI units\nFont 0: cmr10---loaded at size 655360 DVI units\n\n42: beginning of page 1\n87: push {141}\nlevel 0:(h=0,v=0,w=0,x=0,y=0,z=0,hh=0,vv=0)\n88: down3 -917504 {159} v:=0-917504=-917504, vv:=-58\n92: pop {142}\n...\n104: putrule {137} height 26214, width 30785863 (2x1950 pixels)\n113: down3 5185936 {159} v:=655360+5185936=5841296, vv:=370\n117: push {141}\nlevel 1:(h=0,v=5841296,w=0,x=0,y=0,z=0,hh=0,vv=370)\n118: right4 12265425 {146} h:=0+12265425=12265425, hh:=777\n[ ]\n123: fntdef1 23 {243}: cmbx10\n145: fntnum23 {194} current font is cmbx10\n146: setchar65 h:=12265425+569796=12835221, hh:=813\n147: w3 251220 {150} h:=12835221+251220=13086441, hh:=829\n151: setchar83 h:=13086441+418700=13505141, hh:=856\n...\n164: setchar82 h:=17448202+565245=18013447, hh:=1142\n165: x0 -62805 {152} h:=18013447-62805=17950642, hh:=1138\n166: setchar89 h:=17950642+569796=18520438, hh:=1174\n[A SHORT STORY]\n167: pop {142}\nlevel 1:(h=0,v=5841296,w=0,x=0,y=0,z=0,hh=0,vv=370)\n...\n550: pop {142}\nlevel 0:(h=0,v=42152922,w=0,x=0,y=0,z=0,hh=0,vv=2670)\n551: down3 1572864 {159} v:=42152922+1572864=43725786, vv:=2770\n555: push {141}\nlevel 0:(h=0,v=43725786,w=0,x=0,y=0,z=0,hh=0,vv=2770)\n556: right4 15229091 {146} h:=0+15229091=15229091, hh:=965\n561: setchar49 h:=15229091+327681=15556772, hh:=986\n[ 1]\n562: pop {142}\nlevel 0:(h=0,v=43725786,w=0,x=0,y=0,z=0,hh=0,vv=2770)\n563: eop {140}\n\nExplanation:\n\n* The DVItype options are recorded at the beginning, followed by\nglobal information about the document, including fonts used.\n\n* Each DVI command is preceded by its byte position in the file\n('42:', '87:', ...), and (because of the '-show-opcodes') followed\nby its decimal opcode value in braces ('{141}', '{142}', ...).\n\n* The 'level' lines record information about the DVI stack; 'h' and\n'v' define the current position in DVI units, while 'hh' and 'vv'\nare the same in pixels.\n\n* Text sequences are summarized in brackets, as in '[A SHORT STORY]'\nand the '[ 1]'.\n",
"subsections": []
},
"File: web2c.info, Node: Font utilities, Next: Legalisms, Prev: DVI utilities, Up: Top": {
"content": "",
"subsections": []
},
"11 Font utilities": {
"content": "",
"subsections": []
},
"The Web2c programs described here convert between various TeX-related": {
"content": "font formats; the first section below briefly describes the formats.\nGFtoPK is the only one that is routinely used, as Metafont outputs GF\nformat, but it's most efficient for device drivers to use PK.\n\nThe precise definitions of the PK, GF, TFM, PL, VF, and VPL formats\nmentioned below are in the source files that read them; 'pktype.web',\n'gftype.web', 'tftopl.web', etc.\n\n* Menu:\n\n* Font file formats:: Explanations of GF, PK, TFM, VF, ...\n* gftopk invocation:: GF -> PK (compact)\n* pktogf invocation:: PK -> GF (expand).\n* pktype invocation:: PK -> human-readable text.\n* gftype invocation:: GF -> human-readable text.\n* tftopl invocation:: TFM -> PL (for editing TFM).\n* pltotf invocation:: PL -> TFM (make editing results usable).\n* vftovp invocation:: VF -> VPL (tftopl for virtual fonts).\n* vptovf invocation:: VPL -> VF (pltotf for virtual fonts).\n* Font utilities available elsewhere:: Type 1, BDF, editors, etc.\n",
"subsections": []
},
"File: web2c.info, Node: Font file formats, Next: gftopk invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.1 Font file formats",
"content": "For another perspective on this, *note (dvips)Font concepts::.\n\nFont files come in several varieties, with suffixes like:\n.tfm .*pk .*gf .*pxl (obsolete) .pl .mf .vf .vpl\nEach represents a file format.\n\nA TFM (TeX font metric) file is a compact binary file that contains\ninformation about each character in a font, about combinations of\ncharacters within that font, and about the font as a whole. The font\nmetric information contained in TFM files is device-independent units is\nused by TeX to do typesetting. Unlike the bitmap (raster) fonts\ndescribed below, TFM font files contain no information about the shapes\nof characters. They describe rectangular areas and combinations\nthereof, but not what will eventually be printed in those areas.\n\nSince TeX does scaling calculations, one TFM file serves for all\nmagnifications of a given typeface. On the other hand, the best printed\nresults are obtained when magnified (or reduced fonts) are not produced\ngeometrically (as done by PostScript, for example) but rather optically,\nwith each size a separate design (as done with Computer Modern and the\nEC fonts, for example); then a separate TFM file is needed for each\nsize.\n\nAt any rate, TeX produces a DVI (DeVice Independent) file from your\nsource document. In order to print DVI files on real devices, you need\nfont files defining digitized character shapes and other data. Then\npreviewers and printer-driver programs can translate your DVI files into\nsomething usable by your monitor or printer. Bitmap fonts come with\nsuffixes such as '.600pk' or '.600gf' or '.3000pxl', where the '600' is\nthe horizontal dots-per-inch resolution at which the font was produced,\nand the 'pk' or 'gf' or 'pxl' indicates the font format. Outline fonts\nin PostScript Type 1 format have suffixes such as '.pfa' or '.pfb'.\n\nFonts in pk (packed) format are in the tightly packed raster format\nthat is pretty much the standard today. They take up less space than\nfonts in the gf (generic font) format that Metafont generates, and far\nless space than fonts in pxl format. Fonts in pxl format take up gross\namounts of disk space and permit only 128 characters. They are\nobsolete.\n\nFont files with the '.pl' (property list) suffix are the plain text\n(human-readable) analog of the binary '.tfm' files. The TFtoPL and\nPLtoTF programs convert between the two formats (*note tftopl\ninvocation:: and *note pltotf invocation::).\n\nFont files with the '.mf' suffix are in Metafont source format."
}
]
},
"These are the files used by Metafont to generate rastered fonts for": {
"content": "specific typefaces at specific magnifications for the specific\nresolution and type of mapping used by your device.\n\nThe suffix '.vf' identifies \"virtual font\" files, for which '.vpl' is\nthe human-readable analog. See *Note vftovp invocation::, and *note\nvptovf invocation::. For further discussion of virtual fonts, see\n'CTAN:/doc/virtual-fonts.knuth', 'CTAN:/help/virtualfonts.txt', and\n*note (dvips)Virtual fonts::.\n\n(This section is based on documentation in the original Unix TeX\ndistribution by Pierre MacKay and Elizabeth Tachikawa.)\n",
"subsections": []
},
"File: web2c.info, Node: gftopk invocation, Next: pktogf invocation, Prev: Font file formats, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.2 GFtoPK: Generic to packed font conversion",
"content": "GFtoPK converts a generic font (GF) file output by, for example,\nMetafont (*note mf invocation::) to a packed font (PK) file. PK files\nare considerably smaller than the corresponding gf files, so they are\ngenerally the bitmap font format of choice. Some DVI-processing\nprograms, notably Dvips, only support PK files and not GF files.\nSynopsis:\n\ngftopk [OPTION]... GFNAME.DPI[gf] [PKFILE]\n\nThe font GFNAME is searched for in the usual places (*note\n(kpathsea)Glyph lookup::). To see all the relevant paths, set the\nenvironment variable 'KPATHSEADEBUG' to '-1' before running the\nprogram.\n\nThe suffix 'gf' is supplied if not already present. This suffix is\nnot an extension; no '.' precedes it: for instance, 'cmr10.600gf'.\n\nIf PKFILE is not specified, the output is written to the basename of\n'GFNAME.DPIpk', e.g., 'gftopk /wherever/cmr10.600gf' creates\n'./cmr10.600pk'.\n\nThe only options are '--verbose', '--help', and '--version' (*note\nCommon options::).\n"
}
]
},
"File: web2c.info, Node: pktogf invocation, Next: pktype invocation, Prev: gftopk invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.3 PKtoGF: Packed to generic font conversion",
"content": "PKtoGF converts a packed font (PK) file to a generic font (GF) file."
}
]
},
"Since PK format is much more compact than GF format, the most likely": {
"content": "reason to do this is to run GFtype (*note gftype invocation::) on the\nresult, so you can see the bitmap images. Also, a few old utility\nprograms do not support PK format. Synopsis:\n\npktogf [OPTION]... PKNAME.DPI[pk] [GFFILE]\n\nThe font PKNAME is searched for in the usual places (*note\n(kpathsea)Glyph lookup::). To see all the relevant paths, set the\nenvironment variable 'KPATHSEADEBUG' to '-1' before running the\nprogram.\n\nThe suffix 'pk' is supplied if not already present. This suffix is\nnot an extension; no '.' precedes it: for instance, 'cmr10.600pk'.\n\nIf GFFILE is not specified, the output is written to the basename of\n'PKNAME.DPIgf', e.g., 'pktogf /wherever/cmr10.600pk' creates\n'./cmr10.600gf'.\n\nThe only options are '--verbose', '--help', and '--version' (*note\nCommon options::).\n",
"subsections": []
},
"File: web2c.info, Node: pktype invocation, Next: gftype invocation, Prev: pktogf invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.4 PKtype: Plain text transliteration of packed fonts",
"content": "PKtype translates a packed font (PK) bitmap file (as output by GFtoPK,\nfor example) to a plain text file that humans can read. It also serves\nas a PK-validating program, i.e., if PKtype can read a file, it's\ncorrect. Synopsis:\n\npktype PKNAME.DPI[pk]\n\nThe font PKNAME is searched for in the usual places (*note\n(kpathsea)Glyph lookup::). To see all the relevant paths, set the\nenvironment variable 'KPATHSEADEBUG' to '-1' before running the\nprogram.\n\nThe suffix 'pk' is supplied if not already present. This suffix is\nnot an extension; no '.' precedes it: for instance, 'cmr10.600pk'.\n\nThe translation is written to standard output.\n\nThe only options are '-help' and '-version' (*note Common options::).\n\nAs an example of the output, here is the (abridged) translation of\nthe letter 'K' in 'cmr10', as rendered at 600dpi with the mode 'ljfour'\nfrom (available from 'ftp://ftp.tug.org/tex/modes.mf').\n\n955: Flag byte = 184 Character = 75 Packet length = 174\nDynamic packing variable = 11\nTFM width = 815562 dx = 4259840\nHeight = 57 Width = 57 X-offset = -3 Y-offset = 56\n[2]23(16)17(8)9(25)11(13)7(27)7(16)7(28)4(18)7(28)2(20)7(27)...\n...\n(14)9(24)12(5)[2]23(13)21\n\nExplanation:\n\n'955'\nThe byte position in the file where this character starts.\n\n'Flag byte'\n'Dynamic packing variable'\nRelated to the packing for this character; see the source code.\n\n'Character'\nThe character code, in decimal.\n\n'Packet length'\nThe total length of this character definition, in bytes.\n\n'TFM width'\nThe device-independent (TFM) width of this character. It is 2^24\ntimes the ratio of the true width to the font's design size.\n\n'dx'\nThe device-dependent width, in \"scaled pixels\", i.e., units of\nhorizontal pixels times 2^16.\n\n'Height'\n'Width'\nThe bitmap height and width, in pixels.\n\n'X-offset'\n'Y-offset'\nHorizontal and vertical offset from the upper left pixel to the\nreference (origin) pixel for this character, in pixels (right and\ndown are positive). The \"reference pixel\" is the pixel that\noccupies the unit square in Metafont; the Metafont reference point\nis the lower left hand corner of this pixel. Put another way, the\nx-offset is the negative of the left side bearing; the right side\nbearing is the horizontal escapement minus the bitmap width plus\nthe x-offset.\n\n'[2]23(16)...'\nFinally, run lengths of black pixels alternate with parenthesized\nrun lengths of white pixels, and brackets indicate a repeated row.\n"
}
]
},
"File: web2c.info, Node: gftype invocation, Next: tftopl invocation, Prev: pktype invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.5 GFtype: Plain text transliteration of generic fonts",
"content": "GFtype translates a generic font (GF) bitmap file (as output by"
}
]
},
"Metafont, for example) to a plain text file that humans can read. It": {
"content": "also serves as a GF-validating program, i.e., if GFtype can read a file,\nit's correct. Synopsis:\n\ngftype [OPTION]... GFNAME.DPI[gf]\n\nThe font GFNAME is searched for in the usual places (*note\n(kpathsea)Glyph lookup::). To see all the relevant paths, set the\nenvironment variable 'KPATHSEADEBUG' to '-1' before running the\nprogram.\n\nThe suffix 'gf' is supplied if not already present. This suffix is\nnot an extension; no '.' precedes it: for instance, 'cmr10.600gf'.\n\nThe translation is written to standard output.\n\nThe program accepts the following options, as well as the standard\n'-help' and '-version' (*note Common options::):\n'-images'\nShow the characters' bitmaps using asterisks and spaces.\n\n'-mnemonics'\nTranslate all commands in the GF file.\n\nAs an example of the output, here is the (abridged) translation of\nthe letter 'K' in 'cmr10', as rendered at 600dpi with the mode 'ljfour'\nfrom 'modes.mf' (available from ), with\nboth '-mnemonics' and '-images' enabled.\n\nGFtype outputs the information about a character in two places: a\nmain definition and a one-line summary at the end. We show both. Here\nis the main definition:\n\n2033: beginning of char 75: 3<=m<=60 0<=n<=56\n(initially n=56) paint (0)24(12)20\n2043: newrow 0 (n=55) paint 24(12)20\n2047: newrow 0 (n=54) paint 24(12)20\n2051: newrow 0 (n=53) paint 24(12)20\n2055: newrow 7 (n=52) paint 10(21)13\n2059: newrow 8 (n=51) paint 8(23)9\n...\n2249: newrow 8 (n=5) paint 8(23)11\n2253: newrow 7 (n=4) paint 10(22)12\n2257: newrow 0 (n=3) paint 24(11)22\n2261: newrow 0 (n=2) paint 24(11)22\n2265: newrow 0 (n=1) paint 24(11)22\n2269: newrow 0 (n=0) paint 24(11)22\n2273: eoc\n.<--This pixel's lower left corner is at (3,57) in METAFONT coordinates\n\n\n\n\n*\n*\n...\n*\n\n\n\n\n\n.<--This pixel's upper left corner is at (3,0) in METAFONT coordinates\n\nExplanation:\n\n'2033'\n'2043'\n'...'\nThe byte position in the file where each GF command starts.\n\n'beginning of char 75'\nThe character code, in decimal.\n\n'3<=m<=60 0<=n<=56'\nThe character's bitmap lies between 3 and 60 (inclusive)\nhorizontally, and between 0 and 56 (inclusive) vertically. (m is a\ncolumn position and n is a row position.) Thus, 3 is the left side\nbearing. The right side bearing is the horizontal escapement\n(given below) minus the maximum m.\n\n'(initially n=56) paint (0)24(12)20'\nThe first row of pixels: 0 white pixels, 24 black pixels, 12 white\npixels, etc.\n\n'newrow 0 (n=55) paint 24(12)20'\nThe second row of pixels, with zero leading white pixels on the\nrow.\n\n'eoc'\nThe end of the main character definition.\n\nHere is the GF postamble information that GFtype outputs at the end:\n\nCharacter 75: dx 4259840 (65), width 815562 (64.57289), loc 2033\n\nExplanation:\n\n'dx'\nThe device-dependent width, in \"scaled pixels\", i.e., units of\nhorizontal pixels times 2^16. The '(65)' is simply the same number\nrounded. If the vertical escapement is nonzero, it would appear\nhere as a 'dy' value.\n\n'width'\nThe device-independent (TFM) width of this character. It is 2^24\ntimes the ratio of the true width to the font's design size. The\n'64.57289' is the same number converted to pixels.\n\n'loc'\nThe byte position in the file where this character starts.\n",
"subsections": []
},
"File: web2c.info, Node: tftopl invocation, Next: pltotf invocation, Prev: gftype invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.6 TFtoPL: TeX font metric to property list conversion",
"content": "TFtoPL translates a TeX font metric (TFM, *note (dvips)Metric files::)\nfile (as output by Metafont, for example) to \"property list format\" (a\nlist of parenthesized items describing the font) that humans can edit or\nread. This program is mostly used by people debugging TeX\nimplementations, writing font utilities, etc. Synopsis:\n\ntftopl [OPTION]... TFMNAME[.tfm] [PLFILE[.pl]]\n\nThe font TFMNAME (extended with '.tfm' if necessary) is searched for\nin the usual places (*note (kpathsea)Supported file formats::). To see\nall the relevant paths, set the environment variable 'KPATHSEADEBUG' to\n'-1' before running the program.\n\nIf PLFILE (which is extended with '.pl' if necessary) is not\nspecified, the property list file is written to standard output. The\nproperty list file can be converted back to TFM format by the companion\nprogram TFtoPL (see the next section).\n\nThe program accepts the following option, as well as the standard\n'-verbose', '-help' and '-version' (*note Common options::):\n'-charcode-format=TYPE'\nOutput character codes in the PL file according to TYPE: either\n'octal' or 'ascii'. Default is 'ascii' for letters and digits,\noctal for all other characters. Exception: if the font's coding\nscheme starts with 'TeX math sy' or 'TeX math ex', all character\ncodes are output in octal.\n\nIn 'ascii' format, character codes that correspond to graphic\ncharacters, except for left and right parentheses, are output as a\n'C' followed by the single character: 'C K', for example. In octal\nformat, character codes are output as the letter 'O' followed by\noctal digits, as in 'O 113' for 'K'.\n\n'octal' format is useful for symbol and other non-alphabetic fonts,\nwhere using ASCII characters for the character codes is merely\nconfusing.\n\nAs an example of the output, here is the (abridged) property list\ntranslation of 'cmr10.tfm':\n\n(FAMILY CMR)\n(FACE O 352)\n(CODINGSCHEME TEX TEXT)\n(DESIGNSIZE R 10.0)\n(COMMENT DESIGNSIZE IS IN POINTS)\n(COMMENT OTHER SIZES ARE MULTIPLES OF DESIGNSIZE)\n(CHECKSUM O 11374260171)\n(FONTDIMEN\n(SLANT R 0.0)\n(SPACE R 0.333334)\n(STRETCH R 0.166667)\n(SHRINK R 0.111112)\n(XHEIGHT R 0.430555)\n(QUAD R 1.000003)\n(EXTRASPACE R 0.111112)\n)\n(LIGTABLE\n...\n(LABEL C f)\n(LIG C i O 14)\n(LIG C f O 13)\n(LIG C l O 15)\n(KRN O 47 R 0.077779)\n(KRN O 77 R 0.077779)\n(KRN O 41 R 0.077779)\n(KRN O 51 R 0.077779)\n(KRN O 135 R 0.077779)\n(STOP)\n...\n)\n...\n(CHARACTER C f\n(CHARWD R 0.305557)\n(CHARHT R 0.694445)\n(CHARIC R 0.077779)\n(COMMENT\n(LIG C i O 14)\n(LIG C f O 13)\n(LIG C l O 15)\n(KRN O 47 R 0.077779)\n(KRN O 77 R 0.077779)\n...\n)\n)\n...\n\nAs you can see, the general format is a list of parenthesized\n\"properties\", nested where necessary.\n\n* The first few items ('FAMILY', 'FACE', and so on) are the so-called\n\"headerbyte\" information from Metafont, giving general information\nabout the font.\n\n* The 'FONTDIMEN' property defines the TeX '\\fontdimen' values.\n\n* The 'LIGTABLE' property defines the ligature and kerning table.\n'LIG' properties define ligatures: in the example above, an 'f' (in\nthe 'LABEL') followed by an 'i' is a ligature, i.e., a typesetting\nprogram like TeX replaces those two consecutive characters by the\ncharacter at position octal '014 in the current font--presumably\nthe 'fi' ligature. 'KRN' properties define kerns: if an 'f' is\nfollowed by character octal '047 (an apostrophe), TeX inserts a\nsmall amount of space between them: 0.077779 times the design size\nthe font was loaded at (about three-quarters of a printer's point\nby default in this case, or .001 inches).\n\n* The 'CHARACTER' property defines the dimensions of a character: its\nwidth, height, depth, and italic correction, also in design-size\nunits, as explained in the previous item. For our example 'f', the\ndepth is zero, so that property is omitted. TFtoPL also inserts\nany kerns and ligatures for this character as a comment.\n"
}
]
},
"File: web2c.info, Node: pltotf invocation, Next: vftovp invocation, Prev: tftopl invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.7 PLtoTF: Property list to TeX font metric conversion",
"content": "PLtoTF translates a property list file (as output by TFtoPL, for\nexample) to TeX font metric (TFM, *note (dvips)Metric files::) format."
}
]
},
"It's much easier for both programs and humans to create the (plain text)": {
"content": "property list files and let PLtoTF take care of creating the binary TFM\nequivalent than to output TFM files directly. Synopsis:\n\npltotf [OPTION]... PLFILE[.pl] [TFMFILE[.tfm]]\n\nIf TFMFILE (extended with '.tfm' if necessary) is not specified, the\nTFM file is written to the basename of 'PLFILE.tfm', e.g., 'pltotf\n/wherever/cmr10.pl' creates './cmr10.tfm'. (Since TFM files are binary,\nwriting to standard output by default is undesirable.)\n\nThe only options are '-verbose', '-help', and '-version' (*note\nCommon options::).\n\nFor an example of property list format, see the previous section.\n",
"subsections": []
},
"File: web2c.info, Node: vftovp invocation, Next: vptovf invocation, Prev: pltotf invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.8 VFtoVP: Virtual font to virtual property lists",
"content": "VFtoVP translates a virtual font metric (VF, *note (dvips)Virtual\nfonts::) file and its accompanying TeX font metric (TFM, *note\n(dvips)Metric files::) file (as output by VPtoVF, for example) to\n\"virtual property list format\" (a list of parenthesized items describing\nthe virtual font) that humans can edit or read. This program is mostly\nused by people debugging virtual font utilities. Synopsis:\n\nvftovp [OPTION]... VFNAME[.vf] [TFMNAME[.tfm] [VPLFILE[.vpl]]]\n\nThe fonts VFNAME and TFMNAME (extended with '.vf' and '.tfm' if\nnecessary) are searched for in the usual places (*note\n(kpathsea)Supported file formats::). To see all the relevant paths, set\nthe environment variable 'KPATHSEADEBUG' to '-1' before running the\nprogram. If TFMNAME is not specified, VFNAME (without a trailing '.vf')\nis used.\n\nIf VPLFILE (extended with '.vpl' if necessary) is not specified, the\nproperty list file is written to standard output. The property list\nfile can be converted back to VF and TFM format by the companion program\nVFtoVP (see the next section).\n\nThe program accepts the following option, as well as the standard\n'-verbose', '-help' and '-version' (*note Common options::):\n'-charcode-format=TYPE'\nOutput character codes in the PL file according to TYPE: either\n'octal' or 'ascii'. Default is 'ascii' for letters and digits,\noctal for all other characters. Exception: if the font's coding\nscheme starts with 'TeX math sy' or 'TeX math ex', all character\ncodes are output in octal.\n\nIn 'ascii' format, character codes that correspond to graphic\ncharacters, except for left and right parentheses, are output as a\n'C' followed by the single character: 'C K', for example. In octal\nformat, character codes are output as the letter 'O' followed by\noctal digits, as in 'O 113' for 'K'.\n\n'octal' format is useful for symbol and other non-alphabetic fonts,\nwhere using ASCII characters for the character codes is merely\nconfusing.\n"
}
]
},
"File: web2c.info, Node: vptovf invocation, Next: Font utilities available elsewhere, Prev: vftovp invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.9 VPtoVF: Virtual property lists to virtual font",
"content": "VPtoVF translates a virtual property list file (as output by VFtoVP, for\nexample) to virtual font (VF, *note (dvips)Virtual fonts::) and TeX font\nmetric (TFM, *note (dvips)Metric files::) files. It's much easier for\nboth programs and humans to create the (plain text) property list files\nand let VPtoVF take care of creating the binary VF and TFM equivalents\nthan to output them directly. Synopsis:\n\nvptovf [OPTION]... VPLFILE[.vpl] [VFFILE[.vf] [TFMFILE[.tfm]]]\n\nIf VFFILE (extended with '.vf' if necessary) is not specified, the VF\noutput is written to the basename of 'VPLFILE.vf'; similarly for\nTFMFILE. For example, 'vptovf /wherever/ptmr.vpl' creates './ptmr.vf'\nand './ptmr.tfm'.\n\nThe only options are '-verbose', '-help', and '-version' (*note\nCommon options::).\n"
}
]
},
"File: web2c.info, Node: Font utilities available elsewhere, Prev: vptovf invocation, Up: Font utilities": {
"content": "",
"subsections": [
{
"name": "11.10 Font utilities available elsewhere",
"content": ""
}
]
},
"The Web2c complement of font utilities merely implements a few basic": {
"content": "conversions. Many other more sophisticated font utilities exist; most\nare in 'CTAN:/fonts/utilities' (for CTAN info, *note\n(kpathsea)unixtex.ftp::). Here are some of the most commonly-requested\nitems:\n\n* AFM (Adobe font metric) to TFM conversion: *note (dvips)Invoking\nafm2tfm::, and 'CTAN:/fonts/utilities/afmtopl'.\n\n* BDF (the X bitmap format) conversion:\n.\n\n* Creating fonts using MetaPost: MetaType1.\n. This is used to create the\nexcellent Latin Modern font family ('CTAN:/fonts/lm'), which\nextends Computer Modern to a vast repertoire of scripts.\n\n* Editing of bitmap fonts: Xbfe from the GNU font utilities mentioned\nbelow; the X BDF-editing programs available from\n and\n; and finally, if your\nfonts have only 128 characters, you can use the old 'gftopxl',\n'pxtoch', and 'chtopx' programs from .\n\n* Editing of outline fonts: FontForge, .\nThis is a very elaborate program with support for many outline\nformats (Type 1, OpenType, TrueType, ...), and many advanced font\nediting features.\n\n* PK bitmaps from PostScript outline fonts: gsftopk from the 'xdvi'\ndistribution. Alternatively, 'ps2pk', from\n'CTAN:/fonts/utilities/ps2pk'.\n\n* PostScript Type 1 font format conversion (i.e., between PFA and PFB\nformats): .\n\n* Tracing bitmaps to fitted outlines: Autotrace\n(), Potrace\n(). For Metafont fonts, either of\nthe two programs 'mftrace' ()\nor 'textrace' () make the job\neasier.\n\n* Virtual font creation: .\n",
"subsections": []
},
"File: web2c.info, Node: Legalisms, Next: References, Prev: Font utilities, Up: Top": {
"content": "",
"subsections": []
},
"Appendix A Legalisms": {
"content": "",
"subsections": []
},
"In general, each file has its own copyright notice stating the copying": {
"content": "permissions for that file. Following is a summary.\n\nThe Stanford TeX programs and Web2c system itself are in the public\ndomain (). The sources may be\ncopied verbatim, or used as the starting point of new software under\ndifferent names; however, per the wishes of the authors, they should be\nmodified only through a '.ch' file, but this is in the nature of a\ndevelopment request rather than a legal requirement.\n\nMLTeX, pdfTeX, LuaTeX, XeTeX, and all the other derived engines have\nused various license terms for their additions to the base code, often\nthe GPL (see ) or (for example) the\nfile 'web2c/pdftexdir/COPYINGv2'. They also mostly make use of\nadditional libraries with their own (compatible) terms. Please see each\nprogram's sources.\n\nThe Kpathsea library is covered by the GNU Lesser General Public\nLicense (*note (kpathsea)Introduction::). Therefore, the binaries\nresulting from a standard Web2c compilation are also covered by the\nLGPL; so if you (re)distribute the binaries, you must also (offer to)\ndistribute the complete source that went into those binaries. See\n or the file\n'kpathsea/COPYING.LESSERv2'.\n",
"subsections": []
},
"File: web2c.info, Node: References, Next: Index, Prev: Legalisms, Up: Top": {
"content": "",
"subsections": []
},
"Appendix B References": {
"content": "1. Kpathsea: *Note Introduction: (kpathsea)Top.\n\n2. Dvips and Afm2tfm: *Note Introduction: (dvips)Top.\n\n3. The TeX Users Group: . For an introduction to the\nTeX system, see .\n\n4. TUGboat, the principal journal for the TeX world:\n.\n\n5. TeX and computer typesetting in general:\n.\n\n6. For a bibliography of formal articles and technical reports on the\nTeX project, see the books 'TeX: The Program' or 'Metafont: The\nProgram' cited below.\n\n7. [Bil87] Neenie Billawala. Write-white printing engines and tuning\nfonts with Metafont. 'TUGboat', 8(1):29-32, April 1987.\n.\n\n8. [Hob89] John D. Hobby. A Metafont-like system with PS output.\n'TUGboat', 10(4):505-512, December 1989.\n.\n\n9. [Hob92] John D. Hobby. A User's Manual for MetaPost. Technical\nReport CSTR-162, AT&T Bell Laboratories, 1992.\n\n10. [Hob93] John D. Hobby. Drawing Graphs with MetaPost. Technical\nReport CSTR-164, AT&T Bell Laboratories, 1993.\n\n11. [HS91] Samuel P. Harbison and Guy L. Steele Jr. 'C--A Reference\nManual'. Prentice-Hall, Upper Saddle River, NJ 07458, USA, third\nedition, 1991. An authoritative reference to the C programming\nlanguage, and a good companion to Kernighan and Ritchie.\n\n12. [KL93] Donald E. Knuth and Silvio Levy. 'The CWEB System of\nStructured Documentation, Version 3.0'. Addison-Wesley, Reading,\nMA, USA, 1993. .\n\n13. [Knu84] Donald E. Knuth. A torture test for TeX. Report No.\nSTAN-CS-84-1027, Stanford University, Department of Computer\nScience, 1984.\n\n14. [Knu86a] Donald E. Knuth. A Torture Test for METAFONT. Report No.\nSTAN-CS-86-1095, Stanford University, Department of Computer\nScience, 1986.\n\n15. [Knu86b] Donald E. Knuth. 'The TeXbook', volume A of 'Computers\nand Typesetting'. Addison-Wesley, Reading, MA, USA, 1986.\n\n16. [Knu86c] Donald E. Knuth. 'TeX: The Program', volume B of\n'Computers and Typesetting'. Addison-Wesley, Reading, MA, USA,\n1986.\n\n17. [Knu86d] Donald E. Knuth. 'The METAFONTbook', volume C of\n'Computers and Typesetting'. Addison-Wesley, Reading, MA, USA,\n1986.\n\n18. [Knu86e] Donald E. Knuth. 'METAFONT: The Program', volume D of\n'Computers and Typesetting'. Addison-Wesley, Reading, MA, USA,\n1986.\n\n19. [Knu86f] Donald E. Knuth. 'Computer Modern Typefaces', volume E\nof 'Computers and Typesetting'. Addison-Wesley, Reading, MA, USA,\n1986.\n\n20. [Knu89] Donald E. Knuth. The errors of TeX. 'Software--Practice\nand Experience', 19(7):607-681, July 1989. This is an updated\nversion of Knuth:1988:ET.\n\n21. [Knu90] Donald Knuth. Virtual Fonts: More Fun for Grand Wizards.\n'TUGboat', 11(1):13-23, April 1990.\n.\n\n22. [Knu92] Donald E. Knuth. 'Literate Programming'. CSLI Lecture\nNotes Number 27. Stanford University Center for the Study of\nLanguage and Information, Stanford, CA, USA, 1992.\n\n23. [Lam94] Leslie Lamport. 'LaTeX: A Document Preparation System:\nUser's Guide and Reference Manual'. Addison-Wesley, Reading, MA,\nUSA, second edition, 1994. Reprinted with corrections, 1996.\n\n24. [Lia83] Franklin Mark Liang. Word hy-phen-a-tion by com-put-er.\nTechnical Report STAN-CS-83-977, Stanford University, August 1983.\n.\n\n25. [Mac91] Pierre A. MacKay. Looking at the pixels: Quality control\nfor 300 dpi laser printer fonts, especially Metafonts. In Robert\nA. Morris and Jacques Andre, editors, 'Raster Imaging and Digital\nTypography II--Papers from the second RIDT meeting, held in Boston,\nOct. 14-16, 1991', pages 205-215, New York, 1991. Cambridge\nUniversity Press.\n",
"subsections": []
},
"File: web2c.info, Node: Index, Prev: References, Up: Top": {
"content": "",
"subsections": []
},
"Index": {
"content": "* Menu:\n\n* \" character, ignored in filenames: \\input filenames. (line 22)\n* #define options: Compile-time options.\n(line 6)\n* $ expansion in filenames: \\input filename caveats.\n(line 17)\n* %& magic number: Determining the memory dump to use.\n(line 19)\n* - starting a filename: Option conventions. (line 19)\n* - starts option names: Option conventions. (line 11)\n* -- starts option names: Option conventions. (line 11)\n* --disable-dump-share configure option: Hardware and memory dumps.\n(line 17)\n* --disable-mf-nowin: Online Metafont graphics.\n(line 65)\n* --enable-epsfwin: Online Metafont graphics.\n(line 20)\n* --enable-hp2627win: Online Metafont graphics.\n(line 28)\n* --enable-ipc configure option: tex invocation. (line 93)\n* --enable-mftalkwin: Online Metafont graphics.\n(line 31)\n* --enable-next: Online Metafont graphics.\n(line 35)\n* --enable-regiswin: Online Metafont graphics.\n(line 40)\n* --enable-suntoolswin: Online Metafont graphics.\n(line 43)\n* --enable-tektronixwin: Online Metafont graphics.\n(line 48)\n* --enable-unitermwin: Online Metafont graphics.\n(line 51)\n* --help common option: Common options. (line 11)\n* --verbose common option: Common options. (line 15)\n* --version common option: Common options. (line 18)\n* --with-editor=CMD: Editor invocation. (line 10)\n* --with-mf-x-toolkit=KIT: Online Metafont graphics.\n(line 59)\n* --with-x: Online Metafont graphics.\n(line 57)\n* -8bit: Common options. (line 110)\n* -base=BASE: Determining the memory dump to use.\n(line 15)\n* -base=DUMPNAME: Common options. (line 39)\n* -change=CHFILE: mft invocation. (line 63)\n* -charcode-format=TYPE: tftopl invocation. (line 27)\n* -charcode-format=TYPE <1>: vftovp invocation. (line 30)\n* -cnf-line: Common options. (line 25)\n* -D compiler options: Compile-time options.\n(line 6)\n* -disable-write18: tex invocation. (line 128)\n* -dpi=REAL: dvitype invocation. (line 24)\n* -enable-write18: tex invocation. (line 127)\n* -enc: tex invocation. (line 86)\n* -file-line-error: Common options. (line 30)\n* -file-line-error-style: Common options. (line 31)\n* -fmt=DUMPNAME: Common options. (line 39)\n* -fmt=FMT: Determining the memory dump to use.\n(line 15)\n* -geometry, supported with Xt: Online Metafont graphics.\n(line 69)\n* -halt-on-error: Common options. (line 46)\n* -images: gftype invocation. (line 26)\n* -ini: Common options. (line 50)\n* -ini <1>: Initial and virgin. (line 10)\n* -interaction=STRING: Common options. (line 55)\n* -ipc: tex invocation. (line 93)\n* -ipc-start: tex invocation. (line 93)\n* -jobname=STRING: Common options. (line 60)\n* -kpathsea-debug=NUMBER: Common options. (line 64)\n* -length=NUMBER: tangle invocation. (line 27)\n* -loose: tangle invocation. (line 46)\n* -lowercase: tangle invocation. (line 35)\n* -magnification=INTEGER: dvicopy invocation. (line 20)\n* -magnification=INTEGER <1>: dvitype invocation. (line 28)\n* -max-pages=N: dvicopy invocation. (line 25)\n* -max-pages=N <1>: dvitype invocation. (line 33)\n* -mem=DUMPNAME: Common options. (line 39)\n* -min-crossrefs=N: bibtex invocation. (line 31)\n* -mixedcase: tangle invocation. (line 35)\n* -mktex=FILETYPE: tex invocation. (line 103)\n* -mktex=FILETYPE <1>: mf invocation. (line 87)\n* -mltex: tex invocation. (line 108)\n* -mnemonics: gftype invocation. (line 29)\n* -no-file-line-error: Common options. (line 31)\n* -no-mktex=FILETYPE: tex invocation. (line 103)\n* -no-mktex=FILETYPE <1>: mf invocation. (line 87)\n* -no-parse-first-line: Common options. (line 77)\n* -no-shell-escape: tex invocation. (line 121)\n* -output-comment=STRING: tex invocation. (line 113)\n* -output-directory: Common options. (line 71)\n* -output-directory <1>: Output file location.\n(line 15)\n* -output-level=N: dvitype invocation. (line 36)\n* -overflow-label-offset=POINTS: gftodvi invocation. (line 59)\n* -page-start=PAGE-SPEC: dvicopy invocation. (line 28)\n* -page-start=PAGE-SPEC <1>: dvitype invocation. (line 46)\n* -parse-first-line: Common options. (line 76)\n* -progname=STRING: Common options. (line 82)\n* -progname=STRING <1>: Determining the memory dump to use.\n(line 17)\n* -recorder: Common options. (line 89)\n* -shell-escape: tex invocation. (line 120)\n* -shell-restricted: tex invocation. (line 122)\n* -show-opcodes: dvitype invocation. (line 52)\n* -strict: tangle invocation. (line 46)\n* -style=MFTFILE: mft invocation. (line 67)\n* -T: mpost invocation. (line 111)\n* -terse: bibtex invocation. (line 28)\n* -tex=TEXPROGRAM: mpost invocation. (line 114)\n* -translate-file=TCXFILE: Common options. (line 103)\n* -troff: mpost invocation. (line 111)\n* -underline: tangle invocation. (line 41)\n* -uppercase: tangle invocation. (line 35)\n* -x: weave invocation. (line 22)\n* ., used for output: Output file location.\n(line 6)\n* .2602gf: mf invocation. (line 48)\n* .aux cross-reference files: bibtex invocation. (line 6)\n* .base: Initial Metafont. (line 6)\n* .bbl bibliography files: bibtex invocation. (line 6)\n* .bib bibliography databases: bibtex invocation. (line 6)\n* .blg BibTeX log file: bibtex invocation. (line 14)\n* .fmt: Initial TeX. (line 6)\n* .mf: mf invocation. (line 24)\n* .mp: mpost invocation. (line 26)\n* .mps files and PDF: mpost invocation. (line 82)\n* .NNN PostScript figures: mpost invocation. (line 31)\n* .NNNgf generic fonts: mf invocation. (line 34)\n* .tcx character translation files: Common options. (line 103)\n* .tcx character translation files <1>: TCX files. (line 6)\n* .tex: tex invocation. (line 20)\n* .tfm output: mf invocation. (line 43)\n* .tfm output <1>: mpost invocation. (line 31)\n* .Xdefaults: Online Metafont graphics.\n(line 69)\n* .Xresources: Online Metafont graphics.\n(line 69)\n* 2602gf: mf invocation. (line 48)\n* 32-bit architecture: Hardware and memory dumps.\n(line 6)\n* 64-bit architecture: Hardware and memory dumps.\n(line 6)\n* 8 bit clean: Common options. (line 110)\n* 8 bit clean output, specifying: Common options. (line 110)\n* 8-bit characters: TCX files. (line 6)\n* \\bibliography: bibtex invocation. (line 18)\n* \\bibliographystyle: bibtex invocation. (line 18)\n* \\charsubdef and MLTeX: \\charsubdef. (line 6)\n* \\countN: dvicopy invocation. (line 28)\n* \\countN <1>: dvitype invocation. (line 46)\n* \\font and dynamic generation: tex invocation. (line 41)\n* \\fontdimen: tftopl invocation. (line 99)\n* \\immediate\\write18: Shell escapes. (line 6)\n* \\input braced (grouped) filename: \\input braced filename.\n(line 6)\n* \\input filename caveats: \\input filename caveats.\n(line 6)\n* \\input filenames: \\input filenames. (line 6)\n* \\input quoted filename: \\input quoted filename.\n(line 6)\n* \\input, and pipes: Shell escapes. (line 64)\n* \\mag: dvicopy invocation. (line 20)\n* \\mag <1>: dvitype invocation. (line 28)\n* \\openin, and pipes: Shell escapes. (line 64)\n* \\openout and security: tex invocation. (line 48)\n* \\openout, and pipes: Shell escapes. (line 64)\n* \\output routine, and \\write: Shell escapes. (line 28)\n* \\pdfshellescape: Shell escapes. (line 64)\n* \\string, and \\input filenames: \\input filename caveats.\n(line 29)\n* \\tracingcharsubdef and MLTeX: \\tracingcharsubdef. (line 6)\n* \\tracinglostchars and MLTeX: \\tracingcharsubdef. (line 11)\n* \\write18 shell escape extension: Shell escapes. (line 6)\n* ^^ notation, avoiding: TCX files. (line 87)\n* ~ expansion in filenames: \\input filename caveats.\n(line 17)\n* abbrv.bst: Basic BibTeX style files.\n(line 16)\n* accented character: TCX files. (line 6)\n* accents, hyphenating words with: MLTeX. (line 6)\n* acknowledgements: Introduction. (line 63)\n* acm.bst: Basic BibTeX style files.\n(line 19)\n* Ada, WEB for: WEB. (line 12)\n* additional Make targets: Additional targets. (line 6)\n* AFM to TFM conversion: Font utilities available elsewhere.\n(line 12)\n* afm2tfm: Font utilities available elsewhere.\n(line 12)\n* afmtopl: Font utilities available elsewhere.\n(line 12)\n* Aleph: TeX extensions. (line 25)\n* aliases for fonts: Path searching. (line 14)\n* alpha.bst: Basic BibTeX style files.\n(line 22)\n* American Mathematical Society, typesetting system: Formats. (line 35)\n* AMSTeX: Formats. (line 35)\n* apalike.bst: Basic BibTeX style files.\n(line 25)\n* architecture dependencies: Hardware and memory dumps.\n(line 6)\n* array limit, fixed: Runtime options. (line 45)\n* array sizes: Runtime options. (line 6)\n* assembly language routines: Compile-time options.\n(line 21)\n* autotrace: Font utilities available elsewhere.\n(line 42)\n* Awk, WEB for: WEB. (line 12)\n* base file, determining: Determining the memory dump to use.\n(line 6)\n* base files: Initial Metafont. (line 6)\n* base files, need mode definitions: Modes. (line 6)\n* base files, plain only: Initial Metafont. (line 26)\n* base files, sharing: Hardware and memory dumps.\n(line 6)\n* bases Make target: Additional targets. (line 28)\n* basic BibTeX style files: Basic BibTeX style files.\n(line 6)\n* basic fonts and macros: Installation. (line 33)\n* batch languages: TeX. (line 9)\n* BDF and GF conversion: Font utilities available elsewhere.\n(line 15)\n* beamer, package: Formats. (line 57)\n* beginfig: mpost invocation. (line 31)\n* Berry, Karl: Introduction. (line 44)\n* BIBINPUTS, search path for bib files: bibtex invocation. (line 18)\n* bibliographies, creating: BibTeX. (line 6)\n* bibliography: References. (line 6)\n* bibliography items, cross-referenced: bibtex invocation. (line 31)\n* bibtex: bibtex invocation. (line 6)\n* BibTeX: BibTeX. (line 6)\n* BibTeX collection: bibtex invocation. (line 58)\n* BibTeX style files: Basic BibTeX style files.\n(line 6)\n* BigEndian machines: Hardware and memory dumps.\n(line 6)\n* binaries, linking: Common options. (line 82)\n* blank lines, in TCX files: TCX files. (line 66)\n* boxes, memory for: Runtime options. (line 20)\n* braced filename for \\input: \\input braced filename.\n(line 6)\n* breakpoints, memory for: Runtime options. (line 20)\n* Breitenlohner, Peter: Introduction. (line 9)\n* BSTINPUTS, search path for bst files: bibtex invocation. (line 18)\n* btex for MetaPost labels: mpost invocation. (line 44)\n* btxdoc.bib: bibtex invocation. (line 52)\n* btxdoc.tex: bibtex invocation. (line 46)\n* btxhak.tex: bibtex invocation. (line 49)\n* byte position: pktype invocation. (line 40)\n* byte position <1>: gftype invocation. (line 76)\n* byte swapping: Hardware and memory dumps.\n(line 17)\n* c-sources Makefile target: Additional targets. (line 12)\n* caveats for \\input filenames: \\input filename caveats.\n(line 6)\n* change files, and MFT: mft invocation. (line 63)\n* change files, and Tangle: tangle invocation. (line 11)\n* change files, and Weave: weave invocation. (line 14)\n* changing error messages style: Common options. (line 31)\n* character codes, in GFtype output: gftype invocation. (line 79)\n* character codes, in PKtype output: pktype invocation. (line 47)\n* character codes, in TCX files: TCX files. (line 77)\n* character proofs of fonts: gftodvi invocation. (line 6)\n* CHARACTER property: tftopl invocation. (line 112)\n* character translation files: TCX files. (line 6)\n* CHARDP property: tftopl invocation. (line 112)\n* CHARHT property: tftopl invocation. (line 112)\n* CHARIC property: tftopl invocation. (line 112)\n* CHARWD property: tftopl invocation. (line 112)\n* chtopx: Font utilities available elsewhere.\n(line 23)\n* class name for Metafont: Online Metafont graphics.\n(line 69)\n* cm.base: Initial Metafont. (line 26)\n* cmbase.mf: Initial Metafont. (line 26)\n* cmbase.mft: mft invocation. (line 73)\n* cmmf.base not recommended: Initial Metafont. (line 26)\n* color, in DVItoMP: dvitomp invocation. (line 15)\n* comments, in TCX files: TCX files. (line 70)\n* comments, MFT control: mft invocation. (line 24)\n* common options: Common options. (line 6)\n* commonalities: Commonalities. (line 6)\n* compilation: Installation. (line 6)\n* compile-time options: configure options. (line 6)\n* compile-time options <1>: Compile-time options.\n(line 6)\n* Computer Modern fonts, and Troff: mpost invocation. (line 61)\n* Computer Modern macros: Initial Metafont. (line 26)\n* Computer Modern Typefaces, production of: mft invocation. (line 73)\n* configuration: Installation. (line 6)\n* configuration file reading: Path searching. (line 6)\n* configuration file values: Runtime options. (line 6)\n* configuration, compile-time: configure options. (line 6)\n* configure --with/--enable options: configure options. (line 6)\n* CONTENTS.tex: weave invocation. (line 22)\n* ConTeXt: Formats. (line 28)\n* conventions for options,: Option conventions. (line 6)\n* conversion, DVI to plain text: dvitype invocation. (line 6)\n* conversion, GF to PK: gftopk invocation. (line 6)\n* conversion, GF to plain text: gftype invocation. (line 6)\n* conversion, PK to GF: pktogf invocation. (line 6)\n* conversion, PK to plain text: pktype invocation. (line 6)\n* conversion, property list to TFM: pltotf invocation. (line 6)\n* conversion, property list to VF: vptovf invocation. (line 6)\n* conversion, TFM to property list: tftopl invocation. (line 6)\n* conversion, VF to VPL: vftovp invocation. (line 6)\n* copyright notices: Legalisms. (line 6)\n* Cork encoding and ISO input: TCX files. (line 48)\n* creating memory dumps: Creating memory dumps.\n(line 6)\n* cross-engine functionality: TeX extensions. (line 8)\n* cross-referenced bibliography items: bibtex invocation. (line 31)\n* cross-references, omitting: weave invocation. (line 22)\n* current directory, used for output: Output file location.\n(line 6)\n* Curtis, Pavel: Introduction. (line 44)\n* Cweb: WEB. (line 12)\n* CWEB: WEB. (line 12)\n* date and time, in memory dumps: Hardware and memory dumps.\n(line 35)\n* debugging DVI utilities: dvitype invocation. (line 52)\n* debugging flags, specifying: Common options. (line 64)\n* decimal character codes, in TCX files: TCX files. (line 77)\n* dependencies, hardware: Hardware and memory dumps.\n(line 6)\n* design-size units: tftopl invocation. (line 101)\n* device definitions, for Metafont: Modes. (line 6)\n* device-independent width: pktype invocation. (line 53)\n* device-independent width <1>: gftype invocation. (line 112)\n* directory structure: Installation. (line 33)\n* DISPLAY: Online Metafont graphics.\n(line 76)\n* dot files, written by TeX programs: tex invocation. (line 48)\n* double quote character, ignored in filenames: \\input filenames.\n(line 22)\n* downloading of fonts for MetaPost labels: mpost invocation. (line 66)\n* DrawingServant: Online Metafont graphics.\n(line 35)\n* dump file: Common options. (line 39)\n* dumping memory: Memory dumps. (line 6)\n* DVI comment, specifying: tex invocation. (line 113)\n* DVI files, converting to MPX: dvitomp invocation. (line 6)\n* DVI files, explained: Font file formats. (line 29)\n* DVI format definition: DVI utilities. (line 14)\n* DVI opcodes, showing: dvitype invocation. (line 52)\n* DVI utilities: DVI utilities. (line 6)\n* dvicopy: dvicopy invocation. (line 6)\n* dvitomp: dvitomp invocation. (line 6)\n* dvitype DVI validation: dvitype invocation. (line 6)\n* dvitype output example: dvitype output example.\n(line 6)\n* dvitype.web: DVI utilities. (line 14)\n* dx horizontal escapement: pktype invocation. (line 57)\n* dx horizontal escapement <1>: gftype invocation. (line 106)\n* dy vertical escapement: gftype invocation. (line 106)\n* dynamic array allocation: Runtime options. (line 45)\n* dynamic Metafont mode definitions with smode: Modes. (line 28)\n* dynamic packing variable: pktype invocation. (line 44)\n* e response at error prompt: Editor invocation. (line 6)\n* e-circumflex: \\charsubdef. (line 20)\n* e-TeX: TeX extensions. (line 20)\n* e.mft: mft invocation. (line 73)\n* EC fonts: tex invocation. (line 41)\n* EC fonts <1>: mf invocation. (line 24)\n* editing of bitmap fonts: Font utilities available elsewhere.\n(line 23)\n* editor invoked at error: Editor invocation. (line 6)\n* eight-bit characters in filenames: \\input filename caveats.\n(line 12)\n* empty.tcx: TCX files. (line 48)\n* endian dependencies: Hardware and memory dumps.\n(line 6)\n* eoc GF command: gftype invocation. (line 97)\n* Eplain: Formats. (line 50)\n* epsf: Online Metafont graphics.\n(line 19)\n* epTeX: TeX extensions. (line 66)\n* errors, editor invoked at: Editor invocation. (line 6)\n* escapement, horizontal: pktype invocation. (line 57)\n* escapement, horizontal <1>: gftype invocation. (line 106)\n* escapement, vertical: gftype invocation. (line 106)\n* etex for MetaPost labels: mpost invocation. (line 44)\n* etex is pdfTeX: TeX extensions. (line 32)\n* eupTeX: TeX extensions. (line 66)\n* executables, shared initial and virgin: Initial and virgin. (line 6)\n* exit status, of shell escape: Shell escapes. (line 34)\n* expanded plain format: Formats. (line 50)\n* expanddepth: Runtime options. (line 24)\n* expansion limit, recursive: Runtime options. (line 25)\n* expansion, and \\input filenames: \\input filename caveats.\n(line 6)\n* extensions to TeX: TeX extensions. (line 6)\n* extramembot: Runtime options. (line 19)\n* FACE property: tftopl invocation. (line 95)\n* FAMILY property: tftopl invocation. (line 95)\n* FAMILY property <1>: tftopl invocation. (line 99)\n* Ferguson, Michael: MLTeX. (line 6)\n* file formats for fonts: Font file formats. (line 6)\n* file recorder: Common options. (line 89)\n* filename conventions, in input files: \\input filenames. (line 6)\n* filenames starting with -: Option conventions. (line 19)\n* first line of the main input file: Common options. (line 103)\n* fixed-point arithmetic: Compile-time options.\n(line 21)\n* FIXPT: Compile-time options.\n(line 21)\n* flag byte: pktype invocation. (line 44)\n* floating-point arithmetic: Compile-time options.\n(line 21)\n* floating-point values: Hardware and memory dumps.\n(line 27)\n* fmt file, determining: Determining the memory dump to use.\n(line 6)\n* fmt files: Initial TeX. (line 6)\n* fmt files, sharing: Hardware and memory dumps.\n(line 6)\n* fmts Make target: Additional targets. (line 24)\n* font aliases: Path searching. (line 14)\n* font character code, translating: TCX files. (line 101)\n* font design: Metafont. (line 6)\n* font downloading for MetaPost labels: mpost invocation. (line 66)\n* font file formats: Font file formats. (line 6)\n* font proofs: gftodvi invocation. (line 6)\n* font utilities: Font utilities. (line 6)\n* font utilities, non-Web2c: Font utilities available elsewhere.\n(line 6)\n* fontforge: Font utilities available elsewhere.\n(line 30)\n* fontinst, for creating virtual fonts: Font utilities available elsewhere.\n(line 49)\n* fonts, basic: Installation. (line 33)\n* format files: Initial TeX. (line 13)\n* formats for TeX: Formats. (line 6)\n* formats Make target: Additional targets. (line 17)\n* fraction routines: Compile-time options.\n(line 21)\n* Free Software Foundation documentation system: Formats. (line 43)\n* freedom of Web2c: Introduction. (line 24)\n* ftp.math.utah.edu: bibtex invocation. (line 58)\n* generating source specials: tex invocation. (line 134)\n* geometric designs: Metafont. (line 6)\n* geometric font scaling: Font file formats. (line 21)\n* geometry for Metafont: Online Metafont graphics.\n(line 69)\n* getoptlongonly: Option conventions. (line 6)\n* GF files, explained: Font file formats. (line 39)\n* GF files, output by Metafont: mf invocation. (line 34)\n* GF format definition: Font utilities. (line 11)\n* GF output: mf invocation. (line 34)\n* GF, converting PK to: pktogf invocation. (line 6)\n* GF, converting to PK: gftopk invocation. (line 6)\n* gftodvi: gftodvi invocation. (line 6)\n* gftopk: gftopk invocation. (line 6)\n* gftopxl: Font utilities available elsewhere.\n(line 23)\n* gftype GF validation: gftype invocation. (line 6)\n* gftype.web: Font utilities. (line 11)\n* glue ratio representations: Hardware and memory dumps.\n(line 27)\n* glue, memory for: Runtime options. (line 20)\n* glyph substitutions: MLTeX. (line 6)\n* gray font: gftodvi invocation. (line 29)\n* group-delimited filename for \\input: \\input braced filename.\n(line 6)\n* Gruff, Billy Goat: Triptrap. (line 6)\n* gsftopk: Font utilities available elsewhere.\n(line 35)\n* Harbison, Samuel P.: Hardware and memory dumps.\n(line 39)\n* hardware and memory dumps: Hardware and memory dumps.\n(line 6)\n* headerbyte information: tftopl invocation. (line 95)\n* height, in pixels: pktype invocation. (line 62)\n* help, online: Common options. (line 11)\n* Herberts, Mathias: Online Metafont graphics.\n(line 20)\n* hex character codes, in TCX files: TCX files. (line 77)\n* HINT (Hint Is Not TeX): TeX extensions. (line 53)\n* history: Introduction. (line 44)\n* hiTeX: TeX extensions. (line 53)\n* Hobby, John: Introduction. (line 9)\n* horizontal escapement: pktype invocation. (line 57)\n* horizontal escapement <1>: gftype invocation. (line 106)\n* hp2627: Online Metafont graphics.\n(line 27)\n* human languages, supported in TeX: Languages and hyphenation.\n(line 6)\n* human-readable text, converting DVI to: dvitype invocation. (line 6)\n* human-readable text, converting GF to: gftype invocation. (line 6)\n* human-readable text, converting PK to: pktype invocation. (line 6)\n* human-readable text, converting TFM to: tftopl invocation. (line 6)\n* human-readable text, converting VF to: vftovp invocation. (line 6)\n* hypertext: TeX extensions. (line 32)\n* hyphenation and languages: Languages and hyphenation.\n(line 6)\n* hyphenation patterns, creating: patgen invocation. (line 6)\n* ice cream: Introduction. (line 24)\n* identifier case: tangle invocation. (line 35)\n* identifier collisions: tangle invocation. (line 46)\n* identifier length: tangle invocation. (line 27)\n* identifiers with underlines: tangle invocation. (line 41)\n* ieeetr.bst: Basic BibTeX style files.\n(line 31)\n* il1-t1.tcx: TCX files. (line 48)\n* il2-t1.tcx: TCX files. (line 48)\n* Info format: Formats. (line 43)\n* initial form, enabling: Common options. (line 50)\n* initial Metafont: Initial Metafont. (line 6)\n* initial MetaPost: Initial MetaPost. (line 6)\n* initial programs: Initial and virgin. (line 19)\n* initial TeX: Initial TeX. (line 6)\n* initializations, lengthy: Initial and virgin. (line 19)\n* input filenames: \\input filenames. (line 6)\n* install-bases Make target: Additional targets. (line 28)\n* install-fmts Make target: Additional targets. (line 24)\n* install-formats Make target: Additional targets. (line 17)\n* install-mems Make target: Additional targets. (line 34)\n* installation: Installation. (line 6)\n* interaction between TCX files and -8bit.: TCX files. (line 104)\n* interaction mode: Common options. (line 55)\n* international characters: TCX files. (line 6)\n* introduction: Introduction. (line 6)\n* IPC: IPC and TeX. (line 6)\n* IPCDEBUG: Compile-time options.\n(line 28)\n* IPCDEBUG <1>: IPC and TeX. (line 13)\n* job name: Common options. (line 60)\n* kerning table, in TFM files: tftopl invocation. (line 101)\n* keyboard character code, translating: TCX files. (line 101)\n* Knuth, Donald E.: Introduction. (line 9)\n* Knuth, Donald E. <1>: mft invocation. (line 56)\n* KPATHSEADEBUG: Common options. (line 64)\n* KRN property: tftopl invocation. (line 101)\n* label font: gftodvi invocation. (line 36)\n* LABEL property: tftopl invocation. (line 101)\n* language support in TeX: Languages and hyphenation.\n(line 6)\n* languages, hyphenation rules for: patgen invocation. (line 6)\n* LaTeX: Formats. (line 18)\n* Latin Modern: Font utilities available elsewhere.\n(line 18)\n* left side bearing: pktype invocation. (line 66)\n* left side bearing <1>: gftype invocation. (line 82)\n* legalisms: Legalisms. (line 6)\n* libsigsegv library: Runtime options. (line 33)\n* licensing terms: Introduction. (line 24)\n* LIG property: tftopl invocation. (line 101)\n* ligature table, in TFM files: tftopl invocation. (line 101)\n* LIGTABLE property: tftopl invocation. (line 101)\n* linking binaries: Common options. (line 82)\n* links to binaries: Determining the memory dump to use.\n(line 30)\n* literate programming: WEB. (line 6)\n* LittleEndian machines: Hardware and memory dumps.\n(line 6)\n* location of texmf.cnf in TeX Live: Runtime options. (line 56)\n* log file, BibTeX: bibtex invocation. (line 14)\n* long data type, size of: Hardware and memory dumps.\n(line 6)\n* Lua: TeX extensions. (line 40)\n* LuaTeX: TeX extensions. (line 40)\n* machine dependencies: Hardware and memory dumps.\n(line 6)\n* machine-readable, converting property lists to: pltotf invocation.\n(line 6)\n* machine-readable, converting property lists to <1>: vptovf invocation.\n(line 6)\n* MacKay, Pierre: Font file formats. (line 62)\n* macro packages, major TeX: Formats. (line 6)\n* macros, basic: Installation. (line 33)\n* macros, predefining in memory dumps: Memory dumps. (line 6)\n* magnification: dvicopy invocation. (line 20)\n* magnification <1>: dvitype invocation. (line 28)\n* mainmemory: Runtime options. (line 15)\n* Make targets, additional: Additional targets. (line 6)\n* Martin, Rick: Introduction. (line 63)\n* Mathematical Reviews: Formats. (line 35)\n* mathematical typesetting: TeX. (line 6)\n* mem file, determining: Determining the memory dump to use.\n(line 6)\n* mem files, sharing: Hardware and memory dumps.\n(line 6)\n* memory dump to use, determining: Determining the memory dump to use.\n(line 6)\n* memory dumps: Memory dumps. (line 6)\n* memory dumps and hardware: Hardware and memory dumps.\n(line 6)\n* memory dumps, contain date and time: Hardware and memory dumps.\n(line 35)\n* memory dumps, creating: Creating memory dumps.\n(line 6)\n* mems Make target: Additional targets. (line 34)\n* meta characters in filenames: \\input filename caveats.\n(line 12)\n* Metafont: Metafont. (line 6)\n* Metafont geometry: Online Metafont graphics.\n(line 69)\n* Metafont graphics: Online Metafont graphics.\n(line 6)\n* Metafont input files: mf invocation. (line 24)\n* Metafont invocation: mf invocation. (line 6)\n* Metafont meets PostScript: MetaPost. (line 6)\n* Metafont online support, new devices: Online Metafont graphics.\n(line 79)\n* Metafont source, prettyprinting: mft invocation. (line 6)\n* Metafont, compatibility in MetaPost: Initial MetaPost. (line 15)\n* Metafont, initial: Initial Metafont. (line 6)\n* Metafont, MetaPost, and TeX: Three programs. (line 6)\n* MetaPost: MetaPost. (line 6)\n* MetaPost and plain Metafont compatibility: Initial MetaPost.\n(line 15)\n* MetaPost input files: mpost invocation. (line 26)\n* MetaPost invocation: mpost invocation. (line 6)\n* MetaPost source, prettyprinting: mft invocation. (line 79)\n* MetaPost, initial: Initial MetaPost. (line 6)\n* MetaPost, TeX, and Metafont: Three programs. (line 6)\n* metatype1: Font utilities available elsewhere.\n(line 18)\n* mf: mf invocation. (line 6)\n* mf.base: Initial Metafont. (line 14)\n* MFEDIT: Editor invocation. (line 10)\n* mfplain: Initial MetaPost. (line 15)\n* mfput: mf invocation. (line 34)\n* mft: mft invocation. (line 6)\n* mftalk: Online Metafont graphics.\n(line 30)\n* MFTERM: Online Metafont graphics.\n(line 11)\n* mftmac.tex: mft invocation. (line 6)\n* micro-typography: TeX extensions. (line 32)\n* mktexmf, disabling: mf invocation. (line 24)\n* mktextfM, disabling: tex invocation. (line 41)\n* mltex: MLTeX. (line 6)\n* MLTeX, enabling: tex invocation. (line 108)\n* mode needed to run Metafont: mf invocation. (line 48)\n* modes file needed for Metafont: Modes. (line 6)\n* modes.mf recommended modes file: Modes. (line 10)\n* modedef: Modes. (line 15)\n* modesetup: Modes. (line 15)\n* modifying texmf.cnf in TeX Live: Runtime options. (line 56)\n* Morgan, Tim: Introduction. (line 44)\n* Morris, Bob: Introduction. (line 63)\n* MPEDIT: Editor invocation. (line 10)\n* mpgraph.pdf: mpost invocation. (line 14)\n* mpman.pdf: mpost invocation. (line 6)\n* mpost: mpost invocation. (line 6)\n* mpost, reason for name change: Installation. (line 19)\n* mpout: mpost invocation. (line 31)\n* mproof.tex: mpost invocation. (line 66)\n* mptrap Make target: Additional targets. (line 41)\n* mptrap test: Triptrap. (line 6)\n* mptrap.readme: Triptrap. (line 6)\n* MPX files, converting from DVI files: dvitomp invocation. (line 6)\n* Multi-lingual TeX: MLTeX. (line 6)\n* multiple spaces, and \\input filenames: \\input filename caveats.\n(line 6)\n* N tilde: \\charsubdef. (line 36)\n* new graphics support for Metafont: Online Metafont graphics.\n(line 79)\n* newrow GF command: gftype invocation. (line 93)\n* next: Online Metafont graphics.\n(line 34)\n* non-Unix system, compiling on: Additional targets. (line 12)\n* non-windows-capable Metafont: Online Metafont graphics.\n(line 65)\n* NOX11WIN: Online Metafont graphics.\n(line 56)\n* NUL, not allowed in filenames: \\input filename caveats.\n(line 12)\n* octal character codes, in TCX files: TCX files. (line 77)\n* offset for overflow labels: gftodvi invocation. (line 59)\n* Omega: TeX extensions. (line 25)\n* online Metafont graphics: Online Metafont graphics.\n(line 6)\n* opcodes, showing DVI: dvitype invocation. (line 52)\n* OpenType support: TeX extensions. (line 40)\n* optical font scaling: Font file formats. (line 21)\n* option conventions: Option conventions. (line 6)\n* origin: pktype invocation. (line 66)\n* output directory, specifying: Common options. (line 71)\n* output directory, specifying <1>: Output file location.\n(line 15)\n* output file location: Output file location.\n(line 6)\n* output files, written by TeX programs: tex invocation. (line 48)\n* outputcomment for DVI files: tex invocation. (line 113)\n* overflow label offset: gftodvi invocation. (line 59)\n* overflow, of runtime stack: Runtime options. (line 25)\n* packet length: pktype invocation. (line 50)\n* page, starting: dvicopy invocation. (line 28)\n* page, starting <1>: dvitype invocation. (line 46)\n* parsing the first line: Common options. (line 77)\n* Pascal, creating from WEB: tangle invocation. (line 6)\n* patgen: patgen invocation. (line 6)\n* path searching: Path searching. (line 6)\n* path searching debugging: Common options. (line 64)\n* PDF: TeX extensions. (line 32)\n* PDF, and .mps files: mpost invocation. (line 82)\n* pdfTeX: TeX extensions. (line 32)\n* permissions, legal: Legalisms. (line 6)\n* PFA and PFB conversion: Font utilities available elsewhere.\n(line 39)\n* pfaedit: Font utilities available elsewhere.\n(line 30)\n* PiCTeX, increasing memory for: Runtime options. (line 20)\n* pipes, reading and writing: Shell escapes. (line 64)\n* pixel height: pktype invocation. (line 62)\n* pixel width: pktype invocation. (line 62)\n* PK bitmaps from PostScript: Font utilities available elsewhere.\n(line 35)\n* PK files, explained: Font file formats. (line 39)\n* PK files, not output by Metafont: mf invocation. (line 34)\n* PK format definition: Font utilities. (line 11)\n* PK, converting GF to: gftopk invocation. (line 6)\n* PK, converting to GF: pktogf invocation. (line 6)\n* pktogf: pktogf invocation. (line 6)\n* pktype PK validation: pktype invocation. (line 6)\n* pktype.web: Font utilities. (line 11)\n* PL files, explained: Font file formats. (line 46)\n* plain Metafont, compatibility in MetaPost: Initial MetaPost.\n(line 15)\n* plain text, converting DVI to: dvitype invocation. (line 6)\n* plain text, converting GF to: gftype invocation. (line 6)\n* plain text, converting PK to: pktype invocation. (line 6)\n* plain text, converting TFM to: tftopl invocation. (line 6)\n* plain text, converting VF to: vftovp invocation. (line 6)\n* plain.base: Initial Metafont. (line 14)\n* plain.bst: Basic BibTeX style files.\n(line 11)\n* plain.fmt: Initial TeX. (line 13)\n* plain.mft: mft invocation. (line 67)\n* pltotf: pltotf invocation. (line 6)\n* pool file, writing: tangle invocation. (line 16)\n* Poole, Simon: Online Metafont graphics.\n(line 50)\n* pooltype: pooltype invocation. (line 6)\n* portable filenames: \\input filenames. (line 25)\n* PostScript fonts, and Troff: mpost invocation. (line 61)\n* PostScript meets Metafont: MetaPost. (line 6)\n* PostScript output: mpost invocation. (line 31)\n* PostScript to PK bitmaps: Font utilities available elsewhere.\n(line 35)\n* PostScript Type 1 font conversion: Font utilities available elsewhere.\n(line 39)\n* PostScript, and font scaling: Font file formats. (line 21)\n* potrace: Font utilities available elsewhere.\n(line 42)\n* predefined macros and memory dumps: Memory dumps. (line 6)\n* prettyprinting Metafont source: mft invocation. (line 6)\n* prettyprinting WEB programs: weave invocation. (line 6)\n* primitives, new: TeX extensions. (line 20)\n* printable characters, specifying: TCX files. (line 87)\n* printer characteristics, for Metafont: Modes. (line 6)\n* production use: Initial and virgin. (line 15)\n* program name, determines memory dump: Determining the memory dump to use.\n(line 30)\n* program names, special: Common options. (line 50)\n* program names, special <1>: Common options. (line 82)\n* program names, special <2>: tex invocation. (line 108)\n* prologues: mpost invocation. (line 111)\n* prologues, and EPSF output: mpost invocation. (line 76)\n* proof mode: mf invocation. (line 48)\n* proof sheets, of fonts: gftodvi invocation. (line 6)\n* property list format: tftopl invocation. (line 43)\n* property list, converting TFM to: tftopl invocation. (line 6)\n* property list, converting VF to virtual: vftovp invocation. (line 6)\n* ps2pk: Font utilities available elsewhere.\n(line 35)\n* psfonts.map, read by MetaPost: mpost invocation. (line 76)\n* pTeX: TeX extensions. (line 59)\n* PXL files, explained: Font file formats. (line 39)\n* pxtoch: Font utilities available elsewhere.\n(line 23)\n* quoted filename for \\input: \\input quoted filename.\n(line 6)\n* Raichle, Bernd: MLTeX. (line 6)\n* reading, additional: Introduction. (line 72)\n* readonly directory, running TeX in: Output file location.\n(line 15)\n* readonly directory, running TeX in <1>: Output file location.\n(line 19)\n* reallocation of arrays: Runtime options. (line 45)\n* recursive expansion limit: Runtime options. (line 25)\n* redefined character substitutions: \\tracingcharsubdef. (line 6)\n* reference pixel: pktype invocation. (line 66)\n* references: References. (line 6)\n* regis: Online Metafont graphics.\n(line 39)\n* Regis graphics support: Online Metafont graphics.\n(line 40)\n* regression testing: tex invocation. (line 113)\n* repeated rows: pktype invocation. (line 76)\n* representation of strings: pooltype invocation. (line 30)\n* restricted shell escapes: Shell escapes. (line 6)\n* right side bearing: pktype invocation. (line 66)\n* right side bearing <1>: gftype invocation. (line 82)\n* Rokicki, Tomas: Introduction. (line 44)\n* run length encoded bitmaps: pktype invocation. (line 76)\n* run length encoded bitmaps <1>: gftype invocation. (line 89)\n* runtime options: Runtime options. (line 6)\n* runtime stack overflow: Runtime options. (line 25)\n* scaled pixels: pktype invocation. (line 57)\n* scaled pixels <1>: gftype invocation. (line 106)\n* scaling of fonts: Font file formats. (line 21)\n* security, and output files: tex invocation. (line 48)\n* security, and shell escapes: Shell escapes. (line 6)\n* security, and write: mpost invocation. (line 88)\n* security, and \\openout: tex invocation. (line 48)\n* segmentation fault: Runtime options. (line 25)\n* shapes: Metafont. (line 6)\n* sharing memory dumps: Hardware and memory dumps.\n(line 6)\n* shell commands in TeX: Shell escapes. (line 6)\n* shellescape enabling in TeX: Shell escapes. (line 6)\n* shellescapecommands: Shell escapes. (line 52)\n* siam.bst: Basic BibTeX style files.\n(line 35)\n* side bearings: pktype invocation. (line 66)\n* side bearings <1>: gftype invocation. (line 82)\n* SIGSEGV: Runtime options. (line 25)\n* slant font: gftodvi invocation. (line 39)\n* slides, producing: Formats. (line 57)\n* SliTeX: Formats. (line 57)\n* small Metafont memory and modes: Modes. (line 15)\n* smode and dynamic Metafont mode definition: Modes. (line 28)\n* sockets: IPC and TeX. (line 6)\n* space-terminated filenames: \\input filenames. (line 10)\n* Spiderweb: WEB. (line 12)\n* Stallman, Richard: Introduction. (line 63)\n* starting page: dvicopy invocation. (line 28)\n* starting page <1>: dvitype invocation. (line 46)\n* Steele Jr., Guy L.: Hardware and memory dumps.\n(line 39)\n* stopping at the first error: Common options. (line 46)\n* strategy, overall: Introduction. (line 18)\n* string numbers, displaying: pooltype invocation. (line 6)\n* string pool, writing: tangle invocation. (line 16)\n* string representation: pooltype invocation. (line 30)\n* style design, for BibTeX: bibtex invocation. (line 49)\n* style files: mft invocation. (line 67)\n* substitutions of font glyphs: MLTeX. (line 6)\n* sun: Online Metafont graphics.\n(line 42)\n* sun-gfx.c: Online Metafont graphics.\n(line 43)\n* Suntools: Online Metafont graphics.\n(line 43)\n* SunView: Online Metafont graphics.\n(line 43)\n* swap space, as array limit: Runtime options. (line 45)\n* swapping bytes: Hardware and memory dumps.\n(line 17)\n* syntax of TCX files: TCX files. (line 65)\n* system C library function: Shell escapes. (line 6)\n* system command: Shell escapes. (line 6)\n* system fonts, using: TeX extensions. (line 40)\n* T1 encoding and ISO input: TCX files. (line 48)\n* tabs, and \\input filenames: \\input filename caveats.\n(line 6)\n* Tachikawa, Elizabeth: Font file formats. (line 62)\n* tangle: tangle invocation. (line 6)\n* targets, additional Make: Additional targets. (line 6)\n* TCX character translation files: TCX files. (line 6)\n* technical illustrations, creating: MetaPost. (line 6)\n* tek: Online Metafont graphics.\n(line 47)\n* Tektronix: Online Metafont graphics.\n(line 48)\n* Tektronix 4014: Online Metafont graphics.\n(line 51)\n* TERM: Online Metafont graphics.\n(line 11)\n* terminator for filenames: \\input filenames. (line 10)\n* terse output: bibtex invocation. (line 28)\n* teTeX distribution: Introduction. (line 56)\n* tex: tex invocation. (line 6)\n* TeX, bibliographies for: bibtex invocation. (line 58)\n* TeX, creating from Metafont: mft invocation. (line 6)\n* TeX, creating from WEB: weave invocation. (line 6)\n* TeX, description of: TeX. (line 6)\n* TeX, extensions to: TeX extensions. (line 6)\n* TeX, format packages for: Formats. (line 6)\n* TeX, initial: Initial TeX. (line 6)\n* TeX, input files found: tex invocation. (line 20)\n* TeX, invocation: tex invocation. (line 6)\n* TeX, Metafont, and MetaPost: Three programs. (line 6)\n* TeX, Web2c implementation of: Introduction. (line 9)\n* tex.fmt: Initial TeX. (line 13)\n* TEXBIB, search path for bib files: bibtex invocation. (line 18)\n* TEXEDIT: Editor invocation. (line 10)\n* texfonts.map: Path searching. (line 14)\n* Texinfo: Formats. (line 43)\n* texmf.cnf: Path searching. (line 6)\n* texmf.cnf <1>: Runtime options. (line 6)\n* texmf.cnf for editors: Editor invocation. (line 10)\n* texmf.cnf for shell escapes: Shell escapes. (line 6)\n* texmfmp.c: Online Metafont graphics.\n(line 79)\n* TEXMFOUTPUT, used for reading: Output file location.\n(line 25)\n* TEXMFOUTPUT, used if . unwritable: Output file location.\n(line 19)\n* texmfcasefoldsearch: Runtime options. (line 42)\n* texput: tex invocation. (line 33)\n* TFM files, converting property lists to: pltotf invocation. (line 6)\n* TFM files, explained: Font file formats. (line 12)\n* TFM files, output by Metafont: mf invocation. (line 43)\n* TFM files, output by MetaPost: mpost invocation. (line 31)\n* TFM width of characters: pktype invocation. (line 53)\n* TFM width of characters <1>: gftype invocation. (line 112)\n* tftopl: tftopl invocation. (line 6)\n* three programs: Three programs. (line 6)\n* time and date, in memory dumps: Hardware and memory dumps.\n(line 35)\n* title font: gftodvi invocation. (line 33)\n* tl-check-fmtshare: Hardware and memory dumps.\n(line 12)\n* tokenization, and \\input filenames: \\input filename caveats.\n(line 6)\n* toolkits, X: Online Metafont graphics.\n(line 59)\n* torture tests: Triptrap. (line 6)\n* translation file for TeX, specifying: Common options. (line 103)\n* translation from WEB to C: Introduction. (line 18)\n* trap Make target: Additional targets. (line 41)\n* trap test: Triptrap. (line 6)\n* trapman.tex: Triptrap. (line 6)\n* Trickey, Howard: Introduction. (line 44)\n* trip Make target: Additional targets. (line 41)\n* trip test: Triptrap. (line 6)\n* tripman.tex: Triptrap. (line 6)\n* triptrap Make target: Additional targets. (line 41)\n* Troff, and MetaPost: mpost invocation. (line 61)\n* troff, supported in MetaPost: MetaPost. (line 12)\n* Troff, WEB for: WEB. (line 12)\n* Trojan horses and TeX programs: tex invocation. (line 48)\n* TrueType support: TeX extensions. (line 40)\n* TUGboat bibliography: bibtex invocation. (line 58)\n* Type 1 conversion: Font utilities available elsewhere.\n(line 39)\n* type design, personal: Initial Metafont. (line 31)\n* type programs, DVI: dvitype invocation. (line 6)\n* type programs, GF: gftype invocation. (line 6)\n* type programs, PK: pktype invocation. (line 6)\n* type programs, pool: pooltype invocation. (line 6)\n* typeface families: Metafont. (line 6)\n* typesetting: TeX. (line 6)\n* Unicode: TeX extensions. (line 25)\n* Unicode input: tex invocation. (line 86)\n* Unicode input, native: TeX extensions. (line 47)\n* uniterm: Online Metafont graphics.\n(line 50)\n* unsrt.bst: Basic BibTeX style files.\n(line 39)\n* upTeX: TeX extensions. (line 59)\n* UTF-8 input: tex invocation. (line 86)\n* UTF-8 input, native: TeX extensions. (line 40)\n* validation, of DVI files: dvitype invocation. (line 6)\n* validation, of GF files: gftype invocation. (line 6)\n* validation, of PK files: pktype invocation. (line 6)\n* validation, of TFM files: tftopl invocation. (line 6)\n* validation, of VF files: vftovp invocation. (line 6)\n* verbose BibTeX output, suppressing: bibtex invocation. (line 28)\n* verbosity, enabling: Common options. (line 15)\n* version number, finding: Common options. (line 18)\n* vertical escapement: gftype invocation. (line 106)\n* VF files, converting property lists to: vptovf invocation. (line 6)\n* vftovp: vftovp invocation. (line 6)\n* virgin programs: Initial and virgin. (line 15)\n* virtual font creation: Font utilities available elsewhere.\n(line 49)\n* virtual fonts, expanding: dvicopy invocation. (line 6)\n* virtual-fonts.knuth: Font file formats. (line 56)\n* virtualfonts.txt: Font file formats. (line 56)\n* vptovf: vptovf invocation. (line 6)\n* weave: weave invocation. (line 6)\n* WEB: WEB. (line 6)\n* web environments, and security: Shell escapes. (line 71)\n* WEB pool files, displaying: pooltype invocation. (line 6)\n* WEB programs, compiling: tangle invocation. (line 6)\n* WEB programs, typesetting: weave invocation. (line 6)\n* WEB2C, search path for TCX files: TCX files. (line 35)\n* Weber, Olaf: Introduction. (line 44)\n* webmac.tex: weave invocation. (line 22)\n* webman.tex: WEB. (line 12)\n* whitespace, in TCX files: TCX files. (line 68)\n* whitespace-terminated filenames: \\input filenames. (line 10)\n* width, device-independent: pktype invocation. (line 53)\n* width, device-independent <1>: gftype invocation. (line 112)\n* width, in pixels: pktype invocation. (line 62)\n* word processor, not: TeX. (line 9)\n* writing memory dumps: Creating memory dumps.\n(line 6)\n* X bitmap fonts: Font utilities available elsewhere.\n(line 15)\n* X class name for Metafont: Online Metafont graphics.\n(line 69)\n* x offset: pktype invocation. (line 66)\n* X resources: Online Metafont graphics.\n(line 69)\n* X toolkits and Metafont: Online Metafont graphics.\n(line 59)\n* xampl.bib: bibtex invocation. (line 55)\n* xbfe, bitmap font editor: Font utilities available elsewhere.\n(line 23)\n* XeTeX: TeX extensions. (line 47)\n* xfed, bitmap font editor: Font utilities available elsewhere.\n(line 23)\n* xfedor, bitmap font editor: Font utilities available elsewhere.\n(line 23)\n* Xlib: Online Metafont graphics.\n(line 56)\n* Xlib support: Online Metafont graphics.\n(line 59)\n* Xt: Online Metafont graphics.\n(line 56)\n* Xt support: Online Metafont graphics.\n(line 59)\n* xterm: Online Metafont graphics.\n(line 56)\n* y offset: pktype invocation. (line 66)\n\n",
"subsections": []
}
},
"flags": [],
"examples": [],
"see_also": []
}