Re: asciidoc 7--8 compatibility

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]