summaryrefslogtreecommitdiff
path: root/MANUAL.txt
Commit message (Collapse)AuthorAge
* Add `empty_paragraphs` extension.John MacFarlane2017-12-04
| | | | | | | | | | | | | | | | * Deprecate `--strip-empty-paragraphs` option. Instead we now use an `empty_paragraphs` extension that can be enabled on the reader or writer. By default, disabled. * Add `Ext_empty_paragraphs` constructor to `Extension`. * Revert "Docx reader: don't strip out empty paragraphs." This reverts commit d6c58eb836f033a48955796de4d9ffb3b30e297b. * Implement `empty_paragraphs` extension in docx reader and writer, opendocument writer, html reader and writer. * Add tests for `empty_paragraphs` extension.
* MANUAL: note on extensions in gfm.John MacFarlane2017-12-04
|
* Update man page and MANUAL date.John MacFarlane2017-12-02
|
* Add --strip-empty-paragraphs option.John MacFarlane2017-12-02
| | | | This works for any input format.
* Added --print-highlight-style option.John MacFarlane2017-11-28
| | | | | | | | This generates a JSON version of a highlighting style, which can be saved as a .theme file, modified, and used with `--highlight-style`. Closes #4106. Closes #4096.
* Update MANUAL dateJohn MacFarlane2017-11-20
|
* MANUAL: clarify that math extensions work with HTML.John MacFarlane2017-11-18
| | | | | Clarify that `tex_math_dollars` and `tex_math_single_backslash` will work with HTML as well as Markdown.
* MANUAL: update date.John MacFarlane2017-11-11
|
* MANUAL: fix header level of "Extension: emoji"Albert Krewinkel2017-11-09
| | | | The level of the "Extension: `emoji`" heading is reduced from 5 to 4 to conform with the other extension headings.
* Deprecated ancient HTML math methods.John MacFarlane2017-11-07
| | | | | | | `--latexmathml`, `--gladtex`, `--mimetex`, `--jsmath`
* MANUAL: consolidate math documentation (#4049)Mauro Bieg2017-11-07
|
* s/suppport/support/Alexander Krotov2017-11-06
|
* Update MANUAL date and man page.John MacFarlane2017-11-04
|
* Clarify that --setext-headers doesn't affect gfm output.John MacFarlane2017-11-04
| | | | Closes #4035.
* Revise clarification on fenced_divs.John MacFarlane2017-11-04
| | | | (#4039)
* Manual: Edit "Extension: fenced_divs" (#4039)Tristano Ajmone2017-11-04
| | | Add paragraph at end of `Extension: fenced_divs` section to clarify that the actual number of colons in fences is irrelevant. (See issue #4037).
* Support `lineAnchors` (or `line-anchors`) in code blocks, for HTML.John MacFarlane2017-11-02
|
* Removed reference to default.beamer in docs.John MacFarlane2017-11-01
| | | | | | | Also added mention of other templates affecting PDF output with different settings. Closes #4024.
* Updated date on manual and regenerated man page.John MacFarlane2017-10-31
|
* Revise documentation of small caps syntax. (#4013)Andrew Dunning2017-10-31
|
* Fix broken reference links in manual. (#4014)Andrew Dunning2017-10-31
|
* Fixed example of slide columns structure in changelog.John MacFarlane2017-10-31
| | | | | | Also documented this feature in MANUAL.txt. Closes #4015.
* Update date on MANUAL.txtJohn MacFarlane2017-10-27
|
* Improved documentation about markdown and gfm extensions.John MacFarlane2017-10-27
|
* Use CamelCase for JavaScript for uniformityKolen Cheung2017-10-26
| | | other instances when javascript is refered to in pandoc is also in CamelCase, the official casing of JavaScript.
* Fixed filters doc linkJohn MacFarlane2017-10-26
|
* Bring MANUAL, README, and pandoc.cabal description in sync.John MacFarlane2017-10-26
|
* Add creole support to manual.John MacFarlane2017-10-26
|
* Fenced divs: ensure that paragraph at end doesn't become Plain.John MacFarlane2017-10-24
| | | | Added test case.
* Implemented fenced Divs.John MacFarlane2017-10-23
| | | | | | | | | + Added Ext_fenced_divs to Extensions (default for pandoc Markdown). + Document fenced_divs extension in manual. + Implemented fenced code divs in Markdown reader. + Added test. Closes #168.
* Use doctemplates 0.2.1: allows `$--` line comments in templates.John MacFarlane2017-10-20
| | | | Closes #3806.
* Clarify DATADIR in MANUALJohn MacFarlane2017-10-18
|
* Split list of authors from MANUAL.txt into separate file, AUTHORS.md.John MacFarlane2017-10-17
| | | | It was getting too long for a man page.
* Updated AUTHORSJohn MacFarlane2017-10-17
|
* App: added --request-header option.John MacFarlane2017-10-15
|
* Updated authors in MANUAL.txt.John MacFarlane2017-10-11
|
* KaTeX fixes:John MacFarlane2017-10-05
| | | | | | | * In Options.HTMLMathMethod, the KaTeX contsructor now takes only one string (for the KaTeX base URL), rather than two [API change]. * The default URL has been updated to the latest version. * The autoload script is now loaded by default.
* Updated AUTHORS.John MacFarlane2017-09-27
|
* Added `--strip-comments` option, `readerStripComments` in `ReaderOptions`.John MacFarlane2017-09-17
| | | | | | | | | | * Options: Added readerStripComments to ReaderOptions. * Added `--strip-comments` command-line option. * Made `htmlTag` from the HTML reader sensitive to this feature. This affects Markdown and Textile input. Closes #2552.
* Update MANUAL.txt (#3919)Ian2017-09-12
| | | Add URL for Prince HTML > PDF engine
* Support for PDF generation via `weasyprint` and `prince` (#3909)Mauro Bieg2017-09-11
| | | | | | | * Rename --latex-engine to --pdf-engine * In `Text.Pandoc.Options.WriterOptions`, rename `writerLaTeXEngine` to `writerPdfEngine` and `writerLaTeXArgs` to `writerPdfArgs`. * Add support for `weasyprint` and `prince`, in addition to `wkhtmltopdf`, for PDF generation via HTML (closes #3906). * `Text.Pandoc.PDF.html2pdf`: use stdin instead of intermediate HTML file
* Write euro symbol directly in LaTeXAndrew Dunning2017-09-08
| | | | The textcomp package allows pdfLaTeX to parse `€` directly, making the \euro command unneeded. Closes #3801.
* Note use of xcolor in manual.Andrew Dunning2017-09-08
|
* add documentation of limitations of grid tables (#3864)Stephen McDowell2017-08-23
| | | | | - see discussion: https://groups.google.com/forum/#!topic/pandoc-discuss/r9fAeeV3dSw - grid tables cannot have row spans or column spans
* Name change OSX -> macOS (#3869)ickc2017-08-23
| | | | | | | | | | | | * Name change OSX -> macOS fix commit c96b64e This commit finishes remaining osx to macOS change, as well as replacing MacOS with macOS. The reason for the later one is because the "correct" casing of macOS is like that. Apple styles it to looks like iOS, watchOS, tvOS, etc. And unfortunately they all start with a lowercase letter, making propercasing (or even title-casing) odd. * fix casing of Linux, UNIX, and Windows
* Markdown reader: use CommonMark rules for list item nesting.John MacFarlane2017-08-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #3511. Previously pandoc used the four-space rule: continuation paragraphs, sublists, and other block level content had to be indented 4 spaces. Now the indentation required is determined by the first line of the list item: to be included in the list item, blocks must be indented to the level of the first non-space content after the list marker. Exception: if are 5 or more spaces after the list marker, then the content is interpreted as an indented code block, and continuation paragraphs must be indented two spaces beyond the end of the list marker. See the CommonMark spec for more details and examples. Documents that adhere to the four-space rule should, in most cases, be parsed the same way by the new rules. Here are some examples of texts that will be parsed differently: - a - b will be parsed as a list item with a sublist; under the four-space rule, it would be a list with two items. - a code Here we have an indented code block under the list item, even though it is only indented six spaces from the margin, because it is four spaces past the point where a continuation paragraph could begin. With the four-space rule, this would be a regular paragraph rather than a code block. - a code Here the code block will start with two spaces, whereas under the four-space rule, it would start with `code`. With the four-space rule, indented code under a list item always must be indented eight spaces from the margin, while the new rules require only that it be indented four spaces from the beginning of the first non-space text after the list marker (here, `a`). This change was motivated by a slew of bug reports from people who expected lists to work differently (#3125, #2367, #2575, #2210, #1990, #1137, #744, #172, #137, #128) and by the growing prevalance of CommonMark (now used by GitHub, for example). Users who want to use the old rules can select the `four_space_rule` extension. * Added `four_space_rule` extension. * Added `Ext_four_space_rule` to `Extensions`. * `Parsing` now exports `gobbleAtMostSpaces`, and the type of `gobbleSpaces` has been changed so that a `ReaderOptions` parameter is not needed.
* slidy uses https instead of http (#3848)ickc2017-08-17
| | | grep -rl 'http://www.w3.org/Talks/Tools/Slidy2' . | xargs sed -i 's/http:\/\/www\.w3\.org\/Talks\/Tools\/Slidy2/https:\/\/www\.w3\.org\/Talks\/Tools\/Slidy2/g'
* Revision to binary format output to stdout:John MacFarlane2017-08-16
| | | | | | | | We now allow default output to stdout when it can be determined that the output is being piped. (On Windows, as mentioned before, this can't be determined.) Using '-o -' forces output to stdout regardless.
* Change behavior with binary format output to stdout.John MacFarlane2017-08-16
| | | | | | | | | | | | | Previously, for binary formats, output to stdout was disabled unless we could detect that the output was being piped (and not sent to the terminal). Unfortunately, such detection is not possible on Windows, leaving windows users no way to pipe binary output. So we have changed the behavior in the following way: * If the -o option is not used, binary output is never sent to stdout by default; instead, an error is raised. * IF '-o -' is used, binary output is sent to stdout, regardless of whether it is being piped. This works on Windows too.
* Document `gfm` in MANUAL.John MacFarlane2017-08-08
| | | | Closes #3509.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-29 09:44:52 +0000