X

When a digression just can't be thrown away

Footnoting

Some non-fiction works use footnotes to digress from the main thesis and explore interesting side-topics. Endnotes are similar to footnotes, except they appear in a group at the end of a chapter or the end of the book.

Blue-phrase has special notemark notation to assist with coalescing and placing footnotes. When an author determines that a sentence or paragraph should be removed from the main composition and placed into a footnote, he can simply delimit the text with asterisk doppelmarks that look like this ** ... **.

Unlike listmarks, citemarks and glossmarks, notemarks do not have interscribed expressions or adjunct expressions, instead the entire text between the doppelmarks is removed from the reading flow and moved to the footnote area.

Here are two examples of notemarks:

This journal ** Gibson presented his journal to the Missouri Historical Society in 1873.** is published here for the first time.

A general order ** Order No. 13, Aug. 17, 1846.** was read at the head of the company.

When this blue-phrase is compiled, the notes are omitted and replaced with footnote symbols. Here's how the example would be emitted:

<p>This journal <a id=nt20 href='#nt24'>*</a> is published here for the first time.</p>

<p>A general order <a id=nt21 href='#nt25'></a> was read at the head of the company.</p>

Building the footnotes/endnotes

The text from all of the notemarks in your manuscript are gathered together and emitted where a build pragma occurs. Notes can be formatted as footnotes (* † ‡ ...) or endnotes (1, 2, 3 ...). Here's what it might look like:

div {
h1 Chapter 1 Endnotes
!build-notes *format=endnotes
}

Then, the relevant portion of the emitted output (ignoring all other notemarks, for brevity) would look like this:

<div>
<h1>Chapter 1 Endnotes</h1>
<ol>
...
<li id=nt24 ><sup><a href='#nt20'>*</a></sup><small>Gibson presented his journal to the Missouri Historical Society in 1873.</small></li>
<li id=nt25 ><sup><a href='#nt21'></a></sup><small>Order No. 13, Aug. 17, 1846.</small></li>
...
</ol>
</div>

Each footnote is hyperlinked back to the place in the body matter where it was written.

Further Reading

BLUE-PHRASE Basics Getting started with symbolic endophrasing. Learn how to author documents with many of the commonly used typographic techniques found in word processors, by using BLUE-PHRASE symbolic endophrasing. There are only a few basic rules to learn.

BLUE-PHRASE Essentials A primer for effectively using BLUE-PHRASE. Learn the essentials necessary to effectively use BLUE-PHRASE, and discover techniques to perform commonly occurring tasks with greater ease using shorthand notation.

BLUE-PHRASE + CSS The fundamentals of styling Learn how to style BLUE-PHRASE with Cascading Style Sheets.

BLUE-PHRASE Quick Ref Syntax cheat sheet A quick reference to BLUE-PHRASE syntax.

Related Sites

BLUE-PHRASE HTML templating and blogging. A computer language for solving problems related to reading, writing, and publishing.

RWSERVE Caching HTTP/2 server with dynamic JavaScript plugins. HTTP/2 is all about speed: fewer bytes, reduced latency, longer connections, multiplexing and prioritization.

READ WRITE GROK A different take on a tech blog. Follow along as Tangled Web Services boldly goes where tech has gone before.

Contact Us

Read Write Tools is able to offer free and low-cost software products because it has low overhead and limited staff. We are happy to answer your customer service and technical support questions when our self-service options aren't able to meet your needs.

Many of the most common customer service issues can be resolved without our help. Check the licensing and accounts pages for ways to resolve issues related to registration, customer numbers, passwords and access keys.

Technical support issues can sometimes be resolved using one of the public forums like Stack Overflow, so search for error messages, blue-phrase syntax questions, and technical problems there. For best results include the name of the product in your search, like rwdoc, rwreuse, rwserve, etc.

For problems that you can't resolve yourself, ask for help.

Connections

Twitter @ReadWriteTools Latest announcements from our developer advocate.

Medium @joehonton Using distraction-free tools for better reading, writing and publishing, and loving it!

Copyright

Copyright © 2020 Read Write Tools, All Rights Reserved.

Software Licensing

Read Write Tools Software License Agreement. The ReadWriteView, ReadWriteNote, ReadWriteDoc, and ReadWriteReuse desktop applications; and the ReadWriteServe server software may be used only in conjunction with the purchase of a software license.

BLUE PHRASE Software License Agreement. The Blue-phrase processor and Blue-phrase symbolic endophrasing may be used only in conjunction with the purchase of a software license.

Read Write Tools Open Source Software. Read Write Tools publishes some of its software portfolio under open source licenses, including RWSERVE plugins, web components, CSS style sheets, editor themes, command line build tools, and Node.js libraries. These are covered by two different open source licenses: the MIT license or the Creative Commons CC-BY-NC-ND 4.0 (Attribution-NonCommercial-NoDerivatives 4.0 International). See each individual file or its associated README file to learn which applies.

Privacy Policy

Data We Obtain From You

  • While you are browsing our website, we log all HTTPS requests from your browser and all responses by our servers.
  • Each time you use our software, we verify the authenticity of your license key using the device address of your computer, and the IP address of your computer network. We use this data to prevent piracy, and to block unlicensed use of our software.

Data Retention

  • We store site visitor log data for a minimum of 90 days.
  • We retain your customer number, license keys and purchase history for a minimum of three years.

Obtaining a copy of your data

  • You may login to your account using the customer number we assigned to you, and the password chosen by you, to view and print all of the data we retain about you.

Data sharing

  • When you purchase a license to any of our software products, we forward payment information from you to a PCI DSS compliant payment processing gateway.
  • We do not sell or share any information with third parties for the purpose of marketing.
Refund Policy

Refund Policy Our goal is customer satisfaction. If, in your opinion, we haven't met our goal, we will refund the unused, pro-rated portion of your license fee.

When a digression just can't be thrown away

🔎