Farewell, footnotes.

I have chosen a Markdown processor that does not support footnotes. In the NodeJS world, there aren't a lot of Markdown engines that support the extended Markdown footnote syntax (MultiMarkdown, Markdown Extras, etc.), and the Github Flavored Markdown syntax. Specifically, GFM-style fenced code blocks with language classes.

As a developer who uses GitHub extensively, I had little choice. As typography nerd, I was disappointed.

Marked, the Javascript Markdown compiler, not the application, is the default engine used in DocPad. It's in active development. GFM, but no footnotes yet.

And yes, while I could use another non-Javascript processor - I'm a fan of Python's implementation, which supports a rich set of extensions - I'm keeping this JS native as much as possible.

Perhaps I'm just being pedantic. Someone agrees:

But the academic practice of relegating notes to the foot of the page or the end of the book is a mirror of Victorian social and domestic practice, in which the kitchen was kept out of sight and the servants were kept below stairs. If the notes are permitted to move around in the margins - as they were in Renaissance books - they can be present where needed and at the same time enrich the life of the page.

The Elements of Typographic Style, by Robert Bringhurst

While I'm not sure I'd compare footnotes to class discrimination, and to be fair, Bringhurst does go on to discuss their proper use. But if I have to be honest, for my purposes any related content is better served with <aside> or links, either in the sidebar, or inline.

This may seem like is a trivial concern, but to a fan of type, it feels like a big deal. But, as typographic traditions have evolved, so shall I.

Riiight... I'm forking marked as we speak.

March 23 2013.