From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH 0/4] fix user-manual with Asciidoctor
Date: Sun, 22 Sep 2019 13:57:55 +0200 [thread overview]
Message-ID: <cover.1569152396.git.martin.agren@gmail.com> (raw)
This series makes user-manual.html and user-manual.pdf render well with
Asciidoctor. The first patch is a while-at-it. The other three patches
then align Asciidoctor-rendering with AsciiDoc, first with two
bigger-scope patches, then with a local ASCII-art fix.
I was happily surprised that there weren't more issues like the one
fixed by patch 4/4. After this series, scrolling through AsciiDoc- vs
Asciidoctor-rendered versions of the user manual side by side is a quite
pleasant experience.
Tested with Asciidoctor 1.5.5 and 1.5.7, but also with 2.0.10 using
brian's recent work on getting 2.x to build the docs.
Martin
Martin Ågren (4):
user-manual.txt: add missing section label
user-manual.txt: change header notation
asciidoctor-extensions.rb: handle "book" doctype in linkgit
user-manual.txt: render ASCII art correctly under Asciidoctor
Documentation/asciidoctor-extensions.rb | 7 +-
Documentation/user-manual.txt | 377 +++++++++---------------
2 files changed, 137 insertions(+), 247 deletions(-)
--
2.23.0
next reply other threads:[~2019-09-22 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 11:57 Martin Ågren [this message]
2019-09-22 11:57 ` [PATCH 1/4] user-manual.txt: add missing section label Martin Ågren
2019-09-22 11:57 ` [PATCH 2/4] user-manual.txt: change header notation Martin Ågren
2019-09-22 11:57 ` [PATCH 3/4] asciidoctor-extensions.rb: handle "book" doctype in linkgit Martin Ågren
2019-09-22 11:57 ` [PATCH 4/4] user-manual.txt: render ASCII art correctly under Asciidoctor Martin Ågren
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1569152396.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.