The logo feature parses logo_path as Markdown and emits it as escaped LaTeX. This breaks the report/proposal build when the path has special characters (e.g., underscores). I need to find a way around this:
- Fence
logo_path using raw_attribute with backtick_code_blocks or similar (my experiments with this feature to date have failed, but maybe I'm missing something).
- Patch the logo in some other way. For example, take the logo at the command line, run Pandoc to generate LaTeX, patch in the logo path using
sed or similar, then generate the pdf with pdflatex. A disadvantage here is that builds start taking configuration from two places (command line flags and YAML metadata). An advantage is that we could move consulting-unrelated metadata (document_hash: placeholder along with the logo) out of the YAML, keeping the Markdown cleanly "consulty."
The logo feature parses
logo_pathas Markdown and emits it as escaped LaTeX. This breaks the report/proposal build when the path has special characters (e.g., underscores). I need to find a way around this:logo_pathusingraw_attributewithbacktick_code_blocksor similar (my experiments with this feature to date have failed, but maybe I'm missing something).sedor similar, then generate the pdf withpdflatex. A disadvantage here is that builds start taking configuration from two places (command line flags and YAML metadata). An advantage is that we could move consulting-unrelated metadata (document_hash:placeholder along with the logo) out of the YAML, keeping the Markdown cleanly "consulty."