Responding to peer reviewers with Pandoc

I’m in the process of responding to the second round of peer reviews of a paper I’ve spent considerable time working on over the past year. Of course, this time around I’ve learned a few new tricks that make the whole process easier to manage…

I spent an entire weekend converting the paper from Word to LaTeX. By hand. But it’s now worth it.
I coerced the other graduate student working on the paper to use Trello, so I can see what he’s working on now, what he’s planning to do next and what he’s already done.
I’ve learned to use git in combination with BitBucket so individual changes are tracked and it’s easy to flip between old and current versions of the paper with a simple git checkout.
I’ve learned how to use the powerful markdown language and document converter, pandoc, which I’m using to format our response to the reviewers.

I’m following the format presented by Matt Might in Responding to peer review. It is an excellent guide to writing a response to peer reviewers, and the method he outlines fits perfectly into a pandoc workflow.

For example, the journal to which we are submitting is run by Elsevier, who certainly has a platform to coordinate communication between editors, authors, and reviewers. A platform that conveniently strips all formatting from the review text. But, after simply copying and pasting the review text into a text file, I add $ marks around the inline LaTeX and convert to PDF. Just reading the reviews is easier when the math and format is clear.

Converting to PDF is as simple as:

pandoc response.txt -o response.pdf

Then, following Matt Might’s workflow, I indent each reviewer response with a > and prepare our replies underneath each item.

We were fortunate in that one reviewer offered a list of polite, meticulously detailed points. However, when converting our responses to PDF, the only difference between regular text and the LaTeX quote environment is increased indentation. When most of a document is normal text with only a few quotes, this is reasonable. But in our case it is very difficult to see, by indentation alone, exactly which text is the reviewer’s comment and which text is our rebuttal.

After far too many hours digging through LaTeX and pandoc discussion forums and a long process of trial and error, I finally came up with the right commands to alter the quote environment. Simply include these lines at the beginning of your markdown file, and pandoc will apply the LaTeX code when converting to pdf.

\let\quoteOld\quote
\let\endquoteOld\endquote
\renewenvironment{quote}{\quoteOld\itshape}{\endquoteOld}

You can save the above lines in a file called preamble.tex that you can then include in the LaTeX header with the pandoc --include-in-header argument.

pandoc --include-in-header preamble.tex response.txt -o response.pdf

Rather than remember to include this code every time you want italicized block quotes, you can download the pandoc default.latex template file, rename it something memorable – like italicquotes.tex – and add the above code somewhere near the top. (Somewhere after the first string of \usepackage commands is probably best.)

Then, copy the italicquotes.tex to the pandoc templates folder, which I found in the following folder:

cp italicquotes.tex /usr/local/share/pandoc-1.11.1/data/templates/

To use this template, simply add --template=italicquotes.tex when you call pandoc:

pandoc -N --template=italicquotes.tex response.txt -o response.pdf

Or, with fancy fonts:

pandoc -N --template=italicquotes.tex \
          --variable mainfont=Georgia \
          --variable sansfont=Arial \
          --variable fontsize=12pt \
          response.txt --latex-engine=xelatex -o response.pdf