From: Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: fake feature “extend” behaving weirdly
Date: Mon, 30 Sep 2013 12:09:42 +0200 [thread overview]
Message-ID: <20130930100942.GA26971@phlegethon> (raw)
In-Reply-To: <52493443.1040003@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1187 bytes --]
···<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
[-- Attachment #1.2: Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-09-30 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 21:55 Philipp Gesang
2013-09-30 8:20 ` Hans Hagen
2013-09-30 10:09 ` Philipp Gesang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130930100942.GA26971@phlegethon \
--to=philipp.gesang@alumni.uni-heidelberg.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).