ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Microtypography in ConTeXt
Date: Wed, 6 Apr 2016 21:37:55 +0200	[thread overview]
Message-ID: <57056593.4020901@wxs.nl> (raw)
In-Reply-To: <01e801d19036$f10845e0$d318d1a0$@tosovsky@email.cz>

On 4/6/2016 9:03 PM, Jan Tosovsky wrote:

>> the other things ... well, they are up to the macro package
>
> Indeed, you most likely figured the problem. They are mentioning luatex, while those features require ConTeXt 'preprocessing'.

i didn't read that document but i assume it refers to latex which for 
sure will have some way to set up these feaures; i don't know about 
plain support

in context protrusion and expansion is supported in mkii (pdftex) and 
mkiv (luatex) .. in mkiv there is a bit more control

there is no preprocessing involved (these two features are just part of 
the par builder)

extra kerning and so is done by manipulating node lists (so not an 
engine feature but a context one)

>> i don't think that there are typographical advantages of using pdftex
>> over luatex (at least not with context)
>
> Great, thanks! I am updating article with comparision of various engines, I'll reflect it.
>
> Jan
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | 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
___________________________________________________________________________________

  parent reply	other threads:[~2016-04-06 19:37 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
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 [this message]
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=57056593.4020901@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).