Age | Commit message (Collapse) | Author | Files | Lines |
|
HTML Reader: Correctly parse inline list-style(-type) for <ol>
|
|
|
|
Previously the left-hand column could not start with 4 or
more spaces indent. This was inconvenient for right-aligned
left columns.
Note that the first (header column) must still have 3 or fewer
spaces indentation, or the table will be treated as an indented
code block.
|
|
Use '=' instead of '#' for atx-style headers in markdown+lhs.
|
|
|
|
Fully implemented features:
* Paragraphs
* Headers
* Basic styling
* Unordered lists
* Ordered lists
* External Links
* Internal Links
* Footnotes, Endnotes
* Blockquotes
Partly implemented features:
* Citations
Very basic, but pandoc can't do much more
* Tables
No headers, no sizing, limited styling
|
|
we no longer need it with the change to toKey, and it
is expensive to skip spaces after every inline.
|
|
Fix implicit header refs for headers with extra spaces
|
|
The abstract populates an "abstract" metadata field.
|
|
|
|
Technically this isn't allowed in an HTML comment, but
we've always allowed it, and so do most other implementations.
It is handy if e.g. you want to put command line arguments
in HTML comments.
|
|
E.g. `<ol type="i">`.
Closes #2313.
|
|
Lines aren't part of the pandoc table model, but we can just
ignore them.
Closes #2307.
|
|
Added test cases.
Closes #2300.
|
|
Closes #2277.
|
|
|
|
“Inline markup is parsed in field names.” [1]
[1] http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#field-lists
|
|
Fix RST reference names with special characters
|
|
Normally these will cause an error in LaTeX, but there
are contexts (e.g. `alltt` environments) where they are
okay. Now that we aren't treating them as super/subscript
outside of math mode, it seems okay to parse them as regular
text.
|
|
|
|
|
|
|
|
|
|
|
|
Org generalize result block
|
|
Trees having a `:noexport:` tag set are not exported. This mirrors
default Emacs Org-Mode behavior.
|
|
Org mode allows headers to be tagged:
``` org-mode
* Headline :TAG1:TAG2:
```
Instead of being interpreted as part of the headline, the tags are now
put into the attributes of empty spans. Spans without textual content
won't be visible by default, but they are detectable by filters. They
can also be styled using CSS when written as HTML.
This fixes #2160.
|
|
Code blocks can be followed by optional result blocks, representing the
output generated by running the code in the code block. It is possible
to choose whether one wants to export the code, the result, both or
none.
This patch allows any kind of `Block` as the result. Previously, only
example code blocks were recognized.
|
|
Group code used to parse block arguments together in one place. This
seems better than having part of the code mixed between unrelated
parsing state changing functions.
|
|
Added `stateHeaderKeys` to `ParserState`; this is a `KeyTable`
like `stateKeys`, but it only gets consulted if we don't find
a match in `stateKeys`, and if `Ext_implicit_header_references`
is enabled.
Closes #1606.
|
|
We only support the href attribute, as there's no place for
"target" in the Pandoc document model for links.
Added HTML reader test module, with tests for this feature.
Closes #1751.
|
|
Introduced by e9d7504.
This regression caused link and image references containing
raw tex not to parse correctly.
Added test.
Closes #2150.
|
|
Earlier versions had a bug and would wrongly think
opening tags containing attributes with slashes in them
were self-closing.
Closes #2146.
|
|
Closes #2127.
|
|
Closes #2122.
|
|
This fixes a regression (not in any released version) on
things like
hi
: - there
Closes #2098.
|
|
|
|
|
|
This version should be a bit more efficient.
This doesn't help with #1735, however.
|
|
Footnotes: check if '^' follows '['
Links: check if '[' or '(' follows ']'
Shorthand links: attempt to lazily parse suffix as referenceLink
|
|
Closes #2062.
This reverts commit c302bdcdbe97b38721015fe82403b2a8f488a702, reversing
changes made to b983adf0d0cbc98d2da1e2751f46ae1f93352be6.
Conflicts:
src/Text/Pandoc/Parsing.hs
src/Text/Pandoc/Readers/Markdown.hs
src/Text/Pandoc/Readers/Org.hs
src/Text/Pandoc/Readers/RST.hs
|
|
Previously the body of the definition (after the `:` or `~` marker)
needed to be in column 4. This commit relaxes that requirement,
to better match the behavior of PHP Markdown Extra. So, now
this is a valid definition list:
foo
: bar
This patch also helps resolve a potentially ambiguity with table
captions:
foo
: bar
-----
table
-----
Is "bar" a definition, or the caption for the table? We'll count
it as a caption for the table.
Closes #2087.
|
|
If the tag parses as a comment, we check to see if the
input starts with `<!--`. If not, it's bogus comment mode
and we fail htmlTag.
Includes test case. Closes #1820.
|
|
MD Reader: Smart apostrophe after inline math
|
|
Require that `<!` or `<?` be followed by nonspace.
This prevents `</ div>` from being parsed as a comment.
Closes #1820.
|
|
Closes #1909.
Adds new parser combinator to Parsing.hs
`a <+?> b`
: if a succeeds, applies b and mappends
output (if any) to result of a. If b fails,
it's just a, if a fails, whole expression fails.
|
|
|
|
|
|
Closes #1931.
|
|
|