Open RussellAndrewEdson opened 1 month ago
Yeah, unfortunately I think it's probably worth starting from scratch. The more we can use the default templates and just change some styles etc, I think the smoother it will be. This goes for the translation to quarto as well. Because it all goes through Pandoc, the more we can use the Pandoc approach, I think the better it will be.
Fixed for the short report template in d5c77415f027becfdf9f71d36a4a22fa7050c922 (I've also gone ahead and included the basic AAGI Palette colours as in #16 and made some additions to the Rmd YAML to control things). Effectively it was a rewrite of the AAGI_markdown.tex
file using the latest pandoc template as the starting point:
\begin{note} ... \end{note}
. This is useful for eye-catching notes that you want the reader to notice/respond to. I use it when asking questions for specific follow-up from clients, etc.AAGI_markdown.tex
template and gotten rid of the AAGI.sty
file entirely. This happened naturally: I'd started out trying to keep the two segregated (e.g., "maybe the AAGI palette colours should be in the style file, that makes sense!"), but I quickly found myself coming up against ludicrous roundabouts and unnecessarily duplicated code to justify the separate file (e.g., "Well since we can't be sure the AAGI palette exists if AAGI.sty
wasn't loaded, then maybe the template file should check if AAGI.sty
was loaded and if not, define a whole bunch of 'placeholder' colours for aagiteal, aagiblue, etc?"). I actually wonder if there's a point to having the AAGI.sty
file at all for the other templates, but I'll see if there's a reasonable segregation that can be made as I continue with the other templates.I'm sure the referencing is probably broken for the other Rmarkdown templates too, so I'll keep working my way through the fixes.
In the Rmarkdown template, references/citations don't work. What a mess...
Given this and probably related issues #12 and #13, it almost feels like a rewrite-from-scratch might be in order for
AAGI.sty
andAAGI_markdown.tex
(e.g., part of #13 looks to be caused by duplication between the .tex file and the .sty file, as well as things not being in the 'proper' order for includes, etc). @rogerssam, thoughts?