From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: copyfont and font features
Date: Thu, 17 Nov 2016 15:05:55 +0100 [thread overview]
Message-ID: <1xj8jgjbquc56.dlg@nililand.de> (raw)
In-Reply-To: <e6518ee0-a412-a72f-81de-9f3185254791@wxs.nl>
Am Thu, 17 Nov 2016 13:07:22 +0100 schrieb Hans Hagen:
>> Simply using \let doesn't work when you want locally a different
>> expansion behaviour:
>>
>> ! error: (font expansion): font has been expanded with different
>> stretch limit.
>>
>> (with pdflatex + lualatex), that's imho the reason why microtype
>> copies the fonts.
>
> in fact that is also the case with pdftex: afaik expansion and
> protrusion values are global and once a font is used they get frozen
Yes, exactly.
>
> in luatex (at least the lua font loader) one can set the expansion at
> definition time (which is more natural but not possible in pdftex)
Yes, but I understand that -- if possible -- microtype prefers code
that works in pdftex *and* luatex.
>> The question is if microtype can easily retrieve the current font
>> features and if it will slow down the code much if it has to
>> redefine fonts again and again.
> that's a matter of implementation
Yes, the maintainer of microtype has been informed about the problem
and can now look for a solution ...
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-11-17 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:17 Ulrike Fischer
2016-11-17 8:46 ` Hans Hagen
2016-11-17 10:02 ` Ulrike Fischer
2016-11-17 12:07 ` Hans Hagen
2016-11-17 14:05 ` Ulrike Fischer [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=1xj8jgjbquc56.dlg@nililand.de \
--to=news3@nililand.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).