[NTG-context] fake feature “extend” behaving weirdly

Philipp Gesang Philipp.Gesang at alumni.uni-heidelberg.de
Mon Sep 30 12:09:42 CEST 2013


···<date: 2013-09-30, Monday>···<from: Hans Hagen>···

> On 9/29/2013 11:55 PM, Philipp Gesang wrote:
> > Hi Hans,
> >
> > this got posted on the DANTE list today.
> >
> >    \definefontfeature [quite_wide] [extend=1.5]
> >    \definefont [mainfont] [file:Iwona-Regular.otf]
> >    \definefont [widefont] [file:Iwona-Regular.otf*quite_wide]
> >
> >    \starttext
> >      \mainfont
> >      {\widefont foo} %% comment this line and “bar” is fine
> >      bar
> >      {\widefont baz}
> >    \stoptext
> >
> > The example defines two fonts with the same base font. If the
> > scaled variant is used before the regular one then the latter
> > will appear scaled as well and the spacing (bboxes?) gets messed
> > up.
> >
> > I suspect a relation to this old issue:
> >
> >    http://tracker.luatex.org/view.php?id=829
> >
> > but if I substitute “slant” for “extend” the behavior is
> > different.
> 
> indeed a known bug in the backend that will be resolved once that part 
> of the code has been cleaned up (extend etc is a seldom used hack so has 
> a low priority)

Ah, so it’s the same bug. Thanks for clarifying!

Philipp

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://www.ntg.nl/pipermail/ntg-context/attachments/20130930/429de527/attachment.pgp>


More information about the ntg-context mailing list