On 21 Jan, 2013, at 12:06, Sam Liddicott <address@hidden> wrote:

This is the smallest solution that exactly matches the definition of the problem which is how to remove formatting specifications that have been added since the document started - answer: render in that environment.

+1 for precision.

For sequential; what good would the pre-amble be if it wasn't guaranteed to be executed after the styles and packages but before the rest of the document? At what other point can we know what the documents actual default text style is?

I'm quite ignorant about styles, but this seems a sound argument to me.

As to the solution, I'm not sure I understand: isn't the requirement to execute a macro after the preamble going to couple the typesetter to one specific style file? Unless you code the general system you mention to register macros for execution, that is. (That'd be better I guess)

Wouldn't it be easier to code this in C++ or scheme? The initial environment is already captured by the typesetter, so all that's needed is to write this with-default-style in C++. Or as a secure script in scheme, then define render-footnote using it.

 * Either to implement the system to register a macro for delayed execution at the end of the preamble (and maybe some other points, come to think of it…) Then add the closure idea to the default style. (I like this one best because of the added functionality with the call hooks)

 * Or to write a little bit of scheme/c++ that retrieves the relevant variables and alter render-footnote to use it.

For the second one, this might have been it:

            (tm-define (get-init* s)

              (:secure #t)

              (get-init (tree->string  s)))

            <assign|get-init|<macro|s|<extern|get-init*|<quote-arg|s>>>>

Then:

            <assign|render-footnote|<macro|nr|body|<with|font-family|<get-init|font-family>|<render-footnote*|<arg|nr>|<arg|nr>|<arg|body>>>>>

However, (get-init "font-family") returns "rm" instead of "normal", so this doesn't work and more changes would be needed.

===

Regarding "enclose.ts": a quick scan was a bit confusing because of the big difference with the rest of the packages I've seen. Finding the active macros was a bit hard in all that text, until I realised I shouldn't be "viewing as source". Maybe a small old fashioned yellow comment block explaining that would help.

--

Miguel de Benito.