Re: Re: [Patch 0/5] Create single PDF for all HTML files
- From
Jeff King <peff@peff.net>
- Date
- Oct 7, 2012, 22:52 UTC
- Message-ID
- <20121007225232.GA3490@sigill.intra.peff.net>
- In-Reply-To
- <1770841099.101310.1349597668191.JavaMail.ngmail@webmail23.arcor-online.net>
On Sun, Oct 07, 2012 at 10:14:28AM +0200, Thomas Ackermann wrote:
> There are "patched QT" and "unpatched QT" versions of wkhtmltopdf > (see http://code.google.com/p/wkhtmltopdf/). I am using V0.9.9 for Windows > which is "patched QT".
That's a definite compatibility question for taking your patches into upstream git.
Show 6 quoted lines
> There is one drawback with wkhtmltopdf: At least on my Netbook (Win7 64bit, > Pentium 1.5GHz) it is very slow. It takes more than 3 hrs to create git-doc.pdf. > > If you want to have a quick look on the resulting pdf just clone > https://github.com/tacker66/git-docpdf.git. This repo contains > a current version of user.manual.pdf and git-doc.pdf
It does look better than the output generated by the "man -Tdvi" loop I posted. It retains more styling from the HTML and it has a nice table of contents. But 3 hours? Yeesh. Mine took 11 seconds.
I wonder if a more sane route is to drop HTML entirely, convert the asciidoc to docbook (which we already do for manpages), and then create a docbook document that is a collection of all elements, which can then be converted to pdf, epub, or whatever. I would not be surprised if somebody has solved this problem before (but it is not really my itch, so I did not look very far).
-Peff