| Age | Commit message (Collapse) | Author |
|
|
|
Closes #8003.
|
|
This reverts commit c1ab48874c04142988505ca5c5caa6626bb68211.
Mistake in measurement.
|
|
Profiling the muse reader revealed that these were creating huge thunks.
|
|
This leads to some performance improvements.
|
|
This improves some benchmarks significantly.
|
|
Sources, the data type passed to the `Reader` function in custom
readers, are now accepted as input to `pandoc.read`.
|
|
|
|
These commands take optional arguments with () and [],
which can lead to problems if the content of the table
cell begins with these characters.
Closes #8001.
|
|
|
|
|
|
|
|
This further reduces memory usage.
See #7943.
|
|
Closes #8000.
|
|
These are actually supported by `\includegraphics`, though
this is not well documented. See
https://tex.stackexchange.com/questions/7938/pdflatex-includegraphics-and-multi-page-pdf-files
Partially addresses #7181.
|
|
Math elements with a name, classes, or other fields are wrapped in a
`Span` with these attributes.
|
|
Refactor for readability.
Co-authored-by: Ola Wolska <[email protected]@gmail.com>
Co-authored-by: Ivar de Bruin <[email protected]>
Co-authored-by: Jaap de Jong <[email protected]>
|
|
|
|
The package is a dependency of hslua; all important modules are
re-exported.
|
|
This allows better round-tripping, because the JATS
writer adds the `ref-` prefix to the citation id to get
the ref element's id.
|
|
Handle issn and isbn; use simpler form for issued date.
|
|
Not 'pages' as we had before. It should go to 'lpage' and 'rpage',
not 'page-range'. See
https://jats.nlm.nih.gov/archiving/tag-library/1.1/element/page-range.html
Fixed some mistakes in test #7042.
|
|
Closes #7995.
|
|
Closes: #7993
|
|
Previously when generating JATS with the `element_citations`
extension enabled, the references were put in a doubly-nested
ref-list element (`<ref-list><ref-list>...`). This is now fixed.
Closes #7990.
|
|
This allows tables with ids to be linked to.
Closes #7285.
|
|
Because many of the exported things aren't combinators...
Also remove redundant explot of indentWith from T.P.Parsing.Lists.
|
|
|
|
|
|
|
|
|
|
See #7943.
|
|
|
|
Grid table parsing in Markdown and rst are updated use the same
functions. Functions are generalized to meet requirements for both
formats.
This change also lays the ground for further generalizations in table
parsers, including support for advanced table features.
API changes in Text.Pandoc.Parsing:
- Parse results of functions `tableWith'` and `gridTableWith'` are now a
`mf TableComponents` instead of a quadruple of alignments, column
widths, header rows and body rows.
Additional exports from Text.Pandoc.Parsing:
- `tableWith'`
- `TableComponents`
- `TableNormalization`
- `toTableComponents`
- `toTableComponents'`
|
|
|
|
Citeproc adopted the BibTeX convention to use the author name "others"
when there are additional authors that are not named. JATS uses the
`<etal>` element for this.
|
|
|
|
|
|
|
|
This modifies `processCitations` so that pandoc will look not just
in the document body but in metadata for a Div with id `refs` in
which to place the formatted bibliography.
Thus, one can include a metadata field, say `refs`, whose content
is an empty div with id `refs`, and the formatted bibliography
will be put into this metadata field. It may then be interpolated
into a template using the variable `refs`.
Closes #7969.
Closes #526 by providing a way to interpolate references into
a template.
|
|
This allows `<div>` to be suppressed using `-raw_html`.
Previously `native_divs` was enabled but could
not be suppressed, because it was not in the list of
available extensions for commonmark-based formats.
Closes #7965.
|
|
This requires at least containers 0.6.0.1, which ships with the oldest
GHC version currently supported by pandoc (GHC 8.6).
|
|
|
|
If the package is local but causes parse errors, parse
everything up to the error and skip the rest. Issue a
CouldNotParseIncludeFile warning indicating that parsing
failed at that point.
T.P.Logging: add CouldNotParseIncludeFile constructor.
|
|
|
|
|
|
that keeps track of whether macros are expanded. This allows
us to improve performance a bit by avoiding unnecessary
runs of the macro expansion code (e.g. from 24 ms to 20 ms on
our standard benchmark).
|
|
|
|
This follows the current default org-mode behavior.
Closes: #3245
|
|
|