From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: italic smallcaps
Date: Wed, 28 Nov 2012 11:32:29 +0100 [thread overview]
Message-ID: <01BADCFB-54E0-4B31-89C8-F9F105A00A21@gmail.com> (raw)
In-Reply-To: <CAF=dkzxPgUn734jDpTwR6x1pqfycNEeApttZEkKh7rwFSfpdhg@mail.gmail.com>
Am 28.11.2012 um 11:18 schrieb Sietse Brouwer <sbbrouwer@gmail.com>:
> \setff{X} enables font feature X in the current scope --- do I
> understand this correctly?
> --Sietse
It enables a predefined set of features which need to define with \definefontfeature.
There is also a difference between \setff and \addff, with \setff you replace the active
feature set (in most cases “default”) with a new set, you can see it in the first line
because kerning etc. is disabled after \setff which I haven’t included in my list.
In the second line I used \adff which add my new list to the active list and because
of this kerning is still active after \addff.
\definefontfeature[smallcapitals] [smcp=yes]
\definefontfeature[oldstylenumber][onum=yes]
\setupbodyfont[pagella]
\starttext
{VA abc \setff{smallcapitals} VA abc}
{VA abc \addff{smallcapitals} VA abc}
{12345 \setff{oldstylenumber} 12345}
\stoptext
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
___________________________________________________________________________________
prev parent reply other threads:[~2012-11-28 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 8:58 Andreas Mang
2012-11-28 9:00 ` Hans Hagen
2012-11-28 9:06 ` Wolfgang Schuster
2012-11-28 10:18 ` Sietse Brouwer
2012-11-28 10:32 ` 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=01BADCFB-54E0-4B31-89C8-F9F105A00A21@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).