ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Murphy <michael.murphy@uni-ulm.de>
To: ntg-context@ntg.nl
Subject: Re: \setfontfeature-problem
Date: Wed, 13 Oct 2010 14:29:00 +0200	[thread overview]
Message-ID: <4CB5A60C.6020409@uni-ulm.de> (raw)
In-Reply-To: <790B5740-B112-4661-BE4A-F88902369977@rz-online.de>

On 13/10/10 12:48, Andreas Harder wrote:
> Hi all,
>
> please have a look at my example:
>
> \definefontfeature[default][default][mode=node,onum=yes]
> \definefontfeature[sc][default][smcp=yes]
>
> \def\sc{\groupedcommand{\setfontfeature{sc}}{}}
>
> \setupbodyfont[palatino]
>
> \starttext
> \startTEXpage[offset=1ex]
>    {\sc Abc} 0369 \crlf
>    \sc{Abc} 0369
> \stopTEXpage
> \startTEXpage[offset=1ex]
>    0369 {\sc Abc} 0369 \crlf
>    0369 \sc{Abc} 0369
> \stopTEXpage
> \stoptext
>
> It seems that if a line starts with \sc{…} the onum-option is ignored. Is there a solution?
>

\setfontfeature deletes all other features; try \addfontfeaturetoset or 
\addfontfeaturetofont instead (not sure what the difference is).

-- 
Michael Murphy
___________________________________________________________________________________
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:[~2010-10-13 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 10:48 \setfontfeature-problem Andreas Harder
2010-10-13 12:29 ` Michael Murphy [this message]
2010-10-13 12:40 ` \setfontfeature-problem Hans Hagen
2010-10-13 12:43   ` \setfontfeature-problem Andreas Harder

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=4CB5A60C.6020409@uni-ulm.de \
    --to=michael.murphy@uni-ulm.de \
    --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).