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? > 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. :) Alan -- Alan Braslau CEA DSM-IRAMIS-SPEC CNRS URA 2464 Orme des Merisiers 91191 Gif-sur-Yvette cedex FRANCE tel: +33 1 69 08 73 15 fax: +33 1 69 08 87 86 mailto:alan.bras...@cea.fr ___________________________________________________________________________________ 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 ___________________________________________________________________________________
