Background

A good while back (around 2 years as of this writing), I needed the feature to turn an R Markdown document into a Word document (that’s easy) and to apply custom styles to specific parts of the Word document (that was trickier). I found some good information in this RStudio article, but it didn’t quite address everything I was looking for.

Specifically, I wanted to find a way to format certain parts of the R Markdown document in a specific style. I asked online and got some help from JJ Allaire (yes, the guy who started RStudio 🤩). Then recently, Dean Attali (yes, the guy who does a lot of cool Shiny stuff ✨) posted a reply asking for an example. I tried to dig out the 2 year old project (it turns out I ended up not needing it for that project and haven’t used it since).

As I was trying to contemplate how to best share the example with Dean, I figured I’ll write a brief blog post, which might benefit others, too. So here it goes.

Word template preparation

• Create a new word document (either through RMarkdown -> Word, or just open Word and create a new empty one).
• Open the word document. Write a bit of text. It doesn’t matter what you write, it’s just meant so you can create and apply new styles to it. For instance you can write Text for mystyle1 .
• Mark the text you wrote, click on the arrow to the left of the Styles box (see the red “circle” in the figure) and choose Create a style . Depending on your version of Word, this might be somewhere else. Create the formatting the way you want.
• Repeat to create as many custom styles as you want, save the word document into the folder of your RMarkdown file.

RMarkdown setup

Start a new Rmarkdown document. Your YAML header should look something like this:

--- title: "An example of formatting text blocks in Word" author: "Andreas Handel" documentclass: article site: bookdown::bookdown_site output: bookdown::word_document2: toc: false reference_docx: wordstyletemplate.docx ---

Note that I’m using bookdown as the output format here, but any others that can produce word output, e.g. the standard R Markdown format, should work equally well. The important part is the last line, which specifies the word document with the custom styles you created in the previous step.

RMarkdown input content

You can now assign text blocks in your R markdown file specific styles. Here I created 3 styles called mystyle1/mystyle2/mystyle3 in the Word doc, and assign them to specific parts of the text. This example markdown text shows how to use the styles.

# A regular section This text is not getting a special format. # A formatted Section . This is formatted according to the _mystyle1_ format. . # Another formatted block of text Some more regular text. . Now text formatted based on _mystyle2_. . More regular text. . This format includes a border and it also works with an equation. $$Y = bX + c$$ . Regular text again. . # With a header Note that the header formatting is overwritten. . 

Word output

The resulting word document looks like this:

Some notes

One thing you see in this example is that your own styles overwrite all others, so headers inside your custom style will just be formatted like your custom style. Some other quirks I noticed is that you seem to need empty lines before and after your custom style block. I seem to remember that formatting of R chunks works ok, but I also seem to recall that sometimes manual intervention is required.

Overall, this approach gives you a good deal of flexibility for applying styling to your Word documents when writing in R Markdown, but there might still be some kinks. As I mentioned in the beginning, I ended up not using it for the project I had intended to use it (a review paper I wrote), so I don’t have a lot of real world experience beyond what I’m describing here.

Further Resources

You can get the Word template and the example R Markdown file I used to illustrate this here and here.

I recently saw that the new R Markdown cookbook has a section describing word styling. I expect that more content will be added to the cookbook, so it’s worth checking regularly.

Andreas Handel, 2023
All content licensed under (CC BY-NC-SA 4.0)
Opinions are my own and do not represent my employer

Made with and Quarto
Inspiration and code snippets taken from these folks
Source at GitHub