Age | Commit message (Collapse) | Author | Files | Lines |
|
from which pandoc is run. Closes #5464.
|
|
|
|
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.
|
|
The `system` Lua module provides utility functions to interact with the
operating- and file system. E.g.
print(pandoc.system.get_current_directory())
or
pandoc.system.with_temporary_directory('tikz', function (dir)
-- write and compile a TikZ file with pdflatex
end)
|
|
|
|
|
|
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.
|
|
Previously if you used `--self-contained` with `html-smart` or
`html+smart`, it wouldn't work.
|
|
This is currently possible with `mklatex` and `-outdir`, but
was not yet possible with xelatex and `-output-directory`.
Closes #5462.
|
|
Closes #5463.
|
|
rendered as p tags. Closes #5457.
|
|
We use forward-slash for a directory separator in tmpDir,
even on Windows (because that's what tex likes). So we
should not put a backslash between the tmpDir and the
filename on Windows. This is harmless enough in normal
Windows setups, but it breaks on Cygwin.
Closes #5451. Thanks to @cc2x for noticing and diagnosing
the problem.
|
|
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.
|
|
These seem to be needed for xelatex but not pdflatex.
Closes #5441.
|
|
fixes #5433
|
|
|
|
|
|
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.
|
|
1) Don't append `.html`
2) Add `wikilink` title
This mirrors behavior of other wiki readers. Generally the
`.html` extension is not wanted. It may be important for
output to HTML in certain circumstances, but it can always
be added using a filter that matches on links with title
`wikilink`.
Note that if you have a workflow that uses pandoc to convert
vimwiki to readable HTML pages, you may need to add such a
filter to reproduce current behavior.
Here is a filter that does the job:
```lua
function Link(el)
if el.title == 'wikilink' then
el.target = el.target .. ".html"
end
return el
end
```
Save this as `fixlinks.lua` and use with `--lua-filter fixlinks.lua`.
Closes #5414.
|
|
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.
|
|
The previous built-in reference doc had only title and content
layouts. Add in a section-header slide and a two-content slide, so
users can more easily modify it to build their own templates.
Golden files needed to be regenerated. Checked on MS PowerPoint 2013.
|
|
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.
|
|
Closes #5427.
|
|
Closes #5422.
|
|
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.
|
|
This is the first step toward making templating work better. It seems
that content shapes have a default ph type. In other words, shapes
with *NO PH TYPE* should be considered to have an "obj" ph type, and
used as content shapes.
see https://github.com/scanny/python-pptx/blob/master/docs/dev/analysis/placeholders/slide-placeholders/placeholders-in-new-slide.rst
|
|
fixes #5416
|
|
If the slide deck has a metadata slide (with author, title, etc) and
has speaker notes before any body content, the speaker notes will be
applied to the metadata slide. If there is no metadata slide, pandoc
will behave as before.
|
|
Previously, if notes came after a section-title header (ie, a level-1
header in a slide-level=2 presentation), they would go on the next
slide. This keeps them on the slide with the header.
|
|
According to nbformat docs, this is supposed to render in every
format. We don't do that, but we at least preserve it as a raw
block in markdown, so you can round-trip.
|
|
Sometimes pandoc creates two HTML blocks, e.g. one for
the open tag and one for a close tag. If these aren't
consolidated, only one will show up in output cell.
|
|
These are upside down ? and !, resp.
Closes #5407.
|
|
Closes #5403.
|
|
For
::: {.cell}
---
:::
|
|
The nbformat spec says that when no format is specified,
the raw cell will be rendered in every markup format.
Pandoc doesn't have a construct that works this way,
so we just fall back to `html`.
|
|
Previously we wrongly assumed it would be in a MetaString.
It's an a MetaInlines.
|
|
We now do a better job marshalling numbers from MetaString
OR MetaInlines into JSON Number.
|
|
If the number is integral, we render it as an integral
not a float.
Closes #5398.
|
|
Should be `{}` not empty string.
Partially addresses #5398.
|
|
sum is lazy; replace with `foldl' (+) 0` to avoid stack
overflow in Text.Pandoc.Pretty with very long strings.
Closes #5401.
|
|
This helps with round-tripping.
|
|
Pandoc's MetaValue doesn't have a distinguished number type,
so numbers are put in MetaStrings. If the MetaString consists
entirely of digits, we convert it to a Number.
We should probably consider adding a MetaNumber constructor
to MetaValue, for better round-tripping with JSON etc.
This change aids round-tripping in ipynb metadata fields,
like `toc_depth`.
|
|
|