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.
This commit is contained in:
parent
d6f9715230
commit
24faccdf5d
1 changed files with 12 additions and 1 deletions
13
MANUAL.txt
13
MANUAL.txt
|
@ -3415,9 +3415,20 @@ And the following produces a raw `html` inline element:
|
||||||
|
|
||||||
This is `<a>html</a>`{=html}
|
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
|
The format name should match the target format name (see
|
||||||
`-t/--to`, above, for a list, or use `pandoc
|
`-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
|
This extension presupposes that the relevant kind of
|
||||||
inline code or fenced code block is enabled. Thus, for
|
inline code or fenced code block is enabled. Thus, for
|
||||||
|
|
Loading…
Add table
Reference in a new issue