Am 18.03.2012 um 23:10 schrieb Alan Braslau:

> On Sun, 18 Mar 2012 21:59:17 +0100
> Wolfgang Schuster <schuster.wolfg...@googlemail.com> wrote:
> 
>> 2. Many of the \define… and \setup… commands are now auto generated
>>   from \installcommandhandler which generates only one setup-command
>>   which can be used for global (i.e. \setup…[..,..=..,..]) and local
>>   (i.e. \setup…[…][..,..=..,..]) settings.
> 
> Thank you Wolfgang for this explanation.
> 
> Do you mean: global (i.e. \define…[..,..=..,..] and local
> (i.e. \setup…[…][..,..=..,..]) settings?

No, I meant with \setupheads[style=bold] you can change the font of each
heading and with \setuphead[section][style=italic] you change only the font
for section. As you can see we have a plural and a singular form of the command.

With the new system to generate the setup commands we have only
\setuphead which handles bot cases.

>> For backward
>> compatibility you can find things like this: \let\setupnotes\setupnote
> 
> OK, but is this a good idea?
> I thought that mkii is kept around for backward compatibility
> and that mkiv takes the liberty to rationalize the syntax,
> sometimes sacrificing backwards compatibility in order not to be
> encumbered with inconsistent syntax, whenever possible.
> 
> Indeed, this sometimes generates much discussion on the mailing list
> when we discover that our favorite command has been removed
> or renamed - a good way of testing to see if we are active and alert. :)

It’s better to promote the new commands but we should take time
until the old variants vanish because we have to get used to them.

Wolfgang
___________________________________________________________________________________
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 via email to