From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Michael Saunders <odradek5@gmail.com>
Subject: Re: ntg-context Digest, Vol 69, Issue 95
Date: Thu, 18 Mar 2010 14:29:23 +0100 [thread overview]
Message-ID: <4BA22AB3.6070002@wxs.nl> (raw)
In-Reply-To: <54d7f5601003180400o2ea155a7j6aa3d7ada27d61fa@mail.gmail.com>
On 18-3-2010 12:00, Michael Saunders wrote:
> Wolfgang Schuster:
>
>> \setupbodyfont[pagella]
>>
>> \definefontfeature[smcp][smcp=yes]
>> \definefontfeature[frac][frac=yes]
>>
>> \setuphead[chapter][textstyle=\addfs{frac}\addfs{smcp}]
> ....
>
> This is just an example, but what I think you mean to say by it is
> that the new command \addfs{} has the behavior I describe, but only
> for otf features and not for things like switching to semibold or to
> condensed (and, presumably, even if I'm able to define my own commands
> for things like semibold, something like:
> \sb ABC \it DEF
> would set the DEF at regular weight).
>
> Since I've never seen anyone talk about \addfs{}, but only give
> examples, I'm guessing (but just guessing) that there exists somewhere
> a list of what otf features are active at any given point, and that
> this command can add to that list. That's great. I might not need it
> anytime soon, but I'm just curious---are there other commands of this
> kind? Maybe something to clear the list?
this mechanism is one of the spin off's of the oriental tex project
(where we play font fonts that have 50+ stylistic variants and 20+
justification variants)
\addfontfeaturetoset {..} % merge
\subtractfontfeaturefromset {..} % merge
\addfontfeaturetofont {..} % overload
\subtractfontfeaturefromfont{..} % overload
\let\addfs\addfontfeaturetoset
\let\subfs\subtractfontfeaturefromset
\let\addff\addfontfeaturetofont
\let\subff\subtractfontfeaturefromfont
there's also \setfontfeature and \setff
in principle you can also use this to let fonts adapt to a language /
script and in due time i'll add it as automatism there
(internally in mkiv this is what we call dynamic features)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-03-18 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1011.1268906049.26807.ntg-context@ntg.nl>
2010-03-18 11:00 ` Michael Saunders
2010-03-18 13:29 ` Hans Hagen [this message]
2010-03-18 13:30 ` Hans Hagen
2010-03-18 14:19 ` 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=4BA22AB3.6070002@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=odradek5@gmail.com \
/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).