iWork gets LaTeX equation editing

In April of last year, Apple released an update for Pages that supported rendering equations entered using LaTeX or MathML. I was really impressed that Apple chose to support not one but two standards for entering equations1, but was pretty bummed to learn that equation rendering was specific to Pages.

Today that changed. All three iWork apps now support equation rendering (even Numbers!). This is a big, big deal for me; it’ll be a huge timesaver2 and enable for much richer math-based animations in my presentations.

If you combine this with handwriting apps like MyScript Nebo, you can hand draw equations, copy them as LaTeX code, and paste them right into your iWork document.

On a different note, iWork on iOS is really growing up. Keynote now supports the editing and creation of paragraph styles and master slide layouts. I still work with Keynote most efficiently on MacOS, especially when editing animations in bulk, but the iOS apps are becoming more and more self-sufficient with each update.

  1. Especially in comparison to Microsoft’s equation syntax, which is just close enough to LaTeX to be infuriating to use.
  2. I used to create equations in a Pages document, then pasted them into Keynote as images. It worked, but it was kludgy as heck.

Mac Power Users #319

This week I was on Mac Power Users to talk about my workflows related to teaching and academic research. I’m a huge fan of MPU so it was quite an honor to be on.

Have a listen – feedback always welcome.

Mac Power Users #319: Teaching Workflows with Teddy Svoronos

How I will write my dissertation

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;
  • equations;
  • 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[1] 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.

  1. 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.  ↩