From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: fake feature “extend” behaving weirdly
Date: Mon, 30 Sep 2013 10:20:19 +0200 [thread overview]
Message-ID: <52493443.1040003@wxs.nl> (raw)
In-Reply-To: <20130929215542.GA22800@phlegethon>
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)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-09-30 8:20 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 [this message]
2013-09-30 10:09 ` Philipp Gesang
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=52493443.1040003@wxs.nl \
--to=pragma@wxs.nl \
--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).