Junichi Uekawa <[EMAIL PROTECTED]> wrote:
> BTW, how would I find out that /var/lib/texmf/web2c/latex.fmt
> is in fact not generated from tex, but pdfetex?
You can do that by parsing /var/lib/texmf/web2c/fmtutil.cnf (or rather
`kpsewhich --format='web2c files' fmtutil.cnf`) if you need to.
> I have an impression that 'epfmt' is probably the
> extention for such files.
I don't think that this is needed - we are working on a system that has
a lot of utilities that are designed to make these internals irrelevant
for users, and as much as possible for package authors, too.
> $ tex -ini '&latex'
> This is TeX, Version 3.141592 (Web2C 7.5.4) (INITEX)
> ---! /var/lib/texmf/web2c/latex.fmt was written by pdfetex
> (Fatal format file error; I'm stymied)
Maybe you should in fact follow Hilmars suggestion and
- create, for each processed file with basename name, a file
fmtutil_$name.cnf, containing
grep ^latex `kpsewhich --format='web2c files' fmtutil.cnf` | \
awk '{print $1,"\t",$2,"\t",$3,"\t &latex name.ini"}'
- also create a file name.ini that contains
\makeatletter
[EMAIL PROTECTED]
\def\WHIZZYCONFIGDIR{'"$CONFIGDIR"'}
\def\WHIZZYHOME{'"$HOME"'}
\makeatother
\let\Documentclass\documentclass
\renewcommand{\documentclass}[2][]{\Documentclass[#1]{#2}
\let\WhizzyLevel'"$LEVEL"'
\def\WhizzyExt{'"$EXT"'}
\input{'"$PACKAGE"'}}
\input{'"$NAME$EXT"'}
\dump
(of course with the variables already replace, that's easy with a here
document).
- call
fmtutil --cnffile fmtutil_name.cnf --fmtdir .
That is probably more complicated than the current procedure, but it's
safe for changes of the internals.
Regards, frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
