From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: style=\setff{…} deprecated?
Date: Fri, 21 Jan 2011 11:38:32 +0100 [thread overview]
Message-ID: <D7920300-0427-4B5C-AEB0-785A2A52507A@uni-koblenz.de> (raw)
Hi all,
I have some setups like:
\setupfootnotes[textstyle=\plf] or
\setupitemize[style=\plf] where \plf is defined as:
\definefontfeature[plf][default] [pnum=yes,lnum=yes]
\def\plf{\groupedcommand{\setfontfeature{plf}}{}}
With the newest beta this setup fails. For footnotes one can use textcommand=\plf\high, but there is no symcommand for item groups. Asides from the old style=\setff{…} behaviour was very convenient, is there a work around?
Here is an example.
\definefontfeature[default] [default] [mode=node,onum=yes]
\definefontfeature[plf] [default] [pnum=yes,lnum=yes]
\definefontfeature[tlf] [default] [tnum=yes,lnum=yes]
\def\plf{\groupedcommand{\setfontfeature{plf}}{}}
\def\tlf{\groupedcommand{\setfontfeature{tlf}}{}}
\setupbodyfont[palatino]
\setupitemgroup
[itemize]
[command=\tlf, % sets the whole environment (besides the first item number)
% style=\setff{tlf}, % used to work (style=\tlf didn't)
]
\starttext
\startitemize[n,columns][stopper=\vl,n=3]
\dorecurse{114}{\item test 0123}
\stopitemize
\stoptext
Greeting
Andreas
___________________________________________________________________________________
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 reply other threads:[~2011-01-21 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 10:38 Andreas Harder [this message]
2011-01-21 13:48 ` Wolfgang Schuster
2011-01-21 14:35 ` 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=D7920300-0427-4B5C-AEB0-785A2A52507A@uni-koblenz.de \
--to=aharder@uni-koblenz.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).