On Sun, 18 Mar 2012 07:56:30 +0100 Wolfgang Schuster wrote:

Am 17.03.2012 um 20:38 schrieb Honza Hejzl:

...

Hi,

I have installed the last standalone version from contextgarden and oops, my (few days) old file does not work properly. My "old" setup of footnotes was like:

\setupfootnotedefinition[loaction=page...] \setupfootnotes[bodyfontsize=8pt, style=\ss...]

Now the context does not understand to that. So I am trying to set up footnotes with \setupnote[footnote] but it seems nothing works. I am not able to use location=serried, location=page, style and so on... Is it connected with some general update? :o(

The command \setupnotedefinition (where \setupfootnotedefinition is a shortcut for \setupnotedefinition[footnote]) is now \setupnotation and “location=serried” is now “alternative=serried”. The \setupnote command (\setupfootnotes is \setupnote[footnote]) has only a “bodyfont” key which accepts “{8pt,sans}” as argument but not “bodyfontsize” key and style is only available for \setupnotation (but as you saw you can add it to bodyfont).

Wolfgang

Looking at strc-not.mkvi and from your explanations above it is still not clear to me how to use the new footnote definitions. We have \setupnotedefinition (with \setupfootnotedefinition=\setupnotedefinition[footnote]), \setupnote (with \setupfootnotes=\setupnote[footnote]), also \setupnotes (=\setupnote ?) Is there any difference between the singular and the plural forms? Also, what parameters are accepted? (I see "% not all make sense here" in strc-not.mkvi) http://wiki.contextgarden.net/Footnotes seems confused (ToDo). In particular, I am still trying to get "next=\autoinsertnextspace" to make \startfootnote\stopfootnote work correctly... Alan

Am 18.03.2012 um 13:14 schrieb Alan Braslau:

On Sun, 18 Mar 2012 07:56:30 +0100 Wolfgang Schuster wrote:

...

Am 17.03.2012 um 20:38 schrieb Honza Hejzl:

...

Hi,

I have installed the last standalone version from contextgarden and oops, my (few days) old file does not work properly. My "old" setup of footnotes was like:

\setupfootnotedefinition[loaction=page...] \setupfootnotes[bodyfontsize=8pt, style=\ss...]

Now the context does not understand to that. So I am trying to set up footnotes with \setupnote[footnote] but it seems nothing works. I am not able to use location=serried, location=page, style and so on... Is it connected with some general update? :o(

The command \setupnotedefinition (where \setupfootnotedefinition is a shortcut for \setupnotedefinition[footnote]) is now \setupnotation and “location=serried” is now “alternative=serried”. The \setupnote command (\setupfootnotes is \setupnote[footnote]) has only a “bodyfont” key which accepts “{8pt,sans}” as argument but not “bodyfontsize” key and style is only available for \setupnotation (but as you saw you can add it to bodyfont).

Wolfgang

Looking at strc-not.mkvi and from your explanations above it is still not clear to me how to use the new footnote definitions. We have \setupnotedefinition (with \setupfootnotedefinition=\setupnotedefinition[footnote]), \setupnote (with \setupfootnotes=\setupnote[footnote]), also \setupnotes (=\setupnote ?) Is there any difference between the singular and the plural forms? Also, what parameters are accepted? (I see "% not all make sense here" in strc-not.mkvi)

1. The \setupnotedefinition was replaced with \setupnotation 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. For backward compatibility you can find things like this: \let\setupnotes\setupnote 3. The argument are same as before (with a few changes)

http://wiki.contextgarden.net/Footnotes seems confused (ToDo).

In particular, I am still trying to get "next=\autoinsertnextspace" to make \startfootnote\stopfootnote work correctly…

Large parts of the code have been rewritten and the next key wasn’t added yet. Wolfgang

Am 18.03.2012 um 23:10 schrieb Alan Braslau:

On Sun, 18 Mar 2012 21:59:17 +0100 Wolfgang Schuster 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