ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: David Wooten <dw@trichotomic.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: hz and protrusion
Date: Sun, 2 Mar 2008 21:08:24 -0800	[thread overview]
Message-ID: <C55FA08A-A6FC-481B-B0F1-2C2A22B8AC1A@trichotomic.net> (raw)
In-Reply-To: <47B5D521.1090200@wxs.nl>

Hans,

This is great news, thanks a million.

Where should I keep an eye out for the interface extensions?

Dave

On Feb 15, 2008, at 10:08 AM, Hans Hagen wrote:

> Hi,
>
> The latest luatex beta + mkiv support hz and protruding. The user
> interface will be extended a bit, but for the moment it goes as  
> follows:
>
> % engine=luatex
>
> % \setupfontexpansion [quality][stretch=2.5,shrink=2.5,step=. 
> 5,factor=1]
>
> \setupfontexpansion[oeps][a=1,b=2]
>
> \setuptolerance[verytolerant,stretch] \showframe
>
> \starttext
>
> \definefontfeature[demo][default] 
> [mode=node,expansion=quality,protrusion=pure]
>
> \start
>     \definedfont[Serif*demo at 12pt]           \enableadjusting
> \enableprotruding \input tufte \par
>    %\definedfont[name:optimanova*demo at 12pt] \enableadjusting
> \enableprotruding \input tufte \par
> \stop
>
> \stoptext
>
> (or the usual \setupalign options)
>
> As you may deduce from this example, handling is gone in mkiv. This  
> not
> only safes some 40K format file, but the new mechanism also runs  
> faster
> (some 10% overhead on 300 pages of pure text, which is rare).
>
> At some point we need to extend the hz/protruding vectors in mkiv to
> cover non latin scripts as well (currently they default to factors of
> 1). As with mkiv, latin glyphs fall back to their shape parent.
>
> Under some circumstances hz may not work as expected. Fixing this is  
> on
> the agenda for the next luatex beta release.
>
> Hans
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-03-03  5:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 18:08 Hans Hagen
2008-03-03  5:08 ` David Wooten [this message]
2008-03-03  9:57   ` Hans Hagen

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=C55FA08A-A6FC-481B-B0F1-2C2A22B8AC1A@trichotomic.net \
    --to=dw@trichotomic.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).