aboutsummaryrefslogtreecommitdiff
path: root/MANUAL.txt
AgeCommit message (Collapse)AuthorFilesLines
2020-03-23Update manual date and man paeg.John MacFarlane1-1/+1
2020-03-20Make MANUAL more explicit about NBSP handling by all_symbols_escapable (#6201)Fabien Schurter1-3/+6
Fixes #6154.
2020-03-13Update copyright year (#6186)Albert Krewinkel1-1/+1
* Update copyright year * Copyright: add notes for Lua and Jira modules
2020-02-17Revert "Allow specifying string value in metadata using `!!literal` tag."John MacFarlane1-7/+1
This reverts commit 3493d6afaa6586c46898cf8bdb0c45bb70d31f28. This might be worth considering in the future, but let's not do it yet...the additional complexity needs a better justification.
2020-02-17Allow specifying string value in metadata using `!!literal` tag.John MacFarlane1-1/+7
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.
2020-02-15Update changelog and man page.John MacFarlane1-1/+1
2020-02-12Introduce new format variants for JATS (#6067)Albert Krewinkel1-1/+4
New formats: - `jats_archiving` for the "Archiving and Interchange Tag Set", - `jats_publishing` for the "Journal Publishing Tag Set", and - `jats_articleauthoring` for the "Article Authoring Tag Set." The "jats" output format is now an alias for "jats_archiving". Closes: #6014
2020-01-31Add Text.Pandoc.Readers.CSV (readCSV).John MacFarlane1-0/+2
This adds csv as an input format. The CSV table is converted into a pandoc simple table. Closes #6100.
2020-01-27Update URLs and use HTTP**S** wherever possible (#6090)Salim B1-62/+62
I've changed _all_ `http:` URLs in the file to their `https` equivalents if the respective sites have properly configured HTTPS.
2020-01-12docs: capitalize Lua where it refers to the programming language nameAlbert Krewinkel1-15/+15
This follows the advise on the Lua website (https://www.lua.org/about.html#name): > […] "Lua" is a name, the name of the Earth's moon and the name of the > language. Like most names, it should be written in lower case with an > initial capital, that is, "Lua".
2020-01-05Bump to 2.9.1.1, update manual.John MacFarlane1-1/+1
2019-12-21Update man page and MANUAL date.John MacFarlane1-1/+1
2019-12-20MANUAL: A bit clearer explanation for `--base-header-level`.John MacFarlane1-2/+3
We now say exactly how to work around the deprecation of this option.
2019-12-17Add jira reader (#5913)Albert Krewinkel1-0/+1
Closes #5556
2019-12-11Regenerate man page.John MacFarlane1-1/+1
2019-12-11Add title-slide-attributes variable to reveal.js template. (#5981)Frederik Elwert1-0/+11
2019-12-07Rename template 'filters' as 'pipes'John MacFarlane1-6/+6
to avoid confusion with the other notion of filter used by pandoc. We may want to rename this upstream in doctemplates as well.
2019-12-07Removed trailing whitespace in manual.John MacFarlane1-5/+5
2019-12-07Document display math syntax in manual.John MacFarlane1-0/+3
2019-12-05Update manual date and man page.John MacFarlane1-1/+1
2019-12-05Clean up manual on pdf generation backend options.John MacFarlane1-13/+22
See #5940.
2019-12-05Roll back part of of `--shift-heading-level-by` change.John MacFarlane1-6/+7
With positive heading shifts, starting in 2.8 this option caused metadata titles to be removed and changed to regular headings. This behavior is incompatible with the old behavior of `--base-header-level` and breaks old workflows, so with this commit we are rolling back this change. Now, there is an asymmetry in positive and negative heading level shifts: + With positive shifts, the metadata title stays the same and does not get changed to a heading in the body. + With negative shifts, a heading can be converted into the metadata title. I think this is a desirable combination of features, despite the asymmetry. One might, e.g., want to have a document with level-1 section headigs, but render it to HTML with level-2 headings, retaining the metadata title (which pandoc will render as a level-1 heading with the default template). Closes #5957. Revises #5615.
2019-11-26Bump to 2.8.0.1 and update changelog and manual.John MacFarlane1-1/+1
2019-11-24Update to doctemplates 0.7.2, update template docs.John MacFarlane1-15/+18
This adds the `nowrap` filter.
2019-11-23Add support for $toc-title$ to HTML (4 and 5) (#5930)Alexandre Franke1-1/+1
2019-11-22Remove grffile requirement in MANUAL.txt (#5927)Ian Max Andolina1-1/+1
See #5848 for the details.
2019-11-22Update date on manual.John MacFarlane1-1/+1
2019-11-20Fix typos (#5919)Brian Wignall1-1/+1
2019-11-18Update man page.John MacFarlane1-1/+1
2019-11-18Update MANUAL.txt for doctemplates changes.John MacFarlane1-4/+8
2019-11-17Reverted the behavior change with `--title-prefix`.John MacFarlane1-2/+1
It now implies `--standalone` again, as before.
2019-11-17Ensure that options imply `--standalone` even in defaults file.John MacFarlane1-2/+2
Certain options (`--self-contained`, `--include-in-header`, etc.) imply `--standalone`. We now handle this after option parsing so that it affects options specified in defaults files too. Behavior change: `--title-prefix` no longer implies `--standalone`.
2019-11-16MANUAL: fix formatting for --shift-heading-level.John MacFarlane1-1/+1
2019-11-16Adjust date on manual, regenerate man page.John MacFarlane1-1/+1
2019-11-14Default files: Allow leaving input-files blank again.John MacFarlane1-1/+1
Leaving it blank yields a Nothing value (interpreted as stdin). Providing an empty list is intepreted as no input. This resolves one part of #5888.
2019-11-13Default files: combine with prior values when appropriate.John MacFarlane1-0/+9
Certain command-line arguments can be repeated: `--metadata-file`, `--css`, `--include-in-header`, `--include-before-body`, `--include-after-body`, `--variable`, `--metadata`, `--syntax-definition`. In these cases, values specified in default files should be added to the list rather than replacing values specified earlier on the command line (perhaps in other default files). So, for example, if one does pandoc --variable foo=3 --defaults d1 --defaults d2 and `d1` sets the variable `bar` and `d2` sets `baz`, all three variables will be set. Closes #5894.
2019-11-13Update manual in light of last change.John MacFarlane1-1/+1
2019-11-11Clarify MANUAL.txt on `--preserve-tabs`John MacFarlane1-3/+4
2019-11-11Markdown reader: fix small super/subscript issue.John MacFarlane1-6/+7
Superscripts and subscripts cannot contain spaces, but newlines were previously allowed (unintentionally). This led to bad interactions in some cases with footnotes. E.g. ``` foo^[note] bar^[note] ``` With this change newlines are also not allowed inside super/subscripts. Closes #5878.
2019-11-07Change merge behavior for metadata.John MacFarlane1-3/+3
Previously, if a document contained two YAML metadata blocks that set the same field, the conflict would be resolved in favor of the first. Now it is resolved in favor of the second (due to a change in pandoc-types). This makes the behavior more uniform with other things in pandoc (such as reference links and `--metadata-file`).
2019-11-06Allow singular input-file in defaults file.John MacFarlane1-0/+1
Closes #5877.
2019-11-03Revise MANUAL's comment on table-mode.John MacFarlane1-3/+2
2019-11-03Allow pdf output to stdout.John MacFarlane1-1/+2
PDF output will not be output to the terminal, but can be sent to stdout using either `-o -` or a pipe. The intermediate format will be determined based on the setting of `--pdf-engine`. Closes #5751.
2019-11-02Manual: clarify when macro definitions are passed as raw latex.John MacFarlane1-2/+5
In Markdown input, they are always passed through. In LaTeX, only if `latex_macros` is disabled.
2019-11-02LaTeX reader: parse macro defs as raw latex...John MacFarlane1-2/+2
when `latex_macros` is disabled. (When `latex_macros` is enabled, we omit them, since pandoc is applying the macros itself.) Previously, it was documented that the macro definitions got passed through as raw latex regardless of whether `latex_macros` was set -- but in fact they never got passed through.
2019-11-02Document how to use custom writers with `--standalone`.John MacFarlane1-0/+7
Closes #5866.
2019-11-01Revert "ALlow multiple comma-separated files for `--defaults`."John MacFarlane1-3/+2
This reverts commit e96f3fd813b3f8b73c3457ff6e9177e2a4a74164.
2019-11-01ALlow multiple comma-separated files for `--defaults`.John MacFarlane1-2/+3
2019-11-01`--defaults` improvements.John MacFarlane1-6/+3
- ToYAML instance is now for `Opt -> Opt`, rather than `Opt`. - This allows us to handle `--defaults` without clobbering all the options that occur prior to `--defaults` on the command line. (Note, however, that options in `--defaults` can replace these options if the `--defaults` option is used after them, which may be a bit confusing given the name.) - `--defaults` may now be used multiple times on the command line, allowing users to break defaults into different chunks.
2019-10-29Update Template syntax in MANUAL.txt with latest doctemplates.John MacFarlane1-58/+146
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-26 15:47:27 +0000