Is there an option to control output page orientation (using knitr->pander->pandoc->docx)

Question

I am playing with Tal\'s intro to producing word tables with as little overhead as possible in real world situations. (Please see for reproducible examples there - Thanks, Tal!)

Answer 1

I am pretty sure the docx writer has no section breaks implemented, also as far as I understand --reference-docx allows for customizing styles and not the page layout (but I might also be wrong here), this is from pandocs guide on --reference-docx:

--reference-docx=FILE

Use the specified file as a style reference in producing a docx file. For best results, the reference docx should be a modified version of a docx file produced using pandoc. The contents of the reference docx are ignored, but its stylesheets are used in the new docx. If no reference docx is specified on the command line, pandoc will look for a file reference.docx in the user data directory (see --data-dir). If this is not found either, sensible defaults will be used. The following styles are used by pandoc: [paragraph] Normal, Title, Authors, Date, Heading 1, Heading 2, Heading 3, Heading 4, Heading 5, Block Quote, Definition Term, Definition, Body Text, Table Caption, Image Caption; [character] Default Paragraph Font, Body Text Char, Verbatim Char, Footnote Ref, Link.

Which are styles that are saved in the /word/styles.xml component of the docx document. The page layout on the other hand is saved in the /word/document.xml component in the tag, but pandoc's docx writer ignores this part as far as I can tell.

The docx writer builds by default a continuous document, with elements such as headers, paragraphs, simple tables and so on ... much like a html output.

---

Option #1 (doesn't solve the page orientation problem):

The only page layout option that you can define through styles is the pageBreakBefore which will add a page break before a certain style

Option #2 (seems elegant but hasn't been tested):

Recently the custom writer has been added that allows for a custom lua script, where you should be able to define how certain Pandoc blocks will be written into the output file ... meaning you could potentially define section breaks and page layout for a specific block inserting the sectPr tag into the document. I haven't tried this out but it would be worth investigating. On pandoc github you can check out a sample lua script file for custom html output.

However, this means, you have to have lua installed, learn the language, and it is up to you if you think its worth the time investment.

Optin #3 (a couple of clicks in Word might just do):

As you will probably spend quite some time setting up how to insert sections and what would be the right size, margins, and figuring how to fit the table to such a layout ... I recommend that you use pandoc to put write your document.docx, that you open in Word, and do the layout by hand:

• select the table you want on the landscape page
• go to Layout > Margins
  > select Apply to: Selected text
  > choose Page Setup > select Landscape

Now a new section with a landscape orientation should surround your table.

What you would anyway also probably want to do is styling the table and table caption a little (font-size,...), to achieve the best result (all text styling can be already applied with pandoc where --reference-docx comes handy).

Option #4 (in situation when you can just use pdf instead of docx):

As far as I could figure out is that with pandoc does a good job with tables in md -> docx (alignment, style, ... ), in tex -> docx it had some trouble sometimes. However if your option allows for a pdf output latex will be your greatest friend. For example your problem is solved as easily as just using

\usepackage{pdflscape}

and adding this around your table

\begin{landscape}
...
\end{landscape}

This are the options that I could think of so far.

I would always recommend using the pdf format for reports, as you can style it to your liking with latex and the layout will stay the way you want it to be.

However, I also know that for various reasons word documents are still the main way of reviewing manuscripts in many fields ... so i would most likely just go with my suggested option 3, mostly cause it is a lazy and quick solution and because I usually don't have many documents with tons of giant tables with awkward placement and styling.

Good luck ;-)