2017-01-25 11:07 GMT+01:00 Philip Taylor <p.tay...@rhul.ac.uk>: > Ulrike Fischer wrote: > > There was once a long discussion about this xetex problem around > > here http://tug.org/pipermail/xetex/2011-February/020072.html > > It is unclear if it is engine bug and imho no one ever added > > something to the issue tracker. > Matthew concluded by writing : > > It seems clear to me that this is a bug, though I'm not sure yet whether > it's better considered as a bug in the XeTeX engine or in the fontspec > package, because it's not clear where the stretchability is being set. > > It seems equally clear to me that the fault cannot lie in the fontspec > package, > since it can be demonstrated with a pure XeTeX example as Jean-François > has shewn ... Whether the fault lies in the XeTeX engine or in the font > is moot, > I believe. >
It might be set in the font and XeTeX just reads it. I do not know how to look inside the font but I heard somewhere, that such mono fonts do exist. > > Philip Taylor > > > > Zdeněk Wagner > http://ttsm.icpf.cas.cz/team/wagner.shtml > http://icebearsoft.euweb.cz > > > -------------------------------------------------- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex >
-------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
