On 3/31/12 9:19 AM, 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?
I'm not sure offhand, but I wonder whether the issue is that your fonts
are in ASCII PostScript (.pfa) format, and perhaps the driver xetex is
using only supports binary PostScript (.pfb) files.
JK
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
