ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid ادريس   سماوي حامد" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
	"Hans Hagen" <pragma@wxs.nl>
Subject: Re: new trickery
Date: Fri, 15 Mar 2013 12:11:09 -0600	[thread overview]
Message-ID: <op.wtz14vrtpw6hmh@ishamid-pc> (raw)
In-Reply-To: <514300D6.1010704@wxs.nl>

On Fri, 15 Mar 2013 05:07:02 -0600, Hans Hagen <pragma@wxs.nl> wrote:

>     \start
>         fijn fietsen 123
>         \type{[+os]}\addfeature{f:oldstyle}
>         fijn fietsen 123
>         \type{[+sc]}\addfeature{f:smallcaps}
>         fijn fietsen 123
>         \type{[=os]}\replacefeature{f:oldstyle}
>         fijn fietsen 123
>         \type{[=sc]}\replacefeature{f:smallcaps}
>         fijn fietsen 123
>     \stop

So I hope I have this right:

\addfeature adds a set of features {<feature1>,<feature2>,...<featureN>}  
to the currently defined/enabled stack of OT features

\subtractfeature subtracts a set of features from the currently  
defined/enabled stack

These two seem clear enough. I'm not so clear on the next one:

\replacefeature replaces all the _added_ features (not the default ones  
defined, e.g., in the typescripts I presume) with only those in the  
argument of \replacefeature. Is that right?

\resetfeature pops all features added to the stack (again, I'm assuming  
this does not include the default ones defined, e.g., in the typescripts).

Question: Does/Will this mechanism completely replace \addff et al, or  
will these mechanism ignore each other (e.g., \resetfeature does not pop  
those defined by \addff).

Best wishes
Idris
-- 
Professor Idris Samawi Hamid
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
___________________________________________________________________________________


  reply	other threads:[~2013-03-15 18:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 23:39 Hans Hagen
2013-03-15  2:08 ` Idris Samawi Hamid ادريس   سماوي حامد
2013-03-15  4:18   ` Idris Samawi Hamid ادريس   سماوي حامد
2013-03-15  8:35     ` Hans Hagen
2013-03-15 17:16       ` Jonathan Barchi
2013-03-15 18:29         ` Hans Hagen
2013-03-15 11:07     ` Hans Hagen
2013-03-15 18:11       ` Idris Samawi Hamid ادريس   سماوي حامد [this message]
2013-03-15 18:29         ` Hans Hagen
2013-03-15 18:30         ` Hans Hagen
2013-03-15  8:31   ` Hans Hagen

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.wtz14vrtpw6hmh@ishamid-pc \
    --to=ishamid@colostate.edu \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).