
Explore/promote/improve alternative PDF generation tools for Sphinx that do not depend on LaTeX, like or.In my view, if we want to give some love to PDFs on RTD, we should have a roadmap to: We discussed this a lot in #8106 with - at the beginning I was a big defender of LaTeX, but since then I have realized that PDFs are more fragile than I thought. I agree, but at the same time, silently failing if the PDF doesn't build ( #7884) or not having PDFs for projects with v2 configuration (~this issue) is not helping the feature. I see this as a "feature of Read the Docs" (all the projects has PDF), not as a "feature of this particular documentation" This is not always considered by the author of the documentation and in those cases, building it by default is 👍🏼 I'm on the fence here because I think the main benefit of the PDF is for readers without the internet. (*active = with X builds in the past Y months? with NNNN visits in the past Y months?) What percentage of active* projects have zero downloads on their PDFs and EPUBs?.What percentage of active* projects use a config file on their default version?.Some questions that might help making this decision, although I don't think we should hard block the decision on those: Given that the config file (2) in itself is opt-in, I wonder if we should make PDF and EPUB off by default on the UI. On a related note, PDF errors are now passing silently #7884. However, building PDFs is quite costly, error-prone, and unclear if being used by a majority of our users. readthedocs.yaml file, where the default for formats is If I understand correctly, this can be overridden by: At the moment, every newly created project on Read the Docs has PDF and EPUB builds enabled in the UI:
