git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] INSTALL: note on using Asciidoctor to build doc
Date: Fri, 19 Mar 2021 00:07:27 +0000	[thread overview]
Message-ID: <YFPrP/hqTFZQB8jy@camp.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqwnu4rzw0.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]

On 2021-03-18 at 20:05:35, Junio C Hamano wrote:
> Mention of asciidoctor may be a good idea, but this gives an
> impression that everything between this new paragraph and the line
> that says
> 
> 	"All formats require at least asciidoc 8.4.1."
> 
> are irrelevant if you choose to use asciidoctor.  Is that really the
> case (e.g. is docbook-xsl unneeded with asciidoctor)?

No, we use Asciidoctor in the same way as AsciiDoc, which is to generate
the DocBook (v5 with Asciidoctor, v4 with AsciiDoc) and then convert.
While Asciidoctor can generate PDFs with an extension and manpages and
HTML with a built-in converter, it doesn't natively know how to generate
other formats, such as Texinfo, so we need to generate DocBook anyway
and it makes sense to make the two processes as similar as possible.

> If not, then wouldn't it make the result easier to follow if you did
> something along this line instead?
> 
> 
>  INSTALL | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git c/INSTALL w/INSTALL
> index 9ba33e6a14..d8e75a7c59 100644
> --- c/INSTALL
> +++ w/INSTALL
> @@ -198,7 +198,9 @@ Issues of note:
>     Building and installing the pdf file additionally requires
>     dblatex.  Version >= 0.2.7 is known to work.
> 
> -   All formats require at least asciidoc 8.4.1.
> +   All formats require at least asciidoc 8.4.1.  Alternatively, you
> +   can use AsciiDoctor by passing USE_ASCIIDOCTOR=YesPlease to make.
> +   You need at least asciidoctor verison X.Y.Z.

This seems fine as an approach.  I think 1.0 is probably sufficient, but
I always use Debian sid, so the oldest version I'm confident that works
is 1.5, since that's the oldest version I've used recently.

Debian 9, which came out in 2017, and Ubuntu 16.04, which came out in
2016, both ship with 1.5.4, so it's probably safe to just say 1.5.
-- 
brian m. carlson (he/him or they/them)
Houston, Texas, US

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2021-03-19  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 11:23 [PATCH] INSTALL: note on using Asciidoctor to build doc Bagas Sanjaya
2021-03-18 20:05 ` Junio C Hamano
2021-03-19  0:07   ` brian m. carlson [this message]

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=YFPrP/hqTFZQB8jy@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 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 NNTP newsgroup(s).