ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "N. Lindenhayn" <mehl@lindenhayn.com>
Subject: Re: LuaTeX + microtype: Small Caps vs. Letter Spacing
Date: Wed, 15 Jun 2011 19:33:07 +0200	[thread overview]
Message-ID: <4DF8ECD3.5030301@wxs.nl> (raw)
In-Reply-To: <4DF8E7ED.5080003@lindenhayn.com>

On 15-6-2011 7:12, N. Lindenhayn wrote:
>>> Ah. Ok that explains it. This means that in latex/fontspec it works
>>> with \setmainfont[Renderer=basic]{...}.
>>
>> I guess so (if basic == basemode). There's nothing wrong with basemode
>> in such cases.
>
> thanks Ulrike and Hans for the comments. It works fine with
> Renderer=basic, although I'm not sure what the side effects of switching
> from Full to Basic will be (it's not a particularly well documented
> feature, at least in the fontspec manual).

In most cases a basic mode is good enough when you want to do 
intercharacter spacing as it makes only sense for scripts that have 
isolated glyphs (even ligatures are to be avoided).

> Sorry for posting to the wrong list; I was thinking about putting this
> in the Lua list, but I remembered someone saying anything Lua related is
> welcome on the ConTeXt list as well... which it probably is, but
> LuaLa(!)TeX is a different story, obviously. I'll try to gather more
> info on the renderer issue, wait a day or two for more comments here,
> and then will post the problem to the Lua list.

it's no problem at all posting here, it's just that you get more respons 
when there is a context example given

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 17:33 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
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 [this message]

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=4DF8ECD3.5030301@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=mehl@lindenhayn.com \
    --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).