[tex-live] texmf.cnf paths for format files

gnwiii at gmail.com gnwiii at gmail.com
Thu Jan 18 19:01:28 CET 2007

On 1/18/07, Vladimir Volovich <vvv at vsu.ru> wrote:

> "HH" == Hans Hagen writes:
>  HH> this puzzles me since pdftex and xetex should set $engine
>  HH> themselves i.e. they *are* the engines
> he was talking about running "kpsewhich", not pdftex or xetex.

In particular, after getting a "cont-en.fmt not found" error, users
are going to be running:

C:\...ttings\WhiteG\Desktop\test\tl2007>kpsewhich cont-en.fmt

because nobody told them they should add the engine:

C:\...ttings\WhiteG\Desktop\test\tl2007>kpsewhich -engine=pdftex cont-en.fmt

> "kpsewhich" doesn't assume any engine, unless you explicitly set it in
> a command-line argument.

On Win32, engine=unset if you didn't give an explicit value on the command line:

>kpsewhich -debug=1 cont-en.fmt
kdebug:kpse_normalize_path (./cont-en.fmt) => 0
kdebug:kpse_normalize_path (f:/TeXLive2007/texmf-var/web2c/unset) => 2
kdebug:kpse_normalize_path (f:/TeXLive2007/texmf/web2c/unset) => 2
kdebug:kpse_normalize_path (f:/TeXLive2007/../share/texmf-local/web2c/unset) =>
kdebug:kpse_normalize_path (f:/TeXLive2007/texmf-dist/web2c/unset) => 2

It would be more helpful to have all the cont-en.fmt's listed, but how
should kpathsea
know what engines to try?  I suppose there should be some
configuration sharing between fmtutil and kpathsea so both agree on a
list of engines.

George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia

More information about the tex-live mailing list