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

Jonathan Kew jonathan_kew at sil.org
Thu Jun 15 14:16:58 CEST 2006

On 15 Jun 2006, at 12:51 pm, William Adams wrote:

> 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).

It's a xetex thing (OK, bug, if you insist!), not fontspec. And  
underlying it are differences between the information available  
through ATS and Fontconfig. And it's also related to the problems  
xetex currently has with optical families on Linux/Windows, mentioned  
recently in connection with Garamond Premier Pro.

I'm currently re-working some of the font-handling code to try and  
improve this, so we'll see how things stand once that's done.....


More information about the XeTeX mailing list