Hi Michael, thank you very much for your reply, I am already using wkhtmltopdf to build PDF from HTMLs. Also, I already tried the singlehtml and indeed works but the problem is that it increases so much the build time that it makes kind of impossible to work locally to test. Using singlehtml to build the PDFs means building 1 time for the documentation and n-times for each desired PDF, which can lead to building time of hours. That is why I would like to avoid rebuilding the documentation, simply converting the current build to PDF reduces so much the time, but as mentioned, getting the *full* (infinite depth) tree from the built html seems tricky.
On Saturday, February 2, 2019 at 1:02:54 PM UTC+1, Michael Gielda wrote: > > Have you looked at WeasyPrint on a single html build? Don't know how well > it works for your use case but that's what I would try first. It's in > Python (yay), and a direct HTML to PDF converter, implementing the CSS Page > spec (for stuff like headers and footers). > > Best regards > Michael > -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
