Install Now
fmtutil.cnf - configuration file for fmtutil
Contents
Bugs
Email bug reports to <https://lists.tug.org/tex-k> (public mailing list).
Description
The fmtutil.cnf file contains the configuration information for fmtutil(8). Each line contains the name
of the format (e.g., ``tex´´, ``latex´´, ``omega´´), the name of the engine that is used by that format
(e.g., ``tex´´, ``etex´´, ``omega´´), the pattern file (e.g., language.dat, language.def), and any
arguments (name of an .ini file).
Fields are separated by whitespace and complete lines can be commented out with ``#´´. The ``pattern
file´´ field cannot be used to define a file that is used while building the format. It tells fmtutil
which files (separated by commas) the format creation procedure reads and it has an effect to the options
--showhyphen and --byhyphen. If the format has no way to customize hyphenation, a ``-´´ can be used to
indicate this.
Files
fmtutil.cnf
default configuration file
language.dat
hyphenation pattern file
language.def
hyphenation pattern file
language.dat.lua
hyphenation pattern file
Name
fmtutil.cnf - configuration file for fmtutil
Notes
The tex(1) and amstex(1) formats always load hyphen.tex. No customization by a pattern file is available
for these formats. Therefore, the pattern-file field for the tex and amstex is usually indicated to be
empty (``-´´).
You can, however, build customized formats on top of plain tex(1) or amstex(1) by using bplain.tex
instead of plain.tex (b for the Babel system). See, for example, the bplain.ini file for the bplain
format).
etex(1) loads language.def, not language.dat.
Symbolic links to the correct engines (e.g., bplain -> tex) are generated by the texlinks(8) script.
Remember to run texlinks(8) if you run fmtutil(8) yourself, rather than using the FORMATS option in
texconfig(8).
See Also
amstex(1), etex(1), fmtutil(8), tex(1), texconfig(8), texlinks(8).
<https://tug.org/texlive/scripts-sys-user.html>
PNG Icons
Emojis