🚀 go-pugleaf

The suggestion to use :EN-:eEN. for endnotes vs. :FN-:eFN for footnotes
is correct, but it raises a problem that has concerned me for a while.

I often write a paper for one style (e.g., a technical report)
where footnotes, tables, and figures are in-line,
then want to produce it in another style (journal submission)
which requires these all to be at the end.

In Waterloo script I tried to make the :FN/:EN tag variable, like this:

.im gmlgdoc
..sr fn=en
:gdoc
Some text
:&fn.
A note.
:e&fn.
More text

Unfortunately, the :gml tags seem to be scanned before substitution,
since this produces:

1
-
        Some text :en A note.  :een More text


A thornier problem is how to make figures/tables come out inline
or at the end of the paper, since this standardly requires moving
the actual blocks of text (:FIG--:eFIG), rather than simply doing
a global change of :FN to :EN.

It turns out, if you examine the code for :EN, that they work by
formatting the text into a 'floating block', delimited by
  .fb begin
  .fb end

I was able to modify the code for figures/tables to allow a PLACE=BACK
attribute value which would produce my figures *or* tables after the
end of the :BODY.  I also defined another value, PLACE=BACKHERE
which in addition prints the lines
                      ---------------------
                       Figure 12 about here
                      ---------------------

at the point where the :FIG occurs.

The problem is that ALL floating blocks seem to be stored in a single
area, and when they are dumped at the end, they come out all interspersed-
end notes, tables, figures, in the order defined.  This is not what
happens in the lists of figures and tables which use different table-of-
contents storage areas.

Is there, in fact, a way to define different types of floating blocks
or to distinguish them by their contents?  If not, perhaps the .fb
control word should be extended to allow
  .fb <n> begin
where <n> would specify a particular storage region.

Is there a different way to accomplish these things?  I'd be glad
to send my modification of the figtab macro to anyone who's interested.

Michael