From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: ntg-context Digest, Vol 69, Issue 95
Date: Thu, 18 Mar 2010 06:00:13 -0500 [thread overview]
Message-ID: <54d7f5601003180400o2ea155a7j6aa3d7ada27d61fa@mail.gmail.com> (raw)
In-Reply-To: <mailman.1011.1268906049.26807.ntg-context@ntg.nl>
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?
That leaves me the problem of installing sets with more than two
weights, more than one width and several design sizes, as we spoke
about earlier. It's late in the day here, but I hope to try that out
tomorrow. Just to make sure I understand the example you and Mojca
gave me:
> \definebodyfont [default] [rm]
> [tf=Serif sa 1,
> bf=SerifBold sa 1,
> it=SerifItalic sa 1,
> sl=SerifSlanted sa 1,
> bi=SerifBoldItalic sa 1,
> bs=SerifBoldSlanted sa 1,
> sc=SerifCaps sa 1]
>
> You could add your
> in=SerifYourFontVariantName sa 1,
> bd=SerifYourOtherFontVariantName sa 1,
I think I can add this block to the top of my own typescript,
duplicate the existing definitions as shown, and, when making up my
own, I think I'm free to define font switches with more than two
characters, so, e.g.:
sbexit=SansSemiboldExtendedItalic sa 1
so, I won't be able to switch variants of this kind independently, but
at least I can get them installed.
After that, I'll move on to the optical examples and see what I can do
about that (I'm hoping they provide for automatic switching of design
size).
Thank you,
-- m
___________________________________________________________________________________
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 parent reply other threads:[~2010-03-18 11:00 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 [this message]
2010-03-18 13:29 ` Hans Hagen
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=54d7f5601003180400o2ea155a7j6aa3d7ada27d61fa@mail.gmail.com \
--to=odradek5@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).