From: Thomas Ackermann <th.acker66@arcor.de>
To: peff@peff.net, th.acker66@arcor.de
Cc: git@vger.kernel.org
Subject: Aw: Re: [Patch 0/5] Create single PDF for all HTML files
Date: Sun, 7 Oct 2012 10:14:28 +0200 (CEST) [thread overview]
Message-ID: <1770841099.101310.1349597668191.JavaMail.ngmail@webmail23.arcor-online.net> (raw)
In-Reply-To: <20121006193205.GD3644@sigill.intra.peff.net>
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".
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
----- Original Nachricht ----
Von: Jeff King <peff@peff.net>
An: Thomas Ackermann <th.acker66@arcor.de>
Datum: 06.10.2012 21:32
Betreff: Re: [Patch 0/5] Create single PDF for all HTML files
> On Sat, Oct 06, 2012 at 05:51:15PM +0200, Thomas Ackermann wrote:
>
> > I wanted to have a single PDF file which contains the complete Git
> documentation
> > (except user-manual) for easier reading on my tablet. The simplest way to
> do
> > this was by using wkhtmltopdf which can combine a set of HTML files into a
> sinlge
> > PDF file and also apply some reformatting. To this end HTML files for all
> the missing
> > files in Documentation/technical and Documentation/howto and also for all
> the
> > release notes in Documentation/RelNotes were created.
>
> It seems like a reasonable goal. I do not have a strong opinion on the
> approach or how the final output looks, but I wasn't able to actually
> get output at all after applying your patches. Running "make fullpdf"
> (after installing dblatex) got me:
>
> The switch --book, is not support using unpatched qt, and will be
> ignored.The switch --footer-html, is not support using unpatched qt,
> and will be ignored.The switch --disable-external-links, is not
> support using unpatched qt, and will be ignored.
>
> after which wkhtmltopdf began pegging my CPU. I let it run for 10
> minutes before giving up.
>
> Another way of doing this would be to format the individual troff
> manpages into dvi or postscript, convert that into pdf, and then
> concatenate that. Something like:
>
> for i in *.[157]; do
> man -Tdvi -l "$i" >"$i.dvi"
> dvipdfm "$i"
> done
> pdftk *.[157].pdf cat output full.pdf
>
> works for me, though obviously that does not handle some of the non-man
> items you included. No idea on how the output compares to yours, but
> it's something you may want to look at.
>
> -Peff
>
---
Thomas
next prev parent reply other threads:[~2012-10-07 8:16 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 ` Thomas Ackermann [this message]
2012-10-07 22:52 ` Jeff King
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=1770841099.101310.1349597668191.JavaMail.ngmail@webmail23.arcor-online.net \
--to=th.acker66@arcor.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).