diff options
| author | John MacFarlane <jgm@berkeley.edu> | 2020-02-17 09:53:36 -0800 |
|---|---|---|
| committer | John MacFarlane <jgm@berkeley.edu> | 2020-02-17 09:53:36 -0800 |
| commit | 3493d6afaa6586c46898cf8bdb0c45bb70d31f28 (patch) | |
| tree | f3502747a8e9113391eefeb83e1f8eb990d62eeb /MANUAL.txt | |
| parent | 6a01386cd1e562eb3d75975e63c0df1491ecc01e (diff) | |
| download | pandoc-3493d6afaa6586c46898cf8bdb0c45bb70d31f28.tar.gz | |
Allow specifying string value in metadata using `!!literal` tag.
This is experimental. Normally metadata values are interpreted
as markdown, but if the !!literal tag is used they will be interpreted
as plain strings.
We need to consider whether this can still be implemented if
we switch back from HsYAML to yaml for performance reasons.
Diffstat (limited to 'MANUAL.txt')
| -rw-r--r-- | MANUAL.txt | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/MANUAL.txt b/MANUAL.txt index 891f37cf8..c45e8b3d9 100644 --- a/MANUAL.txt +++ b/MANUAL.txt @@ -3914,7 +3914,8 @@ from the main markdown input document. Metadata will be taken from the fields of the YAML object and added to any existing document metadata. Metadata can contain lists and objects (nested -arbitrarily), but all string scalars will be interpreted as Markdown. Fields +arbitrarily), but all string scalars will be interpreted as +Markdown, unless marked with the YAML tag `!!literal`. Fields with names ending in an underscore will be ignored by pandoc. (They may be given a role by external processors.) Field names must not be interpretable as YAML numbers or boolean values (so, for @@ -3945,6 +3946,11 @@ when the field contains blank lines or block-level formatting: This is the abstract. It consists of two paragraphs. + + # This is a YAML comment; it will be ignored. + # The following field is marked as literal and will be + # interpreted as a literal string rather than Markdown: + catalog_number: !!literal '*abc123<f>*' ... Template variables will be set automatically from the metadata. Thus, for |