> > --parse-handler: This new option makes it possible to give a file name
> > containing OCaml code to invoke on a parse error. It allows displaying
> > the parse error in a custom format.
>
> Can other programming languages be eventually also reused here for special
> error
> reporting?
Not currently.
> I would like to clarify another implementation detail because of more
> surprising
> error messages:
> …
> kpathsea: Running mktextfm ptmr8t
> /usr/share/texmf/web2c/mktexnam: Could not map source abbreviation for
> ptmr8t.
> /usr/share/texmf/web2c/mktexnam: Need to update ?
> mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode;
> input ptmr8t
> This is METAFONT, Version 2.718281 (TeX Live 2013/TeX Live for SUSE Linux)
>
>
> kpathsea: Running mktexmf ptmr8t
> ! I can't find file `ptmr8t'.
> <*> ...:=ljfour; mag:=1; nonstopmode; input ptmr8t
>
> Please type another input file name
> ! Emergency stop.
> <*> ...:=ljfour; mag:=1; nonstopmode; input ptmr8t
>
> Transcript written on mfput.log.
> grep: ptmr8t.log: Datei oder Verzeichnis nicht gefunden
> mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input
> ptmr8t' failed to make ptmr8t.tfm.
> kpathsea: Appending font creation commands to missfont.log.
>
> ! Font T1/ptm/m/n/10=ptmr8t at 10.0pt not loadable: Metric (TFM) file not
> found
> .
> <to be read again>
> relax
> l.85 \begin{document}
>
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on manual.log.
> …
>
> Which software package should provide the needed font files for the
> documentation generation process?
I don't know about the installation of latex on Suse. Perhaps google for
the error and see what comes up.
julia_______________________________________________
Cocci mailing list
[email protected]
https://systeme.lip6.fr/mailman/listinfo/cocci
