<div dir="ltr">2017-01-28 0:34 GMT+01:00 Reinhard Kotucha <span dir="ltr"><<a href="mailto:reinhard.kotucha@web.de" target="_blank">reinhard.kotucha@web.de</a>></span>:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 2017-01-27 at 10:21:34 +0900, Norbert Preining wrote:<br>
<br>
> > > > ---! /home/cec/.texlive2016/texmf-<wbr>var/web2c/pdftex/latex.fmt doesn't match<br>
><br>
> > Maybe it's better not to remove anything right now because Charles is<br>
> > able to reproduce the bug and can provide further information.<br>
><br>
> Reinhard, the bug is obvious to me. An *old* format is tried to be<br>
> loaded into a newer engine. That is very typical.<br>
<br>
</span>Hi Norbert,<br>
obviously, of course, but this is not what I mean. Since pool files<br>
were even abolished long time before TL-2013 was released, the actual<br>
bug is that they are mentioned at all in error messages.<br></blockquote><div><br></div><div>Imagine that you have a mess in PATH, you run a tex binary from 2011 (form another distro, not from TL) which requires a pool file but it finds a format from TL 2016 were no pool exists. How can you set a better error message?<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I would agree with you if a TeX system older than ten years is<br>
involved but this is definitely not the case here.<br>
<br>
If an inappropriate format file is loaded, I would expect that TeX<br>
only reports a "Fatal format file error" but doesn't mention a pool<br>
file. The message we're talking about is misleading. pdftex does<br>
*not* load a (non-existent) pool file at all but complains that it<br>
doesn't match.<br>
<br>
I assume that Knuth's TeX checks whether the format file and the<br>
binary match *and* whether the format file and the pool file match.<br>
Newer engines, which are not aware of pool files, should do only the<br>
first check. They can't do the the second one anyway, otherwise<br>
creation of format files will always fail. Hence it's unclear what<br>
triggered this error message. This is also the reason I said that<br>
someone who is familiar with TeX's internals can provide further<br>
information and probably a patch.<br>
<br>
In other words, the actual bug is not that a new binary found a stale<br>
format file or vice versa but the misleading error message.<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
Regards,<br>
Reinhard<br></div></div></blockquote><div><br><br><br clear="all"><div><div class="gmail_signature">Zdeněk Wagner<br><a href="http://ttsm.icpf.cas.cz/team/wagner.shtml" target="_blank">http://ttsm.icpf.cas.cz/team/wagner.shtml</a><br><a href="http://icebearsoft.euweb.cz" target="_blank">http://icebearsoft.euweb.cz</a></div></div>
<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">
<br>
--<br>
------------------------------<wbr>------------------------------<wbr>------<br>
Reinhard Kotucha Phone: <a href="tel:%2B49-511-3373112" value="+495113373112">+49-511-3373112</a><br>
Marschnerstr. 25<br>
D-30167 Hannover mailto:<a href="mailto:reinhard.kotucha@web.de">reinhard.kotucha@web.de</a><br>
------------------------------<wbr>------------------------------<wbr>------<br>
</div></div></blockquote></div><br></div></div>