Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#2079 miktex doesn't find mf files in the current directory

open
METAFONT (8)
2014-02-18
2011-08-18
U_Fischer
No

This problem has been reported on http://tex.stackexchange.com/questions/25959/metafont-can-not-find-d7seg-mf/25970#25970.

If you run this document

\documentclass{article}

\newfont{\dviiseg}{d7seg scaled 1200}

\begin{document}
$\mbox{\dviiseg{c}}(c)$
\end{document}

with d7seq.mf only in the current directory you get an error:

(J:\MiKTeX2.9\tex\latex\base\size10.clo))Making d7seg.tfm from I:\Z-Test\d7seg.mf...
Running miktex-mf.exe...
This is METAFONT, Version 2.718281 (MiKTeX 2.9)

! I can't find file `d7seg'.
<*> \mode:=cx;nonstopmode;input d7seg

It works fine if the mf is moved to a root:

(J:\MiKTeX2.9\tex\latex\base\size10.clo))Making d7seg.tfm from I:\Z-Test\d7seg.mf...
Running miktex-mf.exe...
This is METAFONT, Version 2.718281 (MiKTeX 2.9)

(I:\TeX-Roots\UFlocaltexmf\fonts\source\d7seg.mf [32] [33] [34] [35] [36]

One can see that at first the d7seq.mf in the current directory is found and that in a second step a mf in a root is searched (and used if found).

Using mf directly works without problems. It is only the "automatic" generation which fails.

(the example d7seq.mf can be found on CTAN)
Ulrike Fischer

Discussion