Re: asciidoc problem, and a possible fix

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 25, 2010, 00:51 UTC
Message-ID: <7vljdhjk9r.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4ABB29E2-6DB1-4712-A3E8-CD524983FB0B@kuiki.net>

hachi <hachi@kuiki.net> writes:

Show 7 quoted lines

> I had an issue building git on some centos 5 machines today, and in trying to interpret the error message I formed the attached patch.
>
> The errors were:
> xmlto: input does not validate (status 1)
> /home/hachi/rpm/BUILD/git-1.7.0.3/Documentation/git-filter-branch.xml:463: parser error : PCDATA invalid Char value 7
> Clone it with <literal>git clone +++0+++</literal>.  The clone
>                                     ^

A shot in the dark without sufficient information I could try to make is that you are trying to use an ancient AsciiDoc, perhaps pre-7.1.2?

I am guessing that the following entry from their ChangeLog:

    Version 7.1.2 (2006-03-07)
    --------------------------
    .Additions and changes
     ...
    - An 'inline passthrough' mechanism has been implemented.

refers to this "triple-plus" passthrough, documented in:

    http://www.methods.co.nz/asciidoc/userguide.html#X77

As the use of feature is isolated to only the documentation for filter-branch, I am personally Ok with replacing that passthru with a simpler formatting element that is supported by an ancient version of AsciiDoc (but I didn't look at your patch in the attachment).