From: Jeff King <peff@peff.net>
To: Thomas Ackermann <th.acker66@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: Re: [Patch 0/5] Create single PDF for all HTML files
Date: Sun, 7 Oct 2012 18:52:32 -0400 [thread overview]
Message-ID: <20121007225232.GA3490@sigill.intra.peff.net> (raw)
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.
> 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
next prev parent reply other threads:[~2012-10-07 22:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 15:51 [Patch 0/5] Create single PDF for all HTML files Thomas Ackermann
2012-10-06 15:53 ` [Patch 1/5] Fix some asciidoc layout problems Thomas Ackermann
2012-10-06 18:39 ` Junio C Hamano
2012-10-06 19:10 ` Jeff King
2012-10-07 8:01 ` Aw: " Thomas Ackermann
2012-10-06 15:55 ` [Patch 2/5] Create html documents for all files in Documentation/technical Thomas Ackermann
2012-10-06 18:45 ` Philip Oakley
2012-10-06 15:55 ` [Patch 3/5] Create html documents for all files in Documentation/RelNotes Thomas Ackermann
2012-10-06 18:48 ` Philip Oakley
2012-10-06 19:21 ` Jeff King
2012-10-07 20:53 ` Junio C Hamano
2012-10-15 11:48 ` Michael J Gruber
2012-10-15 20:49 ` Junio C Hamano
2012-10-06 15:57 ` [Patch 4/5] Create html documents for all files in Documentation/howto Thomas Ackermann
2012-10-06 15:58 ` [Patch 5/5] Create pdf from all html files Thomas Ackermann
2012-10-06 19:11 ` Jeff King
2012-10-06 19:32 ` [Patch 0/5] Create single PDF for all HTML files Jeff King
2012-10-07 20:54 ` Junio C Hamano
2012-10-07 8:14 ` Aw: " Thomas Ackermann
2012-10-07 22:52 ` Jeff King [this message]
2012-10-15 11:55 ` Michael J Gruber
2012-10-15 17:42 ` Jeff King
2012-10-08 22:53 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121007225232.GA3490@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=th.acker66@arcor.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).