git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Cc: Drew Northup <drew.northup@maine.edu>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation/Notes: Remove 'footnote:' warning
Date: Mon, 18 Jul 2011 02:13:08 -0500	[thread overview]
Message-ID: <20110718071308.GA4745@elie.gateway.2wire.net> (raw)
In-Reply-To: <CAK9CXBV=OMRVzEjUmb6JP8nM9bQ4DqM0D7xCywxs0TUD5+scrw@mail.gmail.com>

Pavan Kumar Sunkara wrote:

> Currently the documentation at
> http://www.kernel.org/pub/software/scm/git/docs/git-notes.html is
> showing the footnote wrongly. This workaround will solve that.

(For reference, the linked-to page was generated with asciidoc 8.4.5
and renders the footnote as

	<br />[Permitted pathnames have the
[...]
	rest of the object ID.]<br />.

inline instead of a nicely labelled link like "[1]" that one might
expect.)

Weird.  That's not the Docbook XSL bug I pointed to --- the HTML
documentation is generated by asciidoc directly, without any help
from Docbook XSL.  And I can't reproduce it locally, either.
*digs around in asciidoc changelog*  Ah, Asciidoc 8.5.1 introduced
styling of footnotes:

     * Styled HTML footnotes.
     * Added links to HTML footnote refs.

Until the kernel.org toolchain gains that feature, wouldn't a simpler
workaround be to put the footnote after the period, so it renders
there as a simple line in brackets?

Barring that, it should be possible to put this information in the
discussion section without disrupting the flow of the text so much,
for example by putting it in parentheses or making it the last
paragraph of the discussion section.  A patch with such a change and
mentioning in the commit message the two bugs you're working around
would seem sane to me.

Thanks,
Jonathan

  reply	other threads:[~2011-07-18  7:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 22:30 [PATCH] Documentation/Notes: Remove 'footnote:' warning Pavan Kumar Sunkara
2011-07-17 13:11 ` Drew Northup
     [not found]   ` <CAK9CXBUAX42gCuRLWUpuvK6SSZXv1Cn4YNoFAfjRhouzd+thcw@mail.gmail.com>
2011-07-17 13:46     ` Pavan Kumar Sunkara
2011-07-17 21:58   ` Jonathan Nieder
2011-07-18  5:42     ` Pavan Kumar Sunkara
2011-07-18  5:51       ` Jonathan Nieder
2011-07-18  6:07         ` Pavan Kumar Sunkara
2011-07-18  7:13           ` Jonathan Nieder [this message]
2011-07-18  9:01             ` Pavan Kumar Sunkara
2011-07-19 20:43               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110718071308.GA4745@elie.gateway.2wire.net \
    --to=jrnieder@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=git@vger.kernel.org \
    --cc=pavan.sss1991@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).