ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: ud@mucschach.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Some layout questions
Date: Thu, 28 Aug 2008 11:05:25 +0200	[thread overview]
Message-ID: <48B66A55.9010100@elvenkind.com> (raw)
In-Reply-To: <005f01c908d9$712b7a50$53826ef0$@de>

Hi Ulrich,

Ulrich Dirr wrote:
>>
>> Afaics, everything else looks ok.
> 
> But has no effect :-(

I was apparently still sleeping when I wrote that. Here is what
works for me:

% engine=luatex
\definefontfeature
    [default][default]
    [protrusion=quality,expansion=quality,mode=node,script=latn]

\definetypeface[kievit][rm][serif][times][default]
\definetypeface[kievit][ss][serif][times][default]
\definetypeface[kievit][tt][mono][modern][default][rscale=1.12]
\definetypeface[kievit][mm][math][iwona] [default][rscale=1.02]

\setupbodyfont[kievit,ss,10pt]

\starttext
\showframe
\setupalign[hanging] \input tufte
\stoptext
%

I used [serif][times] instead of [sans][kievit] because I don't have
the font, but that should not matter. Things to note:

* The relative ordering of commands matters, your \definefontfeature
   was too late. I'll try to document that in the manual.
* You only need \usetypescript[xxx] if the \definetypeface
   commands are actually inside of a \starttypescript[xxx] block.
* It turns out I could not use [features=hz] because at a lower
   level [times] already sets up [features=default], and that setting
   wins over the high-level one.
   But in your new setup for kievit, you could also do it this way:
     \definefontfeature
        [hz][default]
        [protrusion=quality,expansion=quality,mode=node,script=latn]
      \definetypeface[kievit][rm][serif][times][default][features=hz]
   just make sure not to attach any [features=...] to the
   \definefontsynonym commands.

Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2008-08-28  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 10:59 Ulrich Dirr
2008-08-27 14:07 ` Taco Hoekwater
2008-08-28  6:43   ` Ulrich Dirr
2008-08-28  8:50     ` Wolfgang Schuster
2008-08-28  9:05     ` Taco Hoekwater [this message]
2008-08-28 10:25       ` Ulrich Dirr
2008-08-28 10:32         ` Taco Hoekwater

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=48B66A55.9010100@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=ntg-context@ntg.nl \
    --cc=ud@mucschach.de \
    /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).