ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mkiv: Charis SIL / SmallCaps
Date: Mon, 21 Jan 2013 18:40:35 +0100	[thread overview]
Message-ID: <10F42F6D-6C83-41A6-9ABB-DDF449191C37@gmail.com> (raw)
In-Reply-To: <20130121122708.75dddb4e@zenlima.eu>


Am 21.01.2013 um 12:27 schrieb Zenlima <post@zenlima.eu>:

> Hi,
> 
> thanks! Now it works with the \setff{..} command.
> 
>> or otherwise also set up kerns
> 
> Sorry, I dont understand what you mean with this. Can you explain it?

When you use

  \definefontfeature[smallcapitals][..,..=..,..]

you have to add “kern=yes” to the list because no kerning happens otherwise.

>> btw, there is a smallcaps feature predefined.
> 
> I thought the \sc is the predefined command for the smallcaps font
> feature. Am I wrong?

No, like the \it. \bf etc commands \sc is a font switch which uses for Latin Modern
a separate font file which contains instead of lowercase letter small capitals, for other
fonts the \sc command load the upright font where the “smallcaps” feature set is
used instead of the “default” set.

Wolfgang
___________________________________________________________________________________
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:[~2013-01-21 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 22:16 Zenlima
2013-01-17 22:53 ` Marco Patzer
2013-01-17 23:16   ` Hans Hagen
2013-01-21 11:27     ` Zenlima
2013-01-21 17:40       ` Wolfgang Schuster [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=10F42F6D-6C83-41A6-9ABB-DDF449191C37@gmail.com \
    --to=wolfgang.schuster@gmail.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).