Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Currently we keep the fancy title slide and add a new
slide with the same title and whatever content was under the
header.
This changes behavior of slides, but is consistent with the
new behavior of the revealjs and other HTML slide show writers.
See #4317.
|
|
This facilitates real 2D revealjs slideshows, with
content under the top-level slide in each stack.
It also enables notes on title slides.
Closes #4317 and #5237.
|
|
Closes #5336.
|
|
...to allow warnings to be threaded through.
Additional fix for #5343.
|
|
Closes #5343.
|
|
The haddock module header contains essentially the
same information, so the boilerplate is redundant and
just one more thing to get out of sync.
|
|
Add ReaderOptions parameter to yamlToMeta [API change].
fixes #5272
|
|
Add command line option `--ipynb-output=all|none|best`.
Closes #5339.
|
|
|
|
Closes #3195.
Note that you can use --pdf-engine-opt=-outdir=bar to specify
a persistent temp dir.
|
|
remove `Author`, closes #5334
|
|
Use span with single class "underline" as in docx writer.
|
|
This improves on the original fix to #5285 by preventing
other mixed lists (lists with a mix of Plain and Para
elements) that were allowed given the original fix.
|
|
This ensures that a figure containing a single image
is parsed as a pandoc "implicit figure" (i.e., a
Para with a single Image whose title attribute begins
with `fig:`). More complex figures will still be parsed
as divs.
Closes #5321.
|
|
Closes #5229.
|
|
This module is one of the most opaque parts of the docx reader: it
deals with the fact that runs have non-nesting formatting, so we have
to figure out the nesting on the fly as we combine them.
We start adding commenting, so new developers can understand and, if
necessary, modify this module. Specific function comments will be
added in the future, but this offers a global description of the
purpose of the module.
|
|
|
|
We have to add one final mempty when we're combining in order to trim
inlines appropriately. (We need to use our own trimming routines here
due to the way that formatted inlines are smushed together when
converting from docx.)
Closes #5273
|
|
|
|
|
|
|
|
|
|
|
|
This allows more control over the common state from within Lua scripts.
|
|
...including data: URIs.
Closes #5303.
|
|
Previously parsing would break if the code block
contained a string of backticks of sufficient length
followed by something other than end of line.
Closes #5304.
|
|
This reverts commit 39889c22df578a4310bcf549fcd507c08fbf1416.
|
|
|
|
The rid attribute can have a space-separated list of ids.
Closes #5310.
|
|
We had previously walked the document to unwrap sdt/sdtContent and
smartTag tags in `word/document.xml`, but not in the
`word/{foot/end}note.xml` and `word/comments.xml`.
Closes #5302
|
|
|
|
even if a richer format is included.
We don't know what output format will be needed.
The fallback can always be weeded out using a filter.
Closes #5293.
|
|
Note that doc-biblioref is only used when link-citations produces
links, since it belongs on links.
See #4213.
|
|
closes #5290
|
|
|
|
The file `init.lua` in pandoc's data directory is run as part of
pandoc's Lua initialization process. Previously, the `pandoc` module was
loaded in `init.lua`, and the structure for marshaling was set-up after.
This allowed simple patching of element marshaling, but made using
`init.lua` more difficult:
- it encouraged mixing essential initialization with user-defined
customization;
- upstream changes to init.lua had to be merged manually;
- accidentally breaking marshaling by removing required modules was
possible;
Instead, all required modules are now loaded before calling `init.lua`.
The file can be used entirely for user customization. Patching
marshaling functions, while discouraged, is still possible via the
`debug` module.
|
|
|
|
|
|
|
|
|
|
|
|
so that 0 means "not in a list," which is more what
one would expect.
|
|
Closes #5285. Previously the algorithm allowed list items
with a mix of Para and Plain, which is never wanted.
compactify in T.P.Shared has been modified so that, if
a list's items contain (at the top level) Para elements
(aside from perhaps at the very end), ALL Plains are
converted to Paras.
|
|
|
|
see #5272
|
|
Some paths in archives are absolute (have an opening slash) which, for
reasons unknown, produces a failure in the test suite on MS
Windows. This fixes that by removing the leading slash if it exists.
Closes #5277 (previously closed with 4cce0ef but reopened due to this bug).
|
|
This reverts commit 2142bbe572cea00b7bb5ad3e10a3afb26845a1f7.
|
|
Try fixing a parsing error on windows by insisting that the parser use
a Posix filepath library for splitting doc paths in a zipfile. (It
might default on Windows to using a backslash as a separator, while
it's always a forward-slash in zip archives.)
|
|
* clarify function name. We had previously used `getDocumentPath`,
but `Document` is an overdetermined term here. Use
`getDocumentXmlPath` to make clear what we're doing.
* Use field notation for setting ReaderEnv. As we've added (and
continue to add) fields, the assignment by position has gotten
harder to read.
* figure out document.xml path once at the beginning of parsing, and
add it to the environment, so we can avoid repeated lookups.
|