From: Thomas Ackermann <th.acker66@arcor.de>
To: git@vger.kernel.org
Cc: philipoakley@iee.org, peff@peff.net, gitster@pobox.com,
th.acker66@arcor.de
Subject: [Patch v2 0/8] Create single PDF for all HTML files
Date: Thu, 11 Oct 2012 19:13:09 +0200 (CEST) [thread overview]
Message-ID: <1412437370.46782.1349975589890.JavaMail.ngmail@webmail22.arcor-online.net> (raw)
Hi,
here is my reworked patch series for creating a single PDF for all
git documentation files.
Thanks to Junio Hamano, Philip Oakley and Jeff King for your comments!
In general, the following problems had to be fixed in doc files in order to create
HTML by using asciidoc and afterwards create a nice looking PDF using wkhtmltopdf:
- Wrong sectioning syntax (e.g. "===" instead of "---")
- Left-over shell scripting commands (in some release notes files)
- Over-long lines which caused very wide right margins in the resulting PDF
- Wrong formatting for email quotes, quoted script code, tables
Also some of the headlines in the documents where changed or even created
initially in order to give a more consistent structure in the resulting 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
---
Thomas
next reply other threads:[~2012-10-11 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 17:13 Thomas Ackermann [this message]
2012-10-11 17:16 ` [Patch v2 1/8] Split over-long synopsis in git-fetch-pack.txt into several lines Thomas Ackermann
2012-10-11 17:18 ` [Patch v2 2/8] Shorten two over-long lines in git-bisect-lk2009.txt by removing some white-space Thomas Ackermann
2012-10-11 19:07 ` Junio C Hamano
2012-10-11 17:19 ` [Patch v2 3/8] Change headline of technical/send-pack-pipeline.txt to not confuse its content with content from git-send-pack.txt Thomas Ackermann
2012-10-11 17:21 ` [Patch v2 4/8] Prerequisites for creating nice html for all files in Documentation/technical Thomas Ackermann
2012-10-11 17:22 ` [Patch v2 5/8] Prerequisites for creating nice html for all files in Documentation/howto Thomas Ackermann
2012-10-11 19:06 ` Junio C Hamano
2012-10-11 17:23 ` [Patch v2 6/8] Prerequisites for creating nice html for all files in Documentation/RelNotes Thomas Ackermann
2012-10-11 17:24 ` [Patch v2 7/8] Create pdf from all html files Thomas Ackermann
2012-10-11 17:26 ` [Patch v2 8/8] Wire everything into Makefile and Documentation/Makefile Thomas Ackermann
2012-10-11 19:30 ` [Patch v2 0/8] Create single PDF for all HTML files Junio C Hamano
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=1412437370.46782.1349975589890.JavaMail.ngmail@webmail22.arcor-online.net \
--to=th.acker66@arcor.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=philipoakley@iee.org \
/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).