ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX + microtype: Small Caps vs. Letter Spacing
Date: Wed, 15 Jun 2011 11:48:10 +0200	[thread overview]
Message-ID: <4DF87FDA.4070302@wxs.nl> (raw)
In-Reply-To: <pr7imog76ivq.dlg@nililand.de>

On 15-6-2011 10:59, Ulrike Fischer wrote:

> With ConTeXt  ver: 2011.06.13 23:08 MKIV  fmt: 2011.6.15  (from the
> minimals) the following fails:

I have to admit that I never used \letterspacefont (luatex offers it as 
a pdftex compatibility feature and as such it's strongly related to 
traditional font handling). The command makes a copy of an internal 
(tfm) + adapted metrics.

> \starttext
>
> \font\test=file:fxlr.otf
> \test abc \letterspacefont\lspfont=\font 500 \lspfont blub

base mode i.e. traditional, so it works

> %breaks: letterspaced font is not small small caps:
> \font\test=file:fxlr.otf:mode=node;+smcp
> \test abc \letterspacefont\lspfont=\font 500 \lspfont blub

a font defined to use node mode, but the copy is a basemode one so it 
has regular shapes and no smallcaps (as there are changed on the fly)

> %letterspacefont works:
> \font\test=file:fxlr.otf:mode=base;+smcp
> \test abc \letterspacefont\lspfont=\font 500 \lspfont blub

base mode i.e. traditional, so it works

> \stoptext

So, when someone wants that feature he/she'd better force basemode which 
is no big deal as letterspacing is selectively applied to often known / 
specially defined fonts.

Anyhow, context users will not use that command / method but instead use 
\kerncharacters[fraction], as in:

{test {\kerncharacters[.5] test \bf test} test}

or

\setuphead
   [section]
   [style=\sca,
    textstyle={\kerncharacters[.5]}]

etc. Support using \letterspacefont is very unlikely to end up in the 
core font code.

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
___________________________________________________________________________________


  reply	other threads:[~2011-06-15  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1523.1308061714.4231.ntg-context@ntg.nl>
2011-06-14 19:52 ` N. Lindenhayn
2011-06-15  7:33   ` Hans Hagen
2011-06-15  8:59     ` Ulrike Fischer
2011-06-15  9:48       ` Hans Hagen [this message]
2011-06-15 10:51         ` Ulrike Fischer
2011-06-15 11:31           ` Hans Hagen
2011-06-15 17:12             ` N. Lindenhayn
2011-06-15 17:33               ` 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=4DF87FDA.4070302@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=news3@nililand.de \
    --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).