From: Stuart Rackham <srackham@methods.co.nz>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: asciidoc 7--8 compatibility
Date: Thu, 05 Oct 2006 12:40:33 +1300 [thread overview]
Message-ID: <45244671.4030509@methods.co.nz> (raw)
In-Reply-To: <4524343B.8060709@s5r6.in-berlin.de>
Stefan Richter wrote:
> Stuart Rackham wrote:
>> --- asciidoc.conf (revision 53)
>> +++ asciidoc.conf (working copy)
>> @@ -62,9 +62,9 @@
>> __=#emphasis
>> ++=#monospaced
>> \##=#unquoted
>> -endif::asciidoc7compatible[]
>> ^=#superscript
>> ~=#subscript
>> +endif::asciidoc7compatible[]
>
> Could git/Documentation/asciidoc.conf just kill all the various meanings
> of +, ~, ^ and make them into regular characters? In a way that works
> with all versions of asciidoc?
[quotes]
^=
~=
+=
From the AsciiDoc User Guide: "A configuration file [quotes] entry can
be subsequently undefined by setting it to a blank value."
>
> (Frankly, using + as a special character may sound like a neat idea if
> all one wants to do is to typeset poems.)
The rationale for the + is discussed in the AsciiDoc changelog
(http://www.methods.co.nz/asciidoc/CHANGELOG.html). It also brings
AsciiDoc in line with the Ruby RDoc source code documentation system syntax.
--
Stuart Rackham
next prev parent reply other threads:[~2006-10-04 23:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 18:55 [PATCH] escape tilde in Documentation/git-rev-parse.txt Stefan Richter
2006-10-03 5:52 ` Junio C Hamano
2006-10-03 7:31 ` Stefan Richter
2006-10-03 8:00 ` Junio C Hamano
2006-10-03 9:19 ` pull-fetch-param.txt (was Re: [PATCH] escape tilde in Documentation/git-rev-parse.txt) Stefan Richter
2006-10-03 20:01 ` pull-fetch-param.txt Junio C Hamano
2006-10-03 22:38 ` pull-fetch-param.txt Stuart Rackham
2006-10-04 2:03 ` pull-fetch-param.txt Junio C Hamano
2006-10-04 16:40 ` asciidoc 7--8 compatibility (was Re: pull-fetch-param.txt) Stefan Richter
2006-10-04 21:06 ` Stuart Rackham
2006-10-04 22:22 ` asciidoc 7--8 compatibility Stefan Richter
2006-10-04 23:40 ` Stuart Rackham [this message]
2006-10-04 16:28 ` pull-fetch-param.txt Stefan Richter
2006-10-04 17:15 ` pull-fetch-param.txt Stefan Richter
2007-07-12 13:06 ` pull-fetch-param.txt (was Re: [PATCH] escape tilde in Documentation/git-rev-parse.txt) Gerrit Pape
2007-07-12 21:58 ` pull-fetch-param.txt Junio C Hamano
2007-07-13 5:53 ` pull-fetch-param.txt Gerrit Pape
2007-07-13 7:17 ` pull-fetch-param.txt Junio C Hamano
2007-07-13 7:48 ` pull-fetch-param.txt Gerrit Pape
2007-07-20 14:32 ` pull-fetch-param.txt Gerrit Pape
2007-07-20 16:45 ` pull-fetch-param.txt Junio C Hamano
2007-07-20 17:09 ` pull-fetch-param.txt Julian Phillips
2007-07-20 18:01 ` pull-fetch-param.txt 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=45244671.4030509@methods.co.nz \
--to=srackham@methods.co.nz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).