<NOTE> tag supported in many WIKI applications. The document may be divided into as many sections as desired, each with its own independently-numbered set of notes. Notice that the accompanying demo contains two such sections.
Around 2002 I developed a script similar to this, except that it is processed server-side (using ColdFusion Markup Language or CFML). I still use it regularly and have found it valuable for many projects, some of them coded from scratch and others converted from older word-processed documents. For example, my very long page on The Harris family of Sandy Cove, which contains over 300 endnotes, was originally a WordPerfect file and has been drastically reformatted on several occasions without any manual renumbering of notes, or having to be revised in anything other than a text editor.
For some time, I have hoped to develop a version of the endnote script which posed no server requirements and would be platform-independent. The present implementation is a first attempt at that goal. Strictly speaking, it does not even require access to a web server, because if the files are required only for personal use, they can be accessed from a local drive. I therefore hope it will be useful to those with access only to an HTML server, but also to group projects where there is shared creation of files and not everyone on the team is able to upload files to a web server.
The document should have a structure something like the following excerpt from the source-code for the demo file (with all code pertaining to the endnotes highlighted):
The rules of construction are simple:
<div class="endnoteBlock">…</div>tagset is optionally used to mark each section of the document which is to have an independently-numbered block of endnotes.
<div class="endnoteBlock">…</div>tagset is present, all notes are treated as belonging to a single group.
BODYtag), at the point where the endnotes are to be generated.
<span class="endnote">…</span>tagset is placed in the text at each point where a number pointing at an endnote is to appear.
spantagsets, or other HTML, may be used wherever desired, providing it does not cause naming conflicts with the above.
However, no warantee whatsoever is made or implied for this script, and there are a few specific caviats which must be acknowledged in order to avoid possible disappointment:
BODYtags, or pages with nesting errors or bleeding tags.
<div class="endnoteBlock">…</div>tagsets are block-level elements (which is necessary in order that they may contain other block-level elements), these
divtags will interrupt the style of elements (such as paragraphs) in which they are contained. Thus, if using styles, special case has to be taken to ensure that these containers will inherit the appropriate style from their own
BODYtag. Thus for example if a style is applied to
Ptags sitting directly inside the body of an existing document, and these
Ptags contain endnotes, the style should be transferred to the
CITEtag can be used for in-text citations, although presumably not for very long ones. It would be presumptuous of me to speculate as to how this would affect the experience of a visually-impaired person in using the page, and I would welcome actual response on this matter.
Version 1 of this script used
<div class="endnote">…</div> where this version uses
<span class="endnote">…</span>. HTML files written using version 1 need only this one change to be made, and they will work with the new
endnotePlacement.js and endnoteStyle.css files.
John Blythe Dobson
University of Winnipeg Library
Released 25 May 2007
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 License.