On Tue, Aug 17, 2010 at 09:54:00PM +0200, Ulrik Vieth wrote: > On 08/17/2010 04:32 PM, Khaled Hosny wrote: > > > >Likely XeTeX does not check this parameter at all and resorts to some > >hard coded default rule thickness. > > No, that cannot be the reason. I know for sure that XeTeX does load > some (but not all) of the OpenType font parameters and maps them to > TeX fontdimen parameters. I have seen that myself in the web2c > sources: > > http://www.tug.org/svn/texlive/trunk/Build/source/texk/web2c/xetexdir/XeTeXOTMath.cpp?view=markup > > However, I have now realized that the problem is caused by of a > mismatch between the unicode-math LaTeX package and the XeTeX > engine: > > When LaTeX starts out, it has LM/CM fonts preloaded in families 0-3. > When unicode-math loads another OpenType math font with > \setmathfont, it loads the font into a new family, e.g. family 4.
I thought about that possibility, but I don't have the expertise to check it my self, thanks. -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
