From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: Alan Braslau <alan.braslau@cea.fr>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: footnotes setup
Date: Mon, 19 Mar 2012 09:27:22 +0100 [thread overview]
Message-ID: <6BCC82BD-A44C-4A2D-AEF0-E0B543C3BBE0@googlemail.com> (raw)
In-Reply-To: <20120318231007.62efec68@iram-hb-003386.extra.cea.fr>
Am 18.03.2012 um 23:10 schrieb Alan Braslau:
> On Sun, 18 Mar 2012 21:59:17 +0100
> Wolfgang Schuster <schuster.wolfgang@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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-03-19 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 19:38 Honza Hejzl
2012-03-18 6:56 ` Wolfgang Schuster
2012-03-18 12:14 ` Alan Braslau
2012-03-18 15:45 ` Steffen Wolfrum
2012-03-18 20:59 ` Wolfgang Schuster
2012-03-18 22:10 ` Alan Braslau
2012-03-19 8:27 ` Wolfgang Schuster [this message]
2012-03-18 16:36 ` Pablo Rodríguez
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=6BCC82BD-A44C-4A2D-AEF0-E0B543C3BBE0@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=alan.braslau@cea.fr \
--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).