Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
"Best Practice: When footnotes are grouped at the end of an article,
wrap them in a `<fn-group>` and use an `<xref>` element in the text, as
usual, to tie each footnote in the list to a particular location in the
text."
Closes #5511.
|
|
Existing FB2 readers, such as FBReader, already display links with type="note" as a superscript.
|
|
|
|
Emacs always uses two spaces when indenting the content of src blocks,
e.g., when exiting a `C-c '` edit-buffer. Pandoc used to indent contents
by the space-equivalent of one tab, but now always uses two spaces, too.
Closes: #5440
|
|
The old `` `a__b__c` `` yields emphasis inside code in asciidoc.
To get a pure literal code span, use `` `+a__b__c+` ``.
|
|
Asciidoctor has a different format for smart quotes.
Closes #5487.
|
|
The environment is beamer-only and as far as I'm
aware there's no latex package that provides it
for non-beamer use.
Closes #5485.
|
|
See f11d0c9dc8b61cc38e138aaecb0f0094add3465a
This fixes round-trip failures.
|
|
|
|
Closes #5481. This includes an update to data/jats.csl.
|
|
We do want to recognize "0" as a number, even though
it has "0" as a prefix.
|
|
not a number.
Closes #5479.
|
|
Regression! The fix for #4683 broke this case.
|
|
iOS chooses to render a number of Unicode entities,
including '↩', as big colorful emoji. This can be
defeated by appending Unicode
VARIATION SELECTOR-15'/'VARIATION SELECTOR-16'.
So we now append this character when escaping
strings, for both '↩' and '↔'.
If other characters prove problematic, they can
simply be added to needsVariationSelector.
Closes #5469.
|
|
Closes #5463.
|
|
rendered as p tags. Closes #5457.
|
|
We only treat Span as transparent if it has no attributes.
|
|
Previously an Emph inside a Span was being treated as
nested markup and ignored. With this patch, the Span
is just ignored.
Closes #5446.
|
|
|
|
|
|
This fixes a regression in beamer due to the fix to #5367.
We put table footnotes outside the table in beamer, because
footnote/footnotehyper don't work with beamer.
|
|
I had been using record syntax in an ADT, is bad style, since it means
that each record produces a partial function. Fortunately we weren't
using the partial functions anywhere, so this changes it to positional
syntax.
|
|
When editing a template/reference-doc, the user might be in Master
view, but when producing a slide show, it is assumed that slide view
will be desired. This removes the "lastView" attr from the
viewProps.xml slide so that the presentation will always open up in
slide view.
Note this requires creating a new "ppt/viewProps.xml" instead of just
moving over the old one from the viewProps file. Since this produces a
slightly different order of xml files in the content manifest, the
golden files will have to be rebuilt.
|
|
Add XWiki Support
Closes #1800
|
|
We don't build it at the moment, so it was causing corruption.
|
|
We were previously carrying over too many elements from the layout,
which produced visual artifacts and some corruption. This empties the
sptree (except for properties) after building the shapes, and then
inserts them.
Together with 5e944bf5, fixes #5402
(Note that this addresses the issue and template in that particular
bug report. Other issues will arise no doubt arise with other
templates.)
|
|
Previously we had applied content shapes based on their index (which
was "1", "2" in MS Word 2013). It turns out that this was a
convention, and could not be relied on. Instead we use a default
type (ie, a ph tag with no "type"). This is more correct, and should
make the application of reference documents in PowerPoint much more
robust.
|