summaryrefslogtreecommitdiff
path: root/doc/faq.txt
diff options
context:
space:
mode:
authorStuart Rackham <srackham@methods.co.nz>2010-10-02 08:58:13 +1300
committerStuart Rackham <srackham@methods.co.nz>2010-10-02 08:58:13 +1300
commit4e87bbd491017652b763b8f420a35204da6bead7 (patch)
tree2c3e12f15e808918020d8145353c03c5c6410531 /doc/faq.txt
parent24ad7eecfd5ea5e6222d36a815da1c6da550b66e (diff)
downloadasciidoc-git-4e87bbd491017652b763b8f420a35204da6bead7.tar.gz
Documentation updates.
Diffstat (limited to 'doc/faq.txt')
-rw-r--r--doc/faq.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/faq.txt b/doc/faq.txt
index 456f810..a7b28da 100644
--- a/doc/faq.txt
+++ b/doc/faq.txt
@@ -9,6 +9,15 @@ AsciiDoc Frequently Asked Questions
newer FAQs may apply to the trunk and not the current release.
======
+== AsciiDoc sometimes generates invalid output markup, why?
+AsciiDoc is backend agnostic, the 'asciidoc' command has no knowledge
+of the syntax or structure of the backend format that it generates.
+Output document validation (syntactic and structural) should be
+performed separately by external validation tools. For example,
+AsciiDoc's 'a2x' toolchain command automatically performs validation
+checks using 'xmllint'.
+
+
== The AsciiDoc toclevels attribute does not work with DocBook outputs, why?
DocBook has no provision for specifying table of contents levels but
you can set the TOC level further down the toolchain by passing the