I can see that there is functionality for exporting individual cells as SVG or PNG, but I have a use case where I’d like to print an entire notebook as a PDF. It has no code, only images and markdown text.
Specifically, I’ve prepared lecture notes using the template here, but now I’m getting requests for PDF versions of the slides, so that they can be read offline. Printing from a browser is splitting images across pages.
Is there some functionality that I’m not aware of / has anyone found a workaround?
The simplest way would be to save the document as PDF, e.g. via the print dialog. Some observations:
I have a hard time imagining how printing (or a conversion via the parent window) could work under these conditions. My recommendation would be to instead generate a PDF on the fly for download, e.g. via html2pdf.
If you provide a link to your notebook maybe I (or others) will be able to give some pointers.
That’s a good idea about a link, here is one example: https://observablehq.com/@krisrs1128/introduction-to-inference
The biggest problem the students have described is the page breaks. I’ll check out html2pdf and report back on whether this works.
Also, if the notebook has a cell in waiting state, chrome will hold on preview, this is a problem when we have a file input or other cells that are intentionally left in waiting state.
Can you provide a demonstration (or describe the steps to create one in detail)? I would think that Chrome should have no concept of Observable’s pending cell states. Are there perhaps other constant DOM changes, like a loop that yields an element on every animation frame?
https://observablehq.com/@a10k/zinzi in this notebook, but when I comment the second cell with widget… the print works… Thanks for looking into this.
Also, on a related note, the width value in my notebook is 954 but when I print, its 272. Is there something in the settings I should tweak? (I’m on windows 10, chrome Version 84.0.4147.135 (Official Build) (64-bit))
I suspect that it has something to do with how Vega (Vega-Lite) calculates layouts, which may conflict with Chrome’s page splitting and cause the page generation to take unusually long. I wasn’t able to narrow it down though.
The pixel width of a print page depends both on the selected output format (paper size and orientation) and the device pixel resolution reported by the OS. You can check the resolution with:
const n = html`<div style="width:1in">`;
or measure the size of a supposed 1x1 inch square yourself: