From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Setting up protrusion, side-effects
Date: Wed, 28 Jul 2010 09:35:07 +0200 [thread overview]
Message-ID: <4C4FDDAB.1070209@googlemail.com> (raw)
In-Reply-To: <3382.79595.qm@web56308.mail.re3.yahoo.com>
Am 28.07.10 02:31, schrieb Martin Althoff:
> When setting up protrusion, I noticed it "disappearing" despite being defined/setup. In a text, when I changed the font from Palatino to Sabon (with \setupbodyfont[sabon]), protrusion stopped working. Changing back to palatino, with nothing else changed, protrusion appeared again.
>
> Note: getting the latest minimals update did not change anything: context: version: 2010.07.27 16:30, LuaTeX, Version beta-0.60.2-2010070117 on OSX 10.6.4
>
> The following test file showed that if the \setupbodyfont takes place before \definefontfeature and \setupalign, protrusion fails completely. In the example 1 below it fails. Disabling the top \setupbodyfont and enabling the bottom \setupbodyfont gets it to work. However, it will fail for both Palatino and Sabon! I could not create an example for one font working and the other not.
>
> Is the order of declaration important? That would be unusual in context by what I have seen so far. Am I missing something?
Fonts are sometimes special and when ypu load a font it's setting
(e.g. ligatures, protrusion etc.) are frozen. To change the settings
you need \definefontfeature before \setupbodyfont, of yourse there is
\addff to change a certain setting but this is only meant for local
changes and not for global range.
Wolfgang
___________________________________________________________________________________
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:[~2010-07-28 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 0:31 Martin Althoff
2010-07-28 7:35 ` Wolfgang Schuster [this message]
2010-07-28 9:20 ` Martin Althoff
2010-07-29 10:12 Martin Althoff
2010-07-29 18:48 ` Hans Hagen
2010-07-31 6:17 ` Martin Althoff
2010-07-31 9:48 ` Hans Hagen
2010-07-31 12:50 ` Martin Althoff
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=4C4FDDAB.1070209@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).