On Sat, Mar 31, 2012 at 06:36:35PM +0200, Orm Finnendahl wrote: > xetex: > > > orm@varese:~/work/texte/sonstiges$ xetex test02.tex > > This is XeTeX, Version 3.1415926-2.2-0.9995.2 (TeX Live 2009/Debian) > > entering extended mode > > (./test02.tex [1] > > kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 > > fssb8a.pfa > > mktexpk: don't know how to create bitmap font for fssb8a.pfa. > > kpathsea: Appending font creation commands to missfont.log. > > > ** WARNING ** Could not locate a virtual/physical font for TFM "fssb8r". > > ** WARNING ** >> This font is mapped to a physical font "fssb8a.pfa". > > ** WARNING ** >> Please check if kpathsea library can find this font: > > fssb8a.pfa > > ** ERROR ** Cannot proceed without .vf or "physical" font for PDF output... > > > Output file removed. > > ) > > Error 256 (driver return code) generating output; > > file test02.pdf may not be valid. > > Transcript written on test02.log. > > orm@varese:~/work/texte/sonstiges$
I highly suspect this is a xdvipdfmx issue, since the engine wouldn't need to real font at all. IIRC, old versions of (x)dvipdfmx had its own map file, so it might be that updmap(-sys) failed to update it for some reason. Running xdvipdfmx -v on the xdv file, will print the loaded map files in the first line, you can then check them and see if the font is there or not. Regards, Khaled -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
