| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Closes #2127.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes a regression (not in any released version) on
things like
hi
: - there
Closes #2098.
|
|
|
|
|
|
|
|
| |
Instead, use a forward-slash to join paths, regardless of the
platform. This matches the way MediaBag now works.
See
https://github.com/jgm/pandoc/commit/56e4ecab20613d86a6660547ed87e7ff4b80d632#commitcomment-10858449
|
|
|
|
| |
In-text citation suffix clashes with links and footnotes
|
| |
|
|
|
|
|
|
|
|
| |
`<` should not be escaped as `\<`, for compatibility with
original Markdown. We now escape `<` and `>` with entities.
Also, we now backslash-escape square brackets.
Closes #2086.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| |
| |
| | |
jlduran-latex-tightlist
Conflicts:
data/templates
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, pandoc has hard-coded the following in order to make tight lists in
LaTeX:
```hs
text "\\itemsep1pt\\parskip0pt\\parsep0pt"
```
Which is fine, but does not allow customizations. For example, the `memoir`
class already has a `\tightlist` declaration for this purpose:
```tex
\newcommand{\tightlist}{%
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
```
I'm proposing to use a similar solution:
```diff
@@ In Writers/LaTeX.hs:
-then text "\\itemsep1pt\\parskip0pt\\parsep0pt"
+then text "\\tightlist"
@@ In templates/default.latex:
+\newcommand{\tightlist}{%
+ \setlength{\itemsep}{1pt}\setlength{\parskip}{0pt}\setlength{\parsep}{0pt}}
```
This allows us to customize the tightness to our needs.
Backward Compatibility
If a person is using a custom LaTeX template (not based upon the `memoir`
class), the `\tightlist` declaration must be added.
|
|\ \
| | |
| | | |
Allow digit as first character of a citation key.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Update parser to recognize citation keys starting with a digit.
* Update documentation accordingly.
* Test case added.
See https://github.com/jgm/pandoc-citeproc/issues/97
|
|\ \ \
| | | |
| | | | |
RST Writer: Normalize headings to sequential levels
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
MD Reader: Smart apostrophe after inline math
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | | |
to behave more like section headers. Closes #1658.
|
|/ / /
| | |
| | |
| | |
| | | |
This properly handles filenames containing spaces and dots.
Closes #2074.
|
|\ \ \
| | | |
| | | | |
LaTeX Reader: Code cleanup
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Using `text:h` causes problems with numbering. Closes #2059.
Thansk to @nkalvi for diagnosing this.
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We use `` :raw-latex:`...` `` and add a definition for this
role to the template.
Closes #1961.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
rootzlevel-master
Conflicts:
src/Text/Pandoc/Readers/Org.hs
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Tests for image links with non-image targets, as introduced in
commit 2ca5101.
|
|\ \ \ \ |
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
mpickering-errortype
Conflicts:
benchmark/benchmark-pandoc.hs
src/Text/Pandoc/Readers/Markdown.hs
src/Text/Pandoc/Readers/Org.hs
src/Text/Pandoc/Readers/RST.hs
tests/Tests/Readers/LaTeX.hs
|
| | | |/ /
| | |/| | |
|
|/ / / / |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fixes for multiple docx writer style bugs.
|
| | | | | |
|
| | | | | |
|
| | |/ /
| |/| | |
|
| | | |
| | | |
| | | |
| | | | |
Closes #1858.
|
| | | |
| | | |
| | | |
| | | | |
Closes #1860.
|
|\ \ \ \
| | | | |
| | | | | |
Support shortcut reference links in markdown writer
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Issue #1977
Most markdown processors support the [shortcut format] for reference links.
Pandoc's markdown reader parsed this shortcuts unoptionally.
Pandoc's markdown writer (with --reference-links option) never shortcutted links.
This commit adds an extension `shortcut_reference_links`. The extension is
enabled by default for those markdown flavors that support reading shortcut
reference links, namely:
- pandoc
- strict pandoc
- github flavoured
- PHPmarkdown
If extension is enabled, reader parses the shortcuts in the same way as
it preveously did. Otherwise it would parse them as normal text.
If extension is enabled, writer outputs shortcut reference links unless
doing so would cause problems (see test cases in `tests/Tests/Writers/Markdown.hs`).
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The `tabular` environment allows non-empty column separators
with the "@{...}" syntax. Previously, pandoc would fail to
parse tables if a non-empty colsep was present. With this
commit, these separators are still ignored, but the table gets
parsed. A test case is included.
|