[XeTeX] Differing font name handling betwixt Mac OS X and W32 (and Linux?) XeTeX

Jjgod Jiang gzjjgod at gmail.com
Thu Jun 15 14:07:24 CEST 2006

AFAIK, XeTeX will first try the font's PSFontName, then it's Font Family..

OpenType fonts in Font Folio does have some naming problems to work
with XeTeX, for example, Warnock Pro, if I installed Warnock Pro Light,
\fontname\f="Warnock Pro" will use Warnock Pro Light instead of Warnock
Pro Regular, the only solution I can find to prevent this is use it's

2006/6/15, William Adams <will.adams at frycomm.com>:
> Okay, I've just had w32xetex build a font cache of the entire (well,
> Western) OpenType Font Folio OpenType fonts.
> Trying it out, I found that some fonts didn't work w/ closed up names
> (Garamond Premier Pro most notably), but did w/ closed up names, and
> that in some instances, font weights weren't correctly chosen
> (noticed this with ITC Franklin Gothic Std (am I the only person in
> the world weirded out by that abbreviation?) and I think Helvetica
> Neue).
> I'm going to be doing more testing on this presently, but it was
> interesting enough, I thought it warranted some specific discussion
> (I think it's been touched on peripherally, not specifically, if my
> uncertain organic memory is reading right).
> So, the short version, to jump start conversation is:
> \setromanfont{Garamond Premr Pro}
>   - works on w32tex (and Linux?)
> but
> \setromanfont{GaramondPremrPro}
>   - works in Mac OS X
> Not sure if it's fontspec-specific, or a XeTeX thing (didn't think to
> test w/ Plain TeX since I'm spoiled by fontspec's goodness).
> William
> --
> William Adams
> senior graphic designer
> Fry Communications
> This email message and any files transmitted with it contain information
> which is confidential and intended only for the addressee(s). If you are
> not the intended recipient(s), any usage,  dissemination, disclosure, or
> action taken in  reliance on it is prohibited.  The reliability of  this
> method of communication cannot be guaranteed.  Email can be intercepted,
> corrupted, delayed, incompletely transmitted, virus-laden,  or otherwise
> affected during transmission. Reasonable steps have been taken to reduce
> the risk of viruses, but we cannot accept liability for damage sustained
> as a result of this message. If you have received this message in error,
> please immediately delete it and all copies of it and notify the sender.
> _______________________________________________
> XeTeX mailing list
> postmaster at tug.org
> http://tug.org/mailman/listinfo/xetex

More information about the XeTeX mailing list