Re: Weird problem in TeXworks but not command-line

Am Wed, 13 Feb 2013 00:48:37 +0000 schrieb Sébastien Loisel:


> I have a baffling issue.

> Then I build using the green "play" button in TeXworks. This is the output
> I get:
> 
> This is XeTeX, Version 3.1415926-2.4-0.9998 (MiKTeX 2.9 64-bit)
...
> C:\ProgramData\MiKTeX\2.9\fonts/tfm/public/mathabx\matha8.tfm already
> exists.
> miktex-xetex.exe: The font file could not be found.
> miktex-xetex.exe: Data: matha8

 
> I can confirm that no PDF file is generated. 

> Then, I open a command line window using cmd.exe. I do this:
 
> C:\Users\Sébastien\Dropbox\2013\miktex-bug>xelatex bug.tex
> This is XeTeX, Version 3.1415926-2.4-0.9998 (MiKTeX 2.9 64-bit)
...
> Output written on bug.pdf (1 page).


The tfm-path above means that the tfm has not been installed but has
been generated (e.g. from a mf-source), but I do find the path a bit
curious. I don't have a multiuser installation so I can't test but I
would have expected the tfm in the UserData root and not in
CommonData. 

What do you get when you run on the command line (where everything
works)

   kpsewhich matha8.tfm

and

   kpsewhich -all matha8.tfm

?


Also you could run in texworks the following document (use a
test.tex in an empty folder!). You will have to add the argument
--shell-escape to the call to pdflatex first (in the options):

\documentclass{article} 
\begin{document}

\immediate\write18{set > testset.log}
\immediate\write18{initexmf --report >testreport.log}
\end{document}

You can then compare the log-files with the output of "set" and
"initexmf --report" on the command line.


You should also check the log-files: They often contains more
informations then the terminal output. 

-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/


------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb