Compiling pdf version

[dicook]

• Pull/push to the pdf branch of the GitHub repo
• Use render to pdf, will build book into pdf directory
• To get started, use ::: {.content-visible when-format="html"} to prevent the interactive plots being generated
• If you run into an error, use your tex installation to typeset the .tex file, because it is easier to track down the problem
• Issues to be aware of
  • some figure definitions for html generate an error for pdf, typically the multicolumn, so the fix is to make it one figure using patchwork (Error likely to be LaTeX Error: Not in outer par mode.)
  • figure cross-references need to be handled with an R snippet, conditionally creating the text string for pdf or html
  • code that is folded in the html will appear in the pdf, so we might want to make more functions to make the code blocks shorter
  • check code doesn't extend outside textwidth
  • fig-alt needs to be in the separate figure options in multicolumn figures
  • for animated figures that don't work well as static, put a reference in the caption to the Figure in the html site. How to do this so it works well for the printed book is not clear yet!

[dicook]

Remember to add the alt-text to figures as you go

[dicook]

I wonder if the published will want pdf images of everything? And whether they need a different colour system, eg cmyk instead of rgb.

[dicook]

• The table of contents is really off
• The supporting files (.tex) get saved as the full book title, Interactively-exploring-high-dimensional-data-and-models-in-R, in the top level directory, but figures and final pdf are saved in the output-dir. This creates a problem when trying to typeset the pdf from these files because figures are all in the wrong directories. The figures from code chunks are generated as pdf.

[dicook]

Adding {r echo=knitr::is_html_output()} to the chunk allows code to be shown and folded in the html output and hidden in the pdf.

[dicook]

Code chunks in the pdf look somewhat orphaned. It might help to put comments at the top of the chunk that is displayed. (See LDA chapter)

[dicook]

There are duplicate references, which must come from the automated package citations, along with the regular in text citations.