Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
The input
[*infile*] [*outfile*]
was getting improperly parsed: "infile" was emphasized, but
"*outfile*" was literal. This was due to failure to parse the
"fallback" in the reference link parser.
Closes #883.
|
|
Closes #856.
|
|
Closes #807.
|
|
|
|
Added tests. This fixes a regression from 1.10.x. Closes #786.
|
|
They do not generate a Quoted element; instead, the double quote
is just turned into a Str with a curly left quote.
This should satisfy the fiction writers. Closes #99 (again).
|
|
* Cleaned up parsing code.
* '-' in an attribute context = '.unnumbered'. The point of this
is to provide a way to specify unnumbered headers in non-English
documents.
|
|
Otherwise some pipe tables get treated as line blocks.
|
|
Closes #772.
|
|
The uri parser is designed for bare URIs. In angle-bracket contexts,
we can be sure that we don't have trailing punctuation. So
`<http://openclipart.org/detail/22566/lego-smiley----happy-by-pitr>`
should work now.
Closes #768.
|
|
(Markdown reader.)
|
|
Added tests for entities in titles and links.
Closes #723.
|
|
We no longer need to use fromEntities on titles.
|
|
Now if mmd_title_blocks is specified, pandoc will parse a
MMD title block if it sees one, even if pandoc_title_blocks is enabled.
|
|
|
|
Parsing failed if you had an unquoted attribute immediately
before the final '}'.
|
|
This reverts commit d46f434d4b8906ae3b983e568549213de94fd1a2.
|
|
|
|
Note: Currently this only affects the markdown reader.
|
|
* Citations will work in markdown even if `--biblio` isn't
specified. Note: this may cause unexpected behavior for people
who use strings of the form `@foo` that are not citations!
* If `--biblio` isn't used, the markdown writer will write markdown
citations rather than CSL-rendered citations.
* This means, for example, that you can do `pandoc -f latex -t markdown`
and convert biblatex or natbib citations into pandoc citations.
|
|
|
|
Now latex macro definitions are preserved when output is latex,
and applied when it is another format, as originally intended.
Partially addresses #730.
\providecommand is still not supported. For this we need changes
to texmath.
|
|
This fixes a subtle regression involving grid tables with
empty cells. Closes #732.
Also added test for grid table with empty cells.
|
|
We no longer needed the smart quote complexity, because of
improvements to singleQuoteStart and singleQuoteEnd.
And we were able to move the check for intraword underscore
to the emphasis parser.
|
|
|
|
|
|
From definitionListItem.
Slight performance improvement.
|
|
Moved a guardEnabled out of an inner loop.
|
|
|
|
|
|
* Tilde code fences can again take bare language.
So
~~~ haskell
is okay, not just
~~~ {.haskell}
* Backtick code blocks can take the bracketed attributes.
* Backtick code blocks don't require a language.
* Consolidated code for the two kinds of fenced code blocks.
Closes #722.
|
|
Otherwise \begin{code}...\end{code} isn't handled
properly in markdown+lhs.
Thanks to Daniel Miot for noticing the bug and
suggesting the fix.
|
|
The 1.10 code assumed that each table header cell contains
exactly one block. That failed for headerless tables (0) and also
for tables with multiple blocks in a header cell.
The code is fixed and tests provided. Thanks to Andrew Lee for
pointing out the bug.
|
|
This reverts commit b158b3fb2182b5c8a6f03759277f4f73cdc24797.
|
|
This allows attributes like `C++`. Any nonspace and non-}.
|
|
Also simplified source URL and link title parsers.
|
|
|
|
Added tests.
|
|
Revises 1a4b47e93368bfbd31daccdfedbd9527ee740201
|
|
* In markdown reader, add a '\1' character to the beginning
of the title of an image that is alone in its paragraph,
if implicit_figures extension is selected.
* In writers, check for Para [Image alt (src,'\1':tit)] and treat
it as a figure if possible.
* Updated tests.
This is a bit of a hack, but it allows us to make implicit_figures
an extension of the markdown reader, rather than the writers.
|
|
|
|
This depends on the new Ext_line_blocks extension.
|
|
This allows explicit attributes to be put on headers, using
a syntax like that for code blocks:
{#id .class .class k=v k=v}
|
|
|
|
Previously header ids were autogenerated by the writers.
Now they are generated (unless supplied explicitly) in the
markdown parser, if the `header_identifiers` extension is
selected.
In addition, the textile reader now supports id attributes on
headers.
|
|
|
|
|
|
Closes #375.
|
|
|