aboutsummaryrefslogtreecommitdiff
path: root/MANUAL.txt
AgeCommit message (Collapse)AuthorFilesLines
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
2019-10-14Fixed typo in example.John MacFarlane1-1/+1
2019-10-14KaTeX math: respect classoption=fleqn variablemb211-0/+6
closes #5815
2019-10-11More documentation of default filesJohn MacFarlane1-0/+16
2019-10-11Fix `gfm_auto_identifiers` behavior with emojis.John MacFarlane1-0/+1
Closes #5813. Note that we also now use emoji names for emojis when `ascii_identifiers` is enabled.
2019-10-11Improve sample --defaults file in MANUAL.txt.John MacFarlane1-63/+113
2019-10-10Improve parsing of --defaults.John MacFarlane1-69/+89
- Add FromYAML instances to Opt and to all subsidiary types. - Remove the use of HsYAML-aeson, which doesn't give good position information on errors. - Rename some fields in Opt to better match cli options or reflect what the ycontain [API change]: + optMetadataFile -> optMetadataFiles + optPDFEngineArgs -> optPDFEngineOpts + optWrapText -> optWrap - Add IpynbOutput enumerated type to Text.Pandoc.App.Opts. Use this instead fo a string for optIpynbOutput. - Add FromYAML instance for Filter in Text.Pandoc.Filters. With these changes parsing of defaults files should be complete and should give decent error messages. Now (unlike before) we get an error if an unknown field is used.
2019-10-10Fix examplel for defaults.John MacFarlane1-2/+2
2019-10-10Added documentation for --defaults.John MacFarlane1-0/+103
2019-10-10`--metadata-file`: when multiple files specified, second takes precedence...John MacFarlane1-8/+10
on conflicting fields. This changes earlier behavior (but not in a release), where first took precedence. Note that this may seem inconsistent with the behavior of multiple YAML blocks within a document, where the first takes precedence. Still, it is convenient to be able to override defaults with options later on the command line.
2019-10-10Make some writers sensitive to 'unlisted' class on headings.John MacFarlane1-0/+5
If this is present on a heading with the 'unnumbered' class, the heading won't appear in the TOC. This class has no effect if 'unnumbered' is not also specified. This affects HTML-based writers (including slide shows and epub), LateX (including beamer), RTF, and PowerPoint. Other writers do not yet support `unlisted`. Closes #1762.
2019-10-07Remove misleading sentence in --variables documentation.John MacFarlane1-5/+2
2019-10-06Clarify that --dpi provides a default and doesn't override...John MacFarlane1-3/+6
dpi values specified in the images themselves. See #5721.
2019-10-03PR corrections.Wandmalfarbe1-1/+1
2019-10-03Add documentation for the variable `hyperrefoptions`.Wandmalfarbe1-0/+11
2019-09-29Minor reformatting of exit code table.John MacFarlane1-23/+24
2019-09-29MANUAL: Use a table for exit codes.John MacFarlane1-23/+25
2019-09-29MANUAL: Put all template variable docs into one section.John MacFarlane1-34/+38
2019-09-29MANUAL.txt - use axt headers consistently.John MacFarlane1-163/+85
2019-09-29MANUAL.txt: Add fuller documentation of templates.John MacFarlane1-72/+261
Including new template syntax, partials, etc. Closes #5779.
2019-09-29Raise error on unsupported extensions. Closes #4338.John MacFarlane1-1/+4
+ An error is now raised if you try to specify (enable or disable) an extension that does not affect the given format, e.g. `docx+pipe_tables`. + The `--list-extensions[=FORMAT]` option now lists only extensions that affect the given FORMAT. + Text.Pandoc.Error: Add constructors `PandocUnknownReaderError`, `PandocUnknownWriterError`, `PandocUnsupportedExtensionError`. [API change] + Text.Pandoc.Extensions now exports `getAllExtensions`, which returns the extensions that affect a given format (whether enabled by default or not). [API change] + Text.Pandoc.Extensions: change type of `parseFormatSpec` from `Either ParseError (String, Extensions -> Extensions)` to `Either ParseError (String, [Extension], [Extension])` [API change]. + Text.Pandoc.Readers: change type of `getReader` so it returns a value in the PandocMonad instance rather than an Either [API change]. Exceptions for unknown formats and unsupported extensions are now raised by this function and need not be handled by the calling function. + Text.Pandoc.Writers: change type of `getWriter` so it returns a value in the PandocMonad instance rather than an Either [API change]. Exceptions for unknown formats and unsupported extensions are now raised by this function and need not be handled by the calling function.
2019-09-28MANUAL.txt: fixed some markdown errors.John MacFarlane1-7/+7
2019-09-24odt: Add external option for native numberingNils Carlson1-0/+10
This adds an external options +native_numbering to the ODT writer enabling enumeration of figures and tables in ODT output.
2019-09-22Make `plain` output plainer.John MacFarlane1-0/+8
Previously we used the following Project Gutenberg conventions for plain output: - extra space before and after level 1 and 2 headings - all-caps for strong emphasis `LIKE THIS` - underscores surrounding regular emphasis `_like this_` This commit makes `plain` output plainer. Strong and Emph inlines are rendered without special formatting. Headings are also rendered without special formatting, and with only one blank line following. To restore the former behavior, use `-t plain+gutenberg`. API change: Add `Ext_gutenberg` constructor to `Extension`. See #5741.
2019-09-21Update documentation wrt docx reader custom style namesNikolay Yakimov1-3/+3
2019-09-20Preserve built-in styles in DOCX with custom style (#5670)Ben Steinberg1-2/+4
This commit prevents custom styles on divs and spans from overriding styles on certain elements inside them, like headings, blockquotes, and links. On those elements, the "native" style is required for the element to display correctly. This change also allows nesting of custom styles; in order to do so, it removes the default "Compact" style applied to Plain blocks, except when inside a table.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-16 19:00:08 +0000