From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Microtypography in ConTeXt
Date: Wed, 6 Apr 2016 10:48:32 +0600 [thread overview]
Message-ID: <40AA119C-EF26-4261-AE1E-21522235EA25@fiee.net> (raw)
In-Reply-To: <01b601d18f85$61ccf760$2566e620$@tosovsky@email.cz>
Am 2016-04-06 um 03:51 schrieb Jan Tosovsky <j.tosovsky@email.cz>:
> <cite>
> Note that character protrusion requires pdfTeX (version 0.14f or later), LuaTeX, or
> XeTeX (at least version 0.9997). Font expansion works with pdfTeX (version 1.20 for
> automatic expansion) or LuaTeX. The package will by default enable protrusion and
> expansion if they can safely be assumed to work. Disabling ligatures requires pdfTeX
> (≥ 1.30) or LuaTeX,
>
> ************************************************
> while the adjustment of interword spacing
> and of kerning only works with pdfTeX (≥ 1.40).
>
> *************************************************
>
> Letterspacing is available with pdfTeX (≥ 1.40) or LuaTeX (≥ 0.62).
> </cite>
Looks like it’s not about interword spacing and kerning in itself, but their *adjustment*.
I didn’t look into that docs, but I’d assume, tracking refers to some logging or visualization of spacing.
AFAIR ConTeXt can do that very nicely (while I never used it and don’t know how to enable it).
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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:[~2016-04-06 4:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <019d01d18f7d$6e3954b0$4aabfe10$@tosovsky@email.cz>
2016-04-05 21:11 ` Hans Hagen
2016-04-05 21:51 ` Jan Tosovsky
[not found] ` <01b601d18f85$61ccf760$2566e620$@tosovsky@email.cz>
2016-04-06 4:48 ` Henning Hraban Ramm [this message]
2016-04-06 7:37 ` Hans Hagen
2016-04-06 7:35 ` Hans Hagen
2016-04-06 19:03 ` Jan Tosovsky
[not found] ` <01e801d19036$f10845e0$d318d1a0$@tosovsky@email.cz>
2016-04-06 19:37 ` Hans Hagen
2016-04-05 20:55 Jan Tosovsky
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=40AA119C-EF26-4261-AE1E-21522235EA25@fiee.net \
--to=texml@fiee.net \
--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).