Re: [RFT] Format our Documentation/ with both AsciiDoc 7 & 8

From: Pierre Habouzit <madcoder@debian.org>
Date: Jun 15, 2007, 08:09 UTC
Message-ID: <20070615080935.GB28554@artemis.intersec.eu>
In-Reply-To: <7vfy4t915f.fsf@assigned-by-dhcp.pobox.com>

On Thu, Jun 14, 2007 at 11:34:20PM -0700, Junio C Hamano wrote:

Show 17 quoted lines

> It turns out that the attribute definition we have had for a
> long time to hide "^" character from AsciiDoc 7 was not honored
> by AsciiDoc 8 even under "-a asciidoc7compatible" mode.
> 
> Also the double colon at the end of definition list term needs
> to be attached to the term, without a whitespace.  After this
> minimum fixups, AsciiDoc 8 (I used 8.2.1 on Debian) with
> compatibility mode seems to produce reasonably good results.
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> 
>  * This is "Request for Test" to people who reported problems
>    formatting our documentation with asciidoc 8.  To format with
>    Asciidoc 8, you would need to say something like:
> 
> 	$ make ASCIIDOC8=YesPlease doc

  sadly, it does not fixes the issue I reported with git-pull.1 (e.g.)
that reads:

   <refspec>
       The canonical format of a <refspec> parameter is ?<src>:<dst>; that

whereas it should be:

   <refspec>
       The canonical format of a <refspec> parameter is +?<src>:<dst>; that

But I've not seen any serious or even noticeable regression here.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org