aboutsummaryrefslogtreecommitdiff
path: root/src/Text/Pandoc/Readers
AgeCommit message (Collapse)AuthorFilesLines
2017-10-23HTML reader: `htmlTag` improvements.John MacFarlane1-8/+19
We previously failed on cases where an attribute contained a `>` character. This patch fixes the bug. Closes #3989.
2017-10-22LaTeX Reader: support \lettrinemb211-0/+1
2017-10-22LaTeX Reader: use opt function consistentlymb211-3/+3
2017-10-19LaTeX reader: be more forgiving in parsing command options.John MacFarlane1-2/+2
This was needed, for example, to make some minted options work.
2017-10-19LaTeX reader: Strip off quotes in `\include` filenames.John MacFarlane1-1/+2
2017-10-19LaTeX reader: support `\expandafter`.John MacFarlane1-6/+19
Closes #3983.
2017-10-19LaTeX reader: handle `\DeclareRobustCommand`.John MacFarlane1-2/+3
Currently it's just treated as a synonym for `\newcommand`. Handles the second case mentioned in #3983.
2017-10-17Latex reader: Skip spaces in image optionsBen Firshman1-0/+2
2017-10-16Improved handling of include files in LaTeX reader.John MacFarlane2-61/+81
Previously `\include` wouldn't work if the included file contained, e.g., a begin without a matching end. We've changed the Tok type so that it stores a full SourcePos, rather than just a line and column. So tokens keeep track of the file they came from. This allows us to use a simpler method for includes, which doesn't require parsing the included document as a whole. Closes #3971.
2017-10-08LaTeX reader: don't treat "..." as Quoted.John MacFarlane1-2/+0
This caused quotes to be omitted in `\texttt` contexts. Closes #3958. However, a better fix would be to modify the
2017-10-08Small logic fix.John MacFarlane1-2/+1
2017-10-08Org reader: end footnotes after two blank linesAlbert Krewinkel1-4/+5
Footnotes can not only be terminated by the start of a new footnote or a header, but also by two consecutive blank lines.
2017-10-06LaTeX reader: read polyglossia/babel \text($LANG){...}.bucklereed1-113/+129
2017-10-02Markdown reader: Fixed bug with indented code following raw LaTeX.John MacFarlane1-1/+1
Closes #3947.
2017-10-02Org reader: support `\n` export optionAlbert Krewinkel3-2/+5
The `\n` export option turns all newlines in the text into hard linebreaks. Closes #3950
2017-09-30Removed writerSourceURL, add source URL to common state.John MacFarlane2-9/+3
Removed `writerSourceURL` from `WriterOptions` (API change). Added `stSourceURL` to `CommonState`. It is set automatically by `setInputFiles`. Text.Pandoc.Class now exports `setInputFiles`, `setOutputFile`. The type of `getInputFiles` has changed; it now returns `[FilePath]` instead of `Maybe [FilePath]`. Functions in Class that formerly took the source URL as a parameter now have one fewer parameter (`fetchItem`, `downloadOrRead`, `setMediaResource`, `fillMediaBag`). Removed `WriterOptions` parameter from `makeSelfContained` in `SelfContained`.
2017-09-28Muse reader: parse anchorsAlexander Krotov1-1/+11
2017-09-26Muse reader: test metadata parsingAlexander Krotov1-2/+1
2017-09-26Fix a typo: s/collabarators/collaborators/Alexander Krotov1-1/+1
2017-09-25Org reader: update emphasis border charsAlbert Krewinkel1-3/+3
The org reader was updated to match current org-mode behavior: the set of characters which are acceptable to occur as the first or last character in an org emphasis have been changed and now allows all non-whitespace chars at the inner border of emphasized text (see `org-emphasis-regexp-components`). Fixes: #3933
2017-09-17Added `--strip-comments` option, `readerStripComments` in `ReaderOptions`.John MacFarlane2-7/+13
* 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.
2017-09-16Markdown reader: added inlines, inlines1.John MacFarlane1-18/+23
Eventually we'll add `processEmphasis` and `processBracketed` to this. This will allow us to conform to CommonMark rules and fix #3903 and #1735.
2017-09-12Textile reader: allow 'pre' code in list item.John MacFarlane1-8/+4
Closes #3916.
2017-09-11Merge pull request #3911 from labdsf/muse-reader-bracesJohn MacFarlane1-1/+8
Muse reader: parse {{{ }}} example syntax
2017-09-11Muse reader: allow inline markup to be followed by punctuationAlexander Krotov1-2/+3
Previously code was not allowed to be followed by comma, and emphasis was allowed to be followed by letter.
2017-09-11Muse reader: parse {{{ }}} example syntaxAlexander Krotov1-1/+8
2017-09-11Muse reader: parse verbatim tagAlexander Krotov1-1/+6
2017-09-10Muse reader: trim newlines from <example>sAlexander Krotov1-1/+10
2017-09-09Muse reader: debug inline code markupAlexander Krotov1-9/+6
2017-09-08Removed old beamer template.John MacFarlane1-0/+1
We now use the default.latex template for both latex and beamer. It contains conditionals for the beamer-specific things. `pandoc -D beamer` will return this template.
2017-09-06Muse reader: Allow finishing header with EOF (#3897)Alexander1-5/+9
2017-09-05LaTeX reader: Better support for ogonek accents.John MacFarlane1-0/+10
2017-09-05LaTeX reader: Improve handling of accents.John MacFarlane1-15/+17
Handle ogonek, and fall back correctly with forms like `\"{}`.
2017-09-05LaTeX reader: support `\k` ogonek accent.John MacFarlane1-0/+5
2017-09-05Muse reader: require at least one space char after * in header (#3895)Alexander1-1/+1
2017-09-04Muse reader: parse <div> tag (#3888)Alexander1-0/+7
2017-09-04HTML reader: Fix pattern match.John MacFarlane1-1/+1
2017-08-30HTML reader: improved handling of figure.John MacFarlane1-17/+17
Previously we had a parse failure if the figure contained anything besides an image and caption.
2017-08-29Muse reader: parse verse markup (#3882)Alexander1-1/+21
2017-08-29hlint Muse reader (#3884)Alexander1-4/+3
2017-08-27RST reader: Fixed `..include::` directive.John MacFarlane1-9/+9
Closes #3880.
2017-08-25LaTeX reader: improved support for \hyperlink, \hypertarget.John MacFarlane1-6/+23
Closes #2549.
2017-08-25Muse reader: parse <verse> tag (#3872)Alexander1-1/+21
2017-08-24LaTeX reader: RN and Rn, from biblatex (#3854)bucklereed1-1/+29
2017-08-22Muse reader: avoid crashes on multiparagraph inline tags (#3866)Alexander1-2/+2
Test checks that behavior is consistent with Amusewiki
2017-08-22Muse reader: do not allow closing tags with EOF (#3863)Alexander1-3/+2
This behavior is compatible to Amusewiki
2017-08-21Muse reader: add definition list support (#3860)Alexander1-1/+28
2017-08-20LaTeX reader: Set identifiers on Spans used for \label.John MacFarlane1-1/+2
2017-08-20LaTeX reader: allow `]` inside group in option brackets.John MacFarlane1-3/+2
Closes #3857.
2017-08-19Markdown reader: use CommonMark rules for list item nesting.John MacFarlane1-68/+61
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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 08:42:41 +0000