git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Todd Zullinger <tmz@pobox.com>
Cc: Alejandro Riveira <ariveira@gmail.com>,
	git@vger.kernel.org, Jay Soffian <jaysoffian@gmail.com>,
	Tom Holaday <tlholaday@gmail.com>
Subject: Re: git doc build failure on OS X 10.5.6 (Leopard) during xmlto  phase
Date: Fri, 13 Mar 2009 11:29:01 +0100	[thread overview]
Message-ID: <49BA356D.8050007@drmicha.warpmail.net> (raw)
In-Reply-To: <20090312170931.GB19175@inocybe.teonanacatl.org>

Todd Zullinger venit, vidit, dixit 12.03.2009 18:09:
> Michael J Gruber wrote:
>> Following up on this:
>> On Fedora 10, I have asciidoc 8.2.5 and docbook 1.7.4 xsl's. For
>> proper man and html doc, I have to set DOCBOOK_XSL_172=Yes but leave
>> ASCIIDOC8 unset! I always forget, though (just like the packagers).
> 
> Check the fedora git packages in rawhide, we don't set ASCIIDOC8. :)

I was unclear, but I meant forgetting to set DOCB... But:

> I experimented with that and found it did not improve things.  We are
> only setting DOCBOOK_XSL_172.  Without that, we get the '.ft C'
> droppings.  With it, we get non-ascii characters in various places
> (where bold should be used to make the (1) notations stand out, for
> example).  This was filed as:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=485161

I hadn't noticed that yet (neither the effect nor the report). So, you
kept it unset intentionally and for a good reason. Please accept my apology!

> 
> I didn't add DOCBOOK_XSL_172 to the F-10 packages yet, because I know
> that it fixes one problem and causes another.  Either way, we'd be
> shipping packages with known brokeness.  I chose to stick with keeping
> the currently broken '.ft C' behavior.  Pick your poison. ;)
> 
> One of the fedora/red hat folks that works on the xmlto and docbook
> packages was going to take a look, as I very much don't understand the
> documentation stack.  :/
> 
> Anyone who does is very welcome to help find the culprit(s) and help
> get fixes to the proper places.

So the easy solution is out again, quite a pitty. The problem occurs on
F10 as well as F11/rawhide, right?

On a related issue: Does anybody know which asciidoc versions need
asciidoc7compatible to be set? 8.2.5 and above certainly don't, so we
should not advise using it. asciidoc's hg repo doesn't go back much more
(the initial revision does not need it either), and I haven't dug for
their earlier history yet.

Michael J Gruber

  reply	other threads:[~2009-03-13 10:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 14:21 git doc build failure on OS X 10.5.6 (Leopard) during xmlto phase Tom Holaday
2009-03-11 14:43 ` Michael J Gruber
2009-03-11 15:12 ` Jay Soffian
2009-03-11 15:39   ` Jay Soffian
2009-03-11 15:49     ` Jay Soffian
2009-03-11 16:27       ` Michael J Gruber
2009-03-11 20:12         ` Alejandro Riveira
2009-03-12 11:17           ` Michael J Gruber
2009-03-12 14:02             ` Alejandro Riveira Fernández
2009-03-12 17:09             ` Todd Zullinger
2009-03-13 10:29               ` Michael J Gruber [this message]
2009-03-13 16:18                 ` Jay Soffian
2009-03-13 17:06                   ` Michael J Gruber
2009-03-31 20:17                   ` byrnejb
2009-03-31 20:56                     ` byrnejb

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=49BA356D.8050007@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=ariveira@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@gmail.com \
    --cc=tlholaday@gmail.com \
    --cc=tmz@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).