I don't have a lot of bandwidth to experiment with this right now, but I would be supportive of us publishing a PDF along with the HTML. It's probably just a matter of adding a few lines to our publish.yml file.

Shouldn't it be able to be built into the /book directory and then linked in the html template instead of the browser print dialogue if that value is set in the book.toml? At least this would be what I would expect from a rendered pdf.

Right, I think I agree: we can remove the 🖨️ button from the pages and instead link to the PDF.

Unfortunately that is less mobile compatible: https://caniuse.com/?search=pdf as fewer browsers seems to have a built-in pdf viewer. :/

If the print.html page is no longer generated, then I suppose people lose a way of easily getting a concatenated version of the HTML for the course. A PDF would be a concatenated version, but it would of course look different.

I don't think much is lost if we don't link to print.html and replace it with a well-formatted PDF.

The alternative could be to introduce another link on the top menu right-hand side for opening it as a pdf-book, or an Export dropdown where different rendered books are mentioned. pdf and epub for example.

I would prefer to add a new page in the course which links to the PDF (and perhaps other formats if we generate those). Horizontal space is a costly resource, so this would allow us to remove the 🖨️ icon on every page.

Look into publishing PDFs with mdbook-typst #1543

Description

mgeisleropenedon Dec 1, 2023

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

mgeisler
openedon Dec 1, 2023