On Sat, Mar 31, 2012 at 06:19:50PM +0200, Orm Finnendahl wrote: > Hi, > > thanks for the help. I wasn't aware of xetex's capabilities to use > systemwide installed fonts. Including them like this works ootb (I > already had these fonts installed): > > \font\rm="ScalaSans-Regular" at 14 pt \rm Hello World! > > There is one drawback though: I have generated all kinds of virtual > fonts, a fake SmallCaps font etc. All tfm, vf, afm files in all kinds > of different encodings are in their respective folders (and they are > all found with kpsewhich). As I'm using them for years now I really > would like to get it working in xetex with TeX's default mechanism > (the main reason for the switch to xetex is its utf-8 > support). Otherwise I'd be stuck with the supplied PostScript fonts > only. > > If xetex is capable of using kpathsea, is there a way to debug the > problem by finding, which part of the program is stuck where?
It should work, AFAIK. This might be a xdvipdfmx issue, if you run xetex --no-pdf does it fail? if not, then try running xdvipdfmx on the resulting xdv file with various verbosity levels and see what is going on. Regards, Khaled -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
