aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTristan Stenner <derstenner@gmail.com>2018-03-19 17:20:16 +0100
committerJohn MacFarlane <jgm@berkeley.edu>2018-03-19 09:20:16 -0700
commit24faccdf5daea774d950e6685c38f18c8528b69a (patch)
tree84c5c231382ea926658319f977b6f8e17e6449f2
parentd6f9715230799e922342295a457900f0dd1e2fe9 (diff)
downloadpandoc-24faccdf5daea774d950e6685c38f18c8528b69a.tar.gz
Add examples for raw docx blocks (#4472)
The documentation states that the target format name should match the output format, which isn't the case for `docx`/`openxml`. This PR adds a remark and a frequently requested example (inserting a pagebreak in docx output) to the documentation.
-rw-r--r--MANUAL.txt13
1 files changed, 12 insertions, 1 deletions
diff --git a/MANUAL.txt b/MANUAL.txt
index ff00288af..e08e9e876 100644
--- a/MANUAL.txt
+++ b/MANUAL.txt
@@ -3415,9 +3415,20 @@ And the following produces a raw `html` inline element:
This is `<a>html</a>`{=html}
+This can be useful to insert raw xml into `docx` documents, e.g.
+a pagebreak:
+
+ ```{=openxml}
+ <w:p>
+ <w:r>
+ <w:br w:type="page"/>
+ </w:r>
+ </w:p>
+ ```
+
The format name should match the target format name (see
`-t/--to`, above, for a list, or use `pandoc
---list-output-formats`).
+--list-output-formats`). Use `=openxml` for `docx` output.
This extension presupposes that the relevant kind of
inline code or fenced code block is enabled. Thus, for