[XeTeX] XeTeX 0.99 released

Will Robertson will at guerilla.net.au
Mon Dec 12 04:00:04 CET 2005

Replies to a few comments by Jonathan Kew:

> * \fontdimen1 (slant) ... are set appropriately when a native font  
> is loaded;

This seems a little erratic; for example, Hoefler Text gives a  
fontdimen1 of 0.0pt. Should this always give some sort of positive  
value for italic fonts, or will it occasionally break?

If the former, I'll leave \emph alone; if fontdimen1 isn't reliable,  
I'm happy to patch the LaTeX command to work correctly always  
(although I'm somewhat hesitant to do so...).

> I can imagine something like:
>   \XeTeXadjustfeatures\myfontselector "Ligatures=Rare  
> Ligatures;Numerals=Oldstyle Numerals"
> or for the OpenType variety:
>   \XeTeXadjustfeatures\myfontselector "+smcp,-liga"
> but I'll need to think some more about what it would involve to  
> actually implement this.

I'm in two minds about this. On the one hand, it would make it easier  
for the macro writer to write a high-level syntax like I've done in  

On the other hand, I have already written it in fontspec, and it  
isn't that complex. I'm more of the opinion that primitives should  
generally only be introduced when they simply can't be done (or can't  
be efficiently) with macros.

> It's also occurred to me, by the way, that we probably want an  
> \ifXeTeXnativefont test that lets you know whether extensions such  
> as \XeTeXglyph, \XeTeXcharglyph, \XeTeXadjustfeatures  
> (potentially), etc., are usable with a given font selector.

Yep. I think TeX-based syntaxes needs as much error correction as  
possible, which is tricky without conditionals to check if the input  
is valid.

How about \XeTeXfonttype = 0, 1, 2 = doesn't exist, legacy TFM, or  

(AAT vs. OpenType is meaningless because one font can contain both  


More information about the XeTeX mailing list