git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Habouzit <madcoder@debian.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [RFT] Format our Documentation/ with both AsciiDoc 7 & 8
Date: Fri, 15 Jun 2007 10:09:35 +0200	[thread overview]
Message-ID: <20070615080935.GB28554@artemis.intersec.eu> (raw)
In-Reply-To: <7vfy4t915f.fsf@assigned-by-dhcp.pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]

On Thu, Jun 14, 2007 at 11:34:20PM -0700, Junio C Hamano wrote:
> 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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-15  8:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 22:25 [PATCH] Documentation typo Pierre Habouzit
2007-06-06 21:16 ` Junio C Hamano
2007-06-06 22:18   ` Pierre Habouzit
2007-06-07  2:09     ` Junio C Hamano
2007-06-15  6:34 ` [RFT] Format our Documentation/ with both AsciiDoc 7 & 8 Junio C Hamano
2007-06-15  8:09   ` Pierre Habouzit [this message]
2007-06-15 22:52     ` Junio C Hamano
2007-06-16  8:49       ` Pierre Habouzit
2007-06-16 21:05         ` Junio C Hamano

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=20070615080935.GB28554@artemis.intersec.eu \
    --to=madcoder@debian.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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).