From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: faked fonts not working
Date: Mon, 24 Jun 2013 20:09:04 +0200 [thread overview]
Message-ID: <51C88B40.8000003@wxs.nl> (raw)
In-Reply-To: <51C888C1.7050308@web.de>
On 6/24/2013 7:58 PM, Pablo Rodríguez wrote:
> On 22/06/13 16:03, Pablo Rodríguez wrote:
>> Dear list,
>>
>> as far as I can remember, this used to work in the past:
>>
>> \setupbodyfontenvironment[default][em=italic]
>> \usemodule[simplefonts]
>>
>> \definefontfeature[fakeitalic][default][slant=.25]
>> \definefontfeature[fakebold][default][extend=2]
>> \definefontfeature[fakebolditalic][default][slant=.25, extend=2]
>> \setmainfont[Larabiefont][italicfont={* Regular}, boldfont={*
>> Regular}, bolditalicfont={* Regular}, italicfeatures=fakeitalic,
>> boldfeatures=fakebold, bolditalicfeatures=fakebolditalic]
>
> I have experienced that one fonts work with this and others don’t.
>
> Is there no way to force these features on all fonts?
\starttext
\definefontfeature[fakeitalic][default][slant=.25]
\definefontfeature[fakebold][default][extend=1.2]
\definefontfeature[fakebolditalic][default][slant=.25, extend=1.2]
\definedfont[Serif*fakeitalic]\input tufte
\definedfont[Serif*fakebold]\input tufte
\definedfont[Serif*fakebolditalic]\input tufte
\stoptext
you'll notice that there is a (known) bug in luatex (the backend):
depending on the order of definitions such a fake can get lost in the
middle of a line when first applied
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-06-24 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 14:03 Pablo Rodríguez
2013-06-24 17:58 ` Pablo Rodríguez
2013-06-24 18:09 ` Hans Hagen [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=51C88B40.8000003@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).