summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStuart Rackham <srackham@methods.co.nz>2009-06-09 10:13:10 +1200
committerStuart Rackham <srackham@methods.co.nz>2009-06-09 10:13:10 +1200
commit694d454fa662f13d5aab754c96a5a820612397e0 (patch)
tree3c69ff6774d2008e633cb7eea4807968a41d7521
parentac83e09cc3e67a78ccd7a0560674f961e22a12c0 (diff)
downloadasciidoc-py3-694d454fa662f13d5aab754c96a5a820612397e0.tar.gz
FAQ: Inline literal confusion.
-rw-r--r--doc/asciidoc.txt4
-rw-r--r--doc/faq.txt18
2 files changed, 20 insertions, 2 deletions
diff --git a/doc/asciidoc.txt b/doc/asciidoc.txt
index 9ac0094..abc8225 100644
--- a/doc/asciidoc.txt
+++ b/doc/asciidoc.txt
@@ -2428,8 +2428,8 @@ asciimath, latexmath::
$$::
Inline and block. The double-dollar passthrough is functionally
- identical with one exception: special characters are escaped.
- Example:
+ identical to the triple-plus passthrough with one exception: special
+ characters are escaped. Example:
$$`[[a,b],[c,d]]((n),(k))`$$
diff --git a/doc/faq.txt b/doc/faq.txt
index 4ff8bf7..70b533e 100644
--- a/doc/faq.txt
+++ b/doc/faq.txt
@@ -2,6 +2,24 @@ AsciiDoc Frequently Asked Questions
===================================
+== How do I prevent double-quoted text being mistaken for an inline literal?
+Mixing doubled-quoted text with inline literal passthroughs can
+produce undesired results, for example, all of the following line is
+interpreted as an inline literal passthrough:
+
+ ``XXX'' `YYY`
+
+In this case the solution is to use monospace quoting instead of the
+inline literal:
+
+ ``XXX'' +YYY+
+
+Use the +\pass:[]+ macro if it's necessary to supress
+substitutions in the monospaced text, for example:
+
+ ``XXX'' +pass:[don't `quote` me]+
+
+
== How can I generate a single HTML document file containing images and CSS styles?
With the advent of Internet Explorer 8 all major web browsers now
support the