Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes #5705.
|
|
|
|
Closes #5685.
|
|
Details at https://groups.google.com/forum/#!topic/pandoc-discuss/c861tTdCFTg
Fix XWiki output for
```
+----------+----------+
| Col A | Col B |
+==========+==========+
| Row A | * Item A |
| | * Item B |
+----------+----------+
```
from (notice that the following XWiki code renders as a table followed by a singleton list)
```
|=Col A|=Col B
|Row A|*. Item A
*. Item B
```
to
```
|=Col A|=Col B
|Row A|(((*. Item A
*. Item B
)))
```
|
|
|
|
It won't in a future version.
|
|
|
|
* Require recent doctemplates. It is more flexible and
supports partials.
* Changed type of writerTemplate to Maybe Template instead
of Maybe String.
* Remove code from the LaTeX, Docbook, and JATS writers that looked in
the template for strings to determine whether it is a book or an
article, or whether csquotes is used. This was always kludgy and
unreliable. To use csquotes for LaTeX, set `csquotes` in your
variables or metadata. It is no longer sufficient to put
`\usepackage{csquotes}` in your template or header includes.
To specify a book style, use the `documentclass` variable or
`--top-level-division`.
* Change template code to use new API for doctemplates.
|
|
The web service passed in to `--webtex` may render formulas using inline
or display style by default. Prefixing formulas with the appropriate
command ensures they are rendered correctly.
This is a followup to the discussion in #5656.
|
|
Return value is now Text rather than being polymorphic.
This makes room for upcoming removal of the TemplateTarget
class from doctemplates.
Other code modified accordingly, and should compile with
both current and upcoming version of doctemplates.
|
|
We add `\textstyle` to the beginning of the formula to ensure it will be rendered in inline style.
Closes #5655.
|
|
Previously we just omitted these. Now we render them
using `\hfill\break` instead of `\\`. This is a revision
of a PR by @sabine (#5591) who should be credited with the
idea.
Closes #3324.
|
|
Workaround for Word Online shortcomming. Fixes #5645
Also, make list para properties go first.
This reordering of properties shouldn't be necessary but
it seems Word Online does not understand the docx correctly otherwise.
|
|
The `raw_attribute` will be used to mark raw bits, even HTML
and LaTeX, and even when `raw_html` and `raw_tex` are enabled,
as they are by default.
To get the old behavior, disable `raw_attribute` in the writer.
Closes #4311.
|
|
Closes #5650.
|
|
Closes #5107.
|
|
Closes #5588.
|
|
* Let the user choose type of PDF/A generated with ConTeXt (closes #5608)
* Updated ConTeXt test documents for changes in tagging
* Updated color profile settings in accordance with ConTeXt wiki
* Made ICC profile and output intent for PDF/A customizable
* Read pdfa variable from meta (and updated manual)
|
|
Closes #5551
|
|
Do not override "fileN" medias when writing to EPUB format (fix #4206)
|
|
Now we boldface code but not other things. This matches the
most common style in man pages (particularly option lists).
Also, remove a regression in the last commit in which 'nowrap'
was removed.
|
|
Previously the bold-facing would be interrupted by
other formatting, because we used `.B`.
Closes #5620.
|
|
In addition, the code generating the image has been moved
to the template, to make it more customizable.
Those who use custom EPUB templates will need to adjust their
templates, adding the code to generate the cover image.
(Previously this was just inserted into 'body'.)
Closes #5643.
|
|
Also document addition of data- prefix to unknown attributes.
Closes #5646.
|
|
|
|
introduced by e87b54dcad5e37133bc0f4cfc8039e9fd0dd1b4e
|
|
|
|
This commit alters the way in which the Powerpoint writer treats
inline code and code blocks.
- Inline code is now formatted at the same size as the surrounding
text.
- Code blocks are now given a margin and font size according to their
level.
- Furthermore this commit allows changing the font with which code is
formatted via the `monofont` option.
Tested in
- PowerPoint 365 for Windows - 1808 (Build 10730.20344 Click-to-Run)
- PowerPoint 365 for Mac - 16.26 (19060901)
|
|
We use the innermost attribute in nested cases.
Closes #4634.
|
|
This causes compilation errors, and I don't know how
to work around them. Closes #5574.
|
|
We try to parse the date and convert to year, month, day,
as expected in pub-date. We also add an iso-8601-date attribute
if possible.
|
|
It's only allowed in a few special contexts, and not in
p elements.
|
|
The JATS spec restricts contents of certain
elements (fn, list-item); this patch wraps
elements that can't go in these contexts inside
p elements with specific-use "wrapper", so the
documents will conform.
Closes #5570.
|
|
Closes #5529.
|
|
Closes #5566.
|
|
Closes #5565.
|
|
This was added in pandoc 2.7.2, but it makes it impossible
to use pandoc-crossref. So this has been rolled back for now,
until we find a good solution to make this behavior optional
(or a creative way to let pandoc-crossref and this feature
to coexist).
See #5474.
|
|
Closes #5420.
|
|
This adds support for Atlassian's jira markup.
Closes #2497
|
|
For example, introduction should go in bodymatter, not frontmatter, and
epigraph, conclusion, and afterward should go in bodymatter, not
backmatter.
For the full list of assignments, see the manual.
Closes #5546.
|
|
e.g. ordered list item, in Markdown writer.
Closes #554.
|
|
Opening and closing tag for math output match now.
|
|
depending on file extension of the image path
|
|
The same text is already in the <figcaption> and
screen-readers would read it twice, see #4737
|
|
Previously we could get an empty ol element, which caused
validation errors with epubcheck.
|
|
add `onlySimpleTableCells` to `Text.Pandoc.Shared`
[API change]
This fixes an inconsistency in the HTML reader, which did not treat tables with `<p>` inside cells as simple.
|
|
|
|
Previously too few backticks were used when the code block
contained an indented line of backticks. (Ditto tildes.)
Cloess #5519.
|
|
A `do` notation was left in a non-monadic function.
|
|
Previously if labels had integer names, it could produce a conflict
with auto-labeled reference links. Now we test for a conflict and find
the next available integer.
Note that this involves adding a new state variable `stPrevRefs` to
keep track of refs used in other document parts when using
`--reference-location=block|section`
Closes #5495
|