Re: endnotes

[Dan Emory <danemory@xxxxxxxxxxxx>]

At 11:31 PM 4/5/00 -0700, mheine@internorth.com wrote:
>Good grief:
>
>450 footnotes in a 24-chapter long book to be converted into endnotes. The
>imminent arrival of Frame 6 will no doubt make the fact that some among us once
>had the temerity  to request  true endnote functionality an even more distant
>memory (unless I missed the relevant section in Adobe's announcement...).
>
>Up until Frame 512/Win or so I relied on Morten Rasmussen's nifty Foot2End
>program for file-by-file conversion, but as of Frame 556, I cannot seem to get
>it to work anymore. Can anyone suggest a utility that will automate the
>conversion process, footnotes to endnotes, in any way?
===========================================================
Below are two posts I made in February 1999:
+++++++++++++++++++++++++++++++++++++++++++++++
I've been testing a solution to the FM footnote problem by producing
endnotes instead. It seems to work fine, and eliminates the hated migration
of footnotes to the wrong page.

The solution has two parts:
1. Make the footnote text very small and invisible, so it takes up hardly
any space. This involves the following substeps:
	a. Remove the footnote reference frame from the
           reference page so as to eliminate the footnote line.
	b. Set the size of the footnote text to 2 points. 
           They're still visible and editable by zooming
           in to 800%.
	c. At print time, globally update all footnote paragraphs
           to make them invisible by changing the text color 
           to white.
2. Compile the invisible footnotes into endnotes by generating a List of
Paragraphs (LOP) containing the numbers and text of of all footnote
paragraphs, with page number references.

During testing of this approach, I found that I could place at least two
footnotes on a page when one of the footnote references was in the last text
line of the page. The two footnotes occupy so little vertical space that the
last text line above the footnotes is less than  0.2" from the bottom of the
text frame. Obviously, more than two such footnotes could appear on a page
when none of them are in the last few lines of text on the page.

Has anyone else tried this method, and if so, are there problems with it I
haven't found yet?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
In my earlier post on this subject, I proposed a solution to the
footnote/endnote problem by making the footnote text small and invisible,
and producing endnotes by generating a LOP that compiles a numbered list of
footnotes, with page references, if desired.

Here is more information about the solution:
1. The footnotes must be numbered sequentially throughout the file for the
solution to work (see item 3 below for the reason why).

2. The Footnote paragraph tag is set up with a font size of 2 pts, and line
spacing of 2 pts (they're still editable by zooming in to 800%). At print
time, the footnote paragraphs are globally updated to change the text color
from black to white so as to make them invisible. The footnote reference
frame is deleted so the extra space it produces is eliminated.

With this setup, I've found that, with one footnote inserted in the last
text line on a page, two more footnotes can be inserted in lines above the
last text line without producing the hated migration of footnotes to the
next page. If no footnote is inserted in the last few lines, more than 3
footnotes per page can be accommodated without producing footnote migration.
The total vertical space occupied by all the footnotes on a page is
calculated using the following formula:

        H = 4(n-1) + 2
Where H = the vertical height in points of all the footnotes on a page, and
n = the number of footnotes on the page.

3. The LOP reference page specifies autonumbering of the FootnoteLOP
paragraphs to replicate the original footnote numbers (this is necessary
since footnote paragraphs do not have autonumbers that can be picked up in a
generated list).

If an endnote LOP for a multi-file book is being generated, the footnotes
will still start at 1 within each file (another FrameMaker anomaly), thus
you must include the chapter title paragraph in the generated LOP, and that
paragraph must have its autonumbering set up to reset the footnote counter
so that the footnotes within each chapter will be properly numbered. That
is, the autonumbering for the ChapTitleLOP paragraph must be set up as:

        <n+>< =0>
          |    |
          |    |
          |    ----------The footnote counter
          |
           -----The chapter number counter

And the autonumbering of the FootnoteLOP paragraph must be set up as:

        < ><n+>  

4. Since FrameMaker numbers table footnotes (in the default setup) as a, b,
etc., and restarts the numbering in each table, the TableFootnote paragraph
cannot be included in the generated LOP for the endnotes, because the
autonumbering described in 3 above would then fail to replicate the original
footnote numbers. That is, table footnotes must be kept readable in the
document, since they cannot appear in the endnotes.


     ====================
     | Nullius in Verba |
     ====================
Dan Emory, Dan Emory & Associates
FrameMaker/FrameMaker+SGML Document Design & Database Publishing
Voice/Fax: 949-722-8971 E-Mail: danemory@primenet.com
10044 Adams Ave. #208, Huntington Beach, CA 92646
---Subscribe to the "Free Framers" list by sending a message to
   majordomo@omsys.com with "subscribe framers" (no quotes) in the body.


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **