Age | Commit message (Collapse) | Author | Files | Lines |
|
Pairs where serialized as two-element lists instead, and are now pushed
again as a table with a single key/value pair.
Fixes: #4202
|
|
An additional `Lua.call` was left in during refactoring, which caused an
exception "attempt to call a nil value".
Fixes: #4202
|
|
Closes #4169.
|
|
instead of relying on CSS. Closes #4162. HTML-based templates have had
the custom CSS for div.line-block removed. Those maintaining custom
templates will want to remove this too.
We still enclose line blocks in a div with class line-block.
|
|
|
|
We were missing an `_`.
See #4188.
|
|
We don't yet produce incremental lists in PowerPoint, but we should at
least treat lists inside BlockQuotes as lists, for compatibility with
other slide formats.
|
|
Add Basic JATS reader based on DocBook reader
|
|
|
|
Previously a `reference.docx` in `~/.pandoc` (or the user data dir)
would be used instead, and this could cause problems because a
user-modified docx sometimes lacks vital sections that we count
on the `distArchive` to supply.
Closes #4182.
|
|
If the contents are single `Plain` block then do not wrap them with
a <p> element.
|
|
|
|
|
|
This will allow more to fit on a single slide, and will probably look better.
|
|
This replaces the more specific blockQuote runProp, which only
affected the size of blockquotes. We can use this for notes, etc.
|
|
This currently prints all notes on a final slide.
Note that at the moment, there is a danger of text overflowing the
note slide, since there is no logic for adding further slides. A
future commit will shrink the font size on these notes, but that won't
take care of the problem altogether. (We might have to implement some
sort of clumsy page-breaking logic here based on font size and
text-box dimensions, though that seems like a can of worms.)
|
|
When we encounter a note, we write it to the state directory of notes,
and input a superscript.
|
|
First step toward implementing notes in pptx writer.
|
|
These are currently implemented in terms of a Bold para for the terms,
and then blockquotes for the definitions. THis can be refined a bit in
the future.
|
|
Also add TODO for ordered lists.
|
|
|
|
Closes #4172.
|
|
|
|
Otherwise they can be interpreted as footnote definitions.
Closes #4171.
|
|
This avoids a clash with a deprecated \textlatin command defined
in Babel. Closes #4161.
|
|
fig, table-wrap & caption Divs for JATS writer
|
|
|
|
|
|
The same init file (`data/init`) that is used to setup the Lua
interpreter for Lua filters is also used to setup the interpreter of
custom writers.lua.
|
|
The custom writer used its own `ToLuaStack` instance definitions, which
made it difficult to share code with Lua filters, as this could result
in conflicting instances. A `Stringify` wrapper is introduced to avoid
this problem.
|
|
Support writing <fig> and <table-wrap> elements with <title> and
<caption> inside them by using Divs with class set to on of
fig, table-wrap or cation. The title is included as a Heading
so the constraint on where Heading can occur is also relaxed.
Also leaves out empty alt attributes on links.
|
|
|
|
These were a result of moving functions to the OOXML module.
|
|
This imports the essential Powerpoint writer.
It works following the standard Pandoc conventions for making other
sorts of slides. At the moment, there are still these TODOs:
1. Syntax highlighting is not yet implemented. (This is difficult
because there are no character classes in Powerpoint.)
2. Footnotes and Definition lists are not yet implemented. (Notes will
usually take the form of a final slide.
3. Image placement and auto-resizing has a few glitches.
4. Reference powerpoint files don't work dependably from the command
line. This will be implemented, but at the moment users are advised
to change themes from within Powerpoint.
|
|
This is for functions used by both Powerpoint and Docx writers.
|
|
This fixes a bug in 2.0.4, whereby pandoc could not
read the theme files generated with `--print-highlight-style`.
It also fixes some CSS issues involving line numbers.
Highlighted code blocks are now enclosed in a div with class
sourceCode.
Highlighting CSS no longer sets a generic color for pre
and code; we only set these for class `sourceCode`.
This will close #4133 and #4128.
|
|
That is, just print the link text without the url.
Closes #4136.
|
|
* Deprecate `--strip-empty-paragraphs` option. Instead we now
use an `empty_paragraphs` extension that can be enabled on
the reader or writer. By default, disabled.
* Add `Ext_empty_paragraphs` constructor to `Extension`.
* Revert "Docx reader: don't strip out empty paragraphs."
This reverts commit d6c58eb836f033a48955796de4d9ffb3b30e297b.
* Implement `empty_paragraphs` extension in docx reader and writer,
opendocument writer, html reader and writer.
* Add tests for `empty_paragraphs` extension.
|
|
|
|
This allows a pandoc markdown native div or span to be
rendered in gfm using raw html tags.
|
|
This is a helper allowing other writers to create single
HTML tags.
|
|
Note that `raw_html` is enabled by default for `gfm`, while
`raw_tex` is disabled by default.
|
|
See #2252.
This also changes fixDisplayMath from Text.Pandoc.Writers.Shared
so that it no longer produces empty Para as an artifact.
(That was the original reason the writer omitted them.)
|
|
|
|
Previously both needed to be specified (unless the image was
being resized to be smaller than its original size).
If height but not width is specified, we now set width to
textwidth (and similarly if width but not height is specified).
Since we have keepaspectratio, this yields the desired result.
|
|
Closes #4111.
|
|
This reverts commit 171187a4527497701b3c77bd56cea2d770d4e3b0.
|
|
...if only one of height/width is given.
|
|
|
|
|