Skip to content
This repository has been archived by the owner on Oct 30, 2020. It is now read-only.

FAQ #2

Open
mcfrank opened this issue Jul 25, 2017 · 2 comments
Open

FAQ #2

mcfrank opened this issue Jul 25, 2017 · 2 comments

Comments

@mcfrank
Copy link
Contributor

mcfrank commented Jul 25, 2017

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?]

@chartgerink
Copy link
Member

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.

@crsh
Copy link
Contributor

crsh commented Jul 26, 2017

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.

chartgerink pushed a commit that referenced this issue Jul 31, 2017
Merge pull request #6 from mcfrank/master
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants