All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	Chris Johnsen <chris_johnsen@pobox.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Add warning about known issues to documentation of cvsimport
Date: Tue, 31 Mar 2009 15:40:56 -0400	[thread overview]
Message-ID: <20090331194056.GA23102@coredump.intra.peff.net> (raw)
In-Reply-To: <20090331112812.GA2090@coredump.intra.peff.net>

On Tue, Mar 31, 2009 at 07:28:12AM -0400, Jeff King wrote:

> On Tue, Mar 31, 2009 at 12:36:46AM +0200, Heiko Voigt wrote:
> 
> > > Note the extra blank line between each heading and its list, and the
> > > lack of a blank line between the end of the first list and the heading
> > > of the second. Your source is very readable, so it really is just
> > > asciidoc being silly, but I wonder if there is a way to work around
> > > that.
> > 
> > My xmlto is not working at the moment. I will check that.
> 
> I looked into it a little more; it happens all over the place, so it is
> a problem somewhere in the documentation toolchain. So don't worry about
> it for this particular patch.

I looked into it more and posted to the docbook-apps list.  Here's what
I found out: the problem is fixed in docbook-xsl 1.74.3. However, our
template to prevent extra .sp in manpage-base.xml prevents it.

That fix is in 7ef0435 (spurious .sp in manpages, 2006-12-13), and I get
good output by reverting it and using docbook 1.74.3.

Going back to the original discussion, it looks like it is a workaround
for docbook-xsl 1.69.0:

  http://article.gmane.org/gmane.comp.version-control.git/32957

Assuming that is correct, I think the sane choices are:

  1. drop the workaround, as that version of docbook-xsl is now several
     years old

     or

  2. turn the workaround off by default, but add a knob to turn it on
     (DOCBOOK_XSL_1690?)

Having it on by default and turning it off with a knob seems silly,
since most versions don't need it. Debian stable is shipping 1.73 these
days, which looks fine without 7ef0435. Are there other platforms still
shipping 1.69.0? Is it too old for us to care?

-Peff

  reply	other threads:[~2009-03-31 19:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 19:53 [PATCH] Add warning about known issues to documentation of cvsimport Heiko Voigt
2009-03-23 20:33 ` Ferry Huberts (Pelagic)
2009-03-30 22:17   ` Heiko Voigt
2009-03-31  5:36     ` Ferry Huberts (Pelagic)
2009-03-31 16:22       ` Heiko Voigt
2009-03-31 16:53         ` [PATCH] cvsimport: Add a note about crlf options to the documentation Heiko Voigt
2009-03-31 17:10         ` [PATCH] Add warning about known issues to documentation of cvsimport Ferry Huberts (Pelagic)
2009-03-24  3:14 ` Jeff King
2009-03-30 22:36   ` Heiko Voigt
2009-03-31  0:51     ` Junio C Hamano
2009-03-31 16:45       ` [PATCH] Cleanup warning about known issues in cvsimport documentation Heiko Voigt
2009-03-31 19:49         ` Jeff King
2009-04-01 20:24           ` [PATCH v2] " Heiko Voigt
2009-03-31 11:28     ` [PATCH] Add warning about known issues to documentation of cvsimport Jeff King
2009-03-31 19:40       ` Jeff King [this message]
2009-03-31 23:55         ` Junio C Hamano
2009-04-01  8:50           ` [PATCH] Documentation: use "spurious .sp" XSLT if DOCBOOK_SUPPRESS_SP is set Chris Johnsen
2009-04-01 10:14             ` Jeff King
2009-04-02  5:25               ` Junio C Hamano
2009-04-01 10:34             ` Jeff King
2009-04-01 12:19               ` Chris Johnsen
2009-04-01 13:06                 ` Jeff King

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=20090331194056.GA23102@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=chris_johnsen@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hvoigt@hvoigt.net \
    /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.