From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: special case to disable italic correction
Date: Tue, 28 Jan 2014 15:14:19 +0100 [thread overview]
Message-ID: <52E7BB3B.8060907@wxs.nl> (raw)
In-Reply-To: <52E560D7.40403@gmx.es>
On 1/26/2014 8:24 PM, Pablo Rodriguez wrote:
> Hi Hans,
>
> after reading the relevant part for italic correction in fonts-mkiv.pdf
> and enabling it in my documents, I have found a case in which the italic
> correction could be improved.
>
> My settings are:
>
> \definefontfeature[default][default][itlc=yes]
> \setupitaliccorrection[global,always]
>
> If I get it right, the italic correction should be avoided before points
> and commas (these are all the exceptions I can imagine for this case).
> The explanation is simple: the space is already at the base line, since
> at the glyph base, the inclination of the italic or slanted glyph makes
> the right side-bearing larger at the baseline. The issue with italic
> correction is mainly with ascenders or at the cap height, but I think it
> isn’t at the base line (or the descenders). Because of that I think it
> is important to disable italic correction before points and commas.
>
> The sample shows the issue:
>
> \setuppagenumbering[location=]
> \definefontfeature[default][default][itlc=yes]
> \setupitaliccorrection[global,always]
> \starttext
> \startTEXpage[offset=1ex]
> Abf. {\em Abf}.\\
> Abf, {\em Abf},\\
> Abf. {\it Abf}.\\
> Abf, {\it Abf},
> \stopTEXpage
> \stoptext
>
> I think it might be worth considering.
>
> Many thanks for your help and your excellent work,
Hard coded char checking is talking all punctuation is tricky, so i now
use a threshold instead (enabled by default).
\disabledirectives[typesetters.threshold]
% % % % test:
\definefontfeature
[default]
[default]
[itlc=yes]
\setupitaliccorrection
[global,always]
% \enabletrackers[typesetters.italics]
\starttext
\startTEXpage[offset=1ex]
f. {\em f}.\par f, {\em f},\par f. {\it f}.\par f, {\it f},\par
f: {\it f}:\par f; {\it f};\par
x. {\em x}.\par x, {\em x},\par x. {\it x}.\par x, {\it x},\par
x: {\it x}:\par x; {\it x};\par
\stopTEXpage
\stoptext
Will be in next beta.
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:[~2014-01-28 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 19:24 Pablo Rodriguez
2014-01-28 14:14 ` Hans Hagen [this message]
2014-01-28 17:51 ` Pablo Rodriguez
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=52E7BB3B.8060907@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).