Open michaeldorman opened 3 months ago
I've spent some time today chasing some ideas, but it seems that no obvious/straightforward solution exist (e.g., see https://github.com/quarto-dev/quarto-cli/discussions/3260). My current suggestion would be just to comment out the pdf chunks atm, and only uncomment them before building the PDF version of the book.
Or... maybe we could try somethings like this:
::: {.content-visible when-format="html"}
code
:::
Sadly -- no.
I've spent some time today chasing some ideas, but it seems that no obvious/straightforward solution exist (e.g., see quarto-dev/quarto-cli#3260). My current suggestion would be just to comment out the pdf chunks atm, and only uncomment them before building the PDF version of the book.
Thanks @Nowosad , commenting out until we need the PDF is a good idea, will use that
I think in the current setup
book_options_pdf.py
always overridesbook_options.py
, even in the HTML version. That is.book_options_pdf.py
is always being run even, and since it comes later in the code it overridesbook_options.py
.Specifically
pd.options.display.max_colwidth=13
in the PDF settings makes columns too narrow in the HTML. Here is an example where this matters (we want to show thePOLYGON EMPTY
text):Is there a way to switch between
book_options_pdf.py
andbook_options.py
? @Nowosad