From: Todd Zullinger <tmz@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Andreas Schwab <schwab@linux-m68k.org>,
git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git 1.6.5.4
Date: Thu, 3 Dec 2009 17:00:20 -0500 [thread overview]
Message-ID: <20091203220020.GS23717@inocybe.localdomain> (raw)
In-Reply-To: <7vfx7r4we7.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 2178 bytes --]
Junio C Hamano wrote:
> This is what I plan to use.
>
> -- >8 ---
> From: Junio C Hamano <gitster@pobox.com>
> Date: Thu, 3 Dec 2009 11:12:32 -0800
> Subject: [PATCH] Documentation: xmlto 0.0.18 does not know --stringparam
>
> Newer DocBook stylesheets want man.base.url.for.relative.links
> parameter set when formatting manpages with external references
> to turn them into full URLs, and leave a helpful "you should
> set this parameter" message in the output. Earlier we added
> the MAN_BASE_URL make variable to specify the value for it.
>
> When MAN_BASE_URL is not given, it ought to be safe to set the
> parameter to empty; it would result in an empty leading path for
> older stylesheets that ignore the parameter, and newer ones
> would produce the same "relative URL" without the message.
>
> Unfortunately, older xmlto (at least version 0.0.18 released in
> early 2004 that comes with RHEL/CentOS 5) does not understand
> the --stringparam command line option, so we cannot add the
> parameter definition unconditionally to the command line. Work
> it around by passing the parameter only when set.
Is it worth sidestepping the xmlto part entirely? If we set this
directly in a .xsl file, it will work on older systems without any
effort. Then we can default MAN_BASE_URL to something and let distro
packagers override it.
I tested with this in Documentation/manpage-base.xsl on a CentOS 5 box
and it builds fine, leaving no cruft in the man pages regarding the
man.base.url...
<!-- set a base URL for relative links -->
<xsl:param name="man.base.url.for.relative.links"
>/path/to/git/docs</xsl:param>
Of course, the relative links looked just like they did in older
docbook releases:
1. Everyday Git
everyday.html
Is it worth the effort to have @@MAN_BASE_URL@@ in
Documentation/manpage-base.xsl or similar and replace it at build
time?
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Just because everything is different doesn't mean anything has
changed.
-- Irene Peter
[-- Attachment #2: Type: application/pgp-signature, Size: 542 bytes --]
next prev parent reply other threads:[~2009-12-03 22:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 9:21 [ANNOUNCE] Git 1.6.5.4 Junio C Hamano
2009-12-03 9:25 ` Jeff King
2009-12-03 12:03 ` Andreas Schwab
2009-12-03 12:15 ` Michael J Gruber
2009-12-03 13:50 ` Andreas Schwab
2009-12-03 14:51 ` Michael J Gruber
2009-12-03 15:03 ` Todd Zullinger
2009-12-03 17:43 ` Junio C Hamano
2009-12-03 20:27 ` Todd Zullinger
2009-12-03 20:48 ` Junio C Hamano
2009-12-03 22:00 ` Todd Zullinger [this message]
2009-12-03 22:30 ` Junio C Hamano
2009-12-04 3:49 ` Eugene Sajine
2009-12-04 6:18 ` Junio C Hamano
2009-12-04 6:39 ` Matthieu Moy
2009-12-04 10:12 ` Andreas Schwab
2009-12-04 17:10 ` Junio C Hamano
2009-12-04 19:33 ` Todd Zullinger
2009-12-05 7:28 ` Junio C Hamano
2009-12-07 0:30 ` Junio C Hamano
2009-12-07 15:18 ` Todd Zullinger
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=20091203220020.GS23717@inocybe.localdomain \
--to=tmz@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=schwab@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox