diff options
author | nickbart1980 <nickbart1980@gmail.com> | 2015-05-05 10:01:57 +0000 |
---|---|---|
committer | nickbart1980 <nickbart1980@gmail.com> | 2015-05-05 10:01:57 +0000 |
commit | 4297677ec6cc509db1f14d36e2ca66ea8b44b63b (patch) | |
tree | 3e62415b4f7641dcc9a26b1962aecc594c283acb /README | |
parent | 1b44acf0c59b70cc63f48a23c6f77e45a982aaf9 (diff) |
Update README on in-field markup in biblio databases
Motivated by https://github.com/jgm/pandoc-citeproc/issues/124.
Diffstat (limited to 'README')
-rw-r--r-- | README | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -2688,6 +2688,12 @@ files, but you can use `.bibtex` to force BibTeX. Note that `pandoc-citeproc --bib2json` and `pandoc-citeproc --bib2yaml` can produce `.json` and `.yaml` files from any of the supported formats. +In-field markup: In bibtex and biblatex databases, pandoc-citeproc parses +(a subset of) LaTeX markup; in CSL JSON databases, an HTML-like markup +([specs](http://docs.citationstyles.org/en/1.0/release-notes.html#rich-text-markup-within-fields)); +and in CSL YAML databases, pandoc markdown. `pandoc-citeproc -j` and `-y` +interconvert these markup formats as far as possible. + As an alternative to specifying a bibliography file, you can include the citation data directly in the `references` field of the document's YAML metadata. The field should contain an array of |