git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
	"Martin Ågren" <martin.agren@gmail.com>
Subject: Re: [PATCH] doc: remove custom callouts format
Date: Tue, 18 Apr 2023 00:41:42 -0400	[thread overview]
Message-ID: <20230418044142.GA130759@coredump.intra.peff.net> (raw)
In-Reply-To: <20230418040034.GC60552@coredump.intra.peff.net>

On Tue, Apr 18, 2023 at 12:00:34AM -0400, Jeff King wrote:

> It's probably still worth moving forward with your patch, as I think it
> takes us in the direction we want long-term (and which builds with
> asciidoctor are already using). But we may want to pair it with a patch
> to work around the issue with git-checkout.1 using asciidoc to avoid
> regressing that section. It may require re-wording or re-organizing to
> work around the bug.

Just to clarify my comment on asciidoctor: since our Makefile will put
its output through docbook, too, it actually is using the xsl you're
removing here (though I'm unclear on why its output looks good in
general even before your patch).

But the problem with git-checkout.1 in particular is that the XML
generated by asciidoc does not close the <calloutlist> at the right spot
(it sticks the continuation onto the calloutlist), whereas asciidoctor
does it right (it closes the calloutlist after item 3).

I had tried putting an open block around the whole example and callout
list before, which asciidoc doesn't like. But doing it just around the
callout list, like so:

diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt
index 6bb32ab460..bd83a6e5d2 100644
--- a/Documentation/git-checkout.txt
+++ b/Documentation/git-checkout.txt
@@ -530,9 +530,11 @@ $ rm -f hello.c
 $ git checkout hello.c            <3>
 ------------
 +
+--
 <1> switch branch
 <2> take a file out of another commit
 <3> restore `hello.c` from the index
+--
 +
 If you want to check out _all_ C source files out of the index,
 you can say

seems to improve things. The generated XML looks sensible, and the
output looks like asciidoctor's, though unfortunately both omit the
blank line between the end of the callout list and the next paragraph.
That might be good enough to live with.

-Peff

  reply	other threads:[~2023-04-18  4:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  1:18 [PATCH] doc: remove custom callouts format Felipe Contreras
2023-04-18  4:00 ` Jeff King
2023-04-18  4:41   ` Jeff King [this message]
2023-04-18  7:25     ` Felipe Contreras
2023-04-18  5:30   ` Felipe Contreras
2023-04-18  6:17     ` Jeff King
2023-04-18  7:15       ` Felipe Contreras
2023-04-18  9:03         ` Jeff King
2023-04-18  9:50           ` Felipe Contreras

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=20230418044142.GA130759@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin.agren@gmail.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).