From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Selectively not using a font feature
Date: Mon, 07 Dec 2009 11:12:21 -0700 [thread overview]
Message-ID: <op.u4kx6va4pw6hmh@ishamid-pc> (raw)
In-Reply-To: <20091207091649.GW13955@katherina.student.utwente.nl>
Hi,
On Mon, 07 Dec 2009 02:16:49 -0700, Matthijs Kooijman <matthijs@stdin.nl>
wrote:
> \definefontfeature[default][default][onum=yes]
> \definefontfeature[normalnum][default][onum=no]
> And in the text use: {\definedfont[Serif*normalnum]0 to 7}
\definefontfeature[default][script=latn,<fea1>=yes,<fea2=yes>,...<fea<n>=yes>,...onum=yes]
\definefontfeature[onum][onum=yes]
\definedfont[Serif*default]
\subff{onum}
should subtract onum from the current stack.
These are not accumulative, they only act on the original featureset --
default here -- so no
\subff{featureset1} \addff{featureset2} effects
For accumulative effects you need \addfs/\subfs, but those are broken at
the moment.
Best wishes
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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:[~2009-12-07 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 22:45 Matthijs Kooijman
2009-12-07 8:50 ` Hans Hagen
2009-12-07 9:16 ` Matthijs Kooijman
2009-12-07 10:22 ` Hans Hagen
2009-12-07 18:12 ` Idris Samawi Hamid ادريس سماوي حامد [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=op.u4kx6va4pw6hmh@ishamid-pc \
--to=ishamid@colostate.edu \
--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).