![](https://secure.gravatar.com/avatar/61c718f1f821c8c19716564a98c0076b.jpg?s=120&d=mm&r=g)
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? Greeting Andreas
![](https://secure.gravatar.com/avatar/01ccb3e814a4f68fcfad142aa7ded057.jpg?s=120&d=mm&r=g)
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
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
On 13-10-2010 12:48, Andreas Harder wrote:
It seems that if a line starts with \sc{…} the onum-option is ignored. Is there a solution?
fixed in upcoming beta ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (3)
-
Andreas Harder
-
Hans Hagen
-
Michael Murphy