rmarkdown-workshop
rmarkdown-workshop copied to clipboard
FAQ
was thinking that we should address:
Q: what if the journal wants it in word? A: pandoc it to word! Q: what if you are collaborating with a non-R person? A: let them edit the markdown, paste the text into google docs? [CH what do you here?]
For Q2 I usually send collaborators the word file and let them track changes as they're used to. Will post more Qs here when I think of them.
Q1: The rmarkdown package can create word documents and papaja also has rudimentary support for word. So I don't think it's necessary to teach pandoc as a means to convert between formats?
Q2: I have send out word files in the past, too. It's a somewhat painful to move the changes back over to the Rmd-file but I'm currently not aware of a better way.
Another common question is how to track changes. The easiest answer is to refer to a version control system, e.g. git and GitHub and teach participants how to comment inline on GitHub. Another possibility that is more appropriate for exchange with journals and reviewers is to use latexdiff to highlight changes in a PDF.