In the spirit of getting my procrastinating done during the holidays (that’s how procrastinating works, right?), I thought I’d share how I choose to write complex papers. For my purposes, “complex” means any paper that involves some combination of:
- citations linked to some bibliography manager;
- internal links (a.k.a. “cross references”).
For simpler papers, I really do like Pages. It makes formatting relatively easy, it has (basic) EndNote and MathType support, and it looks lovely on high resolution displays. More recently, I’ve become smitten with Apple’s new Handoff feature that works with iOS 8 and OSX Yosemite devices. Being able to work on a paper at my desk, then pick up where I left off on my iPad as I move to the couch, then switch to my iPhone so I can stretch my legs, is pretty neat. Maybe this will get old someday, but for now it’s the bee’s knees.
Then there are the problems. In addition to the inability of Pages to satisfy my need for numbered equations, Apple is developing a bit of a reputation for poor backward-compatibility. I am terrified by the prospect of trying to open my dissertation in a few years and getting an alert like this (source: Google+):
This is totally unacceptable, and I hope Apple understands what a massive detterent this is.
The opposite end of the usability vs. flexibility spectrum, there’s LaTeX. LaTeX combines the longevity of plain text with a robust bibliography management system, not to mention the fact that LaTeX was conceived for the purpose of printing mathematical formulas. But, as the above links may suggest, LaTeX tools won’t be winning any awards for UI design.
Enter multimarkdown. Developed by Fletcher Penny, MMD allows me to use one of the hundreds of markdown text editors for iOS using a syntax that can be exported as LaTeX. This export process does take some time to set up (see here for details), but once it’s read I simply have to prepend this metadata to the beginning of a file to make it export-ready:
Title: Title of my document Author: Teddy Svoronos latex input: /path/to/header/mmd-teddy-header latex footer: /path/to/footer/mmd-teddy-footer Base header level: 2 Bibtex: /path/to/bibtex/file/bibfull Biblio Style:plain
I may get into the details of this setup in a later post; let me know if there’s any interest.
My editor of choice is Byword (which was recently updated to support Handoff), though I use Fletcher’s own MultiMarkdown Composer when I need to get in the weeds of internal links, table creation, and using the app’s native table of contents viewer.
The only potential rub in this setup is if my advisors want to use Word track changes to provide comments. In this case, I’ll have to export my file as rich text and do some manual futzing to make it presentable. Not great, but those occasional costs are outweighed by the benefits outlined above.
Boy, I’d better get writing.
- For background on markdown, see Gruber’s original specification. For an introduction to the syntax for non-coders and why you should use it, I recommend David Spark’s excellent iBook. ↩