Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes #5119.
|
|
We use HTML for a figure in markdown dialects that can't
represent it natively.
Closes #5121.
|
|
|
|
The implementation of `pipeProcess` was rewritten to fix sporadic
failures caused by prematurely closed pipes.
|
|
Give the filename and the byte offset.
Closes #4765.
|
|
[API change]
|
|
|
|
Previously they were not monadic; we now have them run in an
instance of the Pandoc monad, like the other readers and writers.
[API change]
|
|
|
|
Captions used to have the word 'caption' prepended; this
has been removed.
Also, 'thumb' is used instead of 'frame' to allow images
to be resized.
Closes #5105.
|
|
Starting with pandoc 2.4, citations and quoted inlines
were no longer recognized after parentheses. This is
because of commit 9b0bd4ec6f5c9125efb3e36232e6d1f6ac08a728,
which is reverted here.
The point of that commit was to allow relocation of
soft line breaks to before an abbreviation, so that
a nonbreaking space could be added after the
abbreviation. Now we simply leave the soft line
break in place, even though this means that
we won't get a nonbreaking space after "Mr."
at the end of a line (and in LaTeX this may
result in a longer intersentential space).
Those who care about this issue should take care
not to end lines with an abbreviation, or to
insert nonbreaking spaces manually.
Closes #5099.
|
|
Nodes of the form
<meta name="calibre:series" content="Classics on War and Politics"/>
are now included from an epub XML metadata file. You can also
include this information in your YAML metadata, like so:
calibre:
series: Classics on War and Policitics
In addition, ibooks-specific metadata can now be included via
an XML file. (Previously, it could only be included via YAML
metadata, see #2693.)
Closes #5098.
|
|
|
|
|
|
|
|
Level one lists should start at 0.5in rather than 0.75in.
(At least this is how LibreOffice behaves for me with a new
document.)
|
|
ODT writer: Fix list indentation
|
|
Previously lists were indented by half an inch on the first line
for each level of nesting. This resulted in lists that looked like
this:
1. The first line of the list point text
the second line of the same list point.
Fix this and bring style into line with libreoffice standards:
1. The first line of the list point text
the second line of the list point text.
|
|
|
|
Word has a 40 character limit for bookmark names. In
addition, bookmarks must begin with a letter. Since
pandoc's auto-generated identifiers may not respect
these constraints, some internal links did not work.
With this change, pandoc uses a bookmark name based
on the SHA1 hash of the identifier when the identifier
isn't a legal bookmark name.
Closes #5091.
|
|
|
|
Use `.`+ as list markers to support nested ordered lists. Closes #5087.
Support list number styles. Closes #5089.
|
|
Equality of Lua objects representing pandoc AST elements is tested by
unmarshalling the objects and comparing the result in Haskell. A new
function `equals` which performs this test has been added to the
`pandoc.utils` module.
Closes: #5092
|
|
This was a mismatch between pandoc's docx, epub, latex, and markdown
writers and the behavior of pandoc-citeproc, which actually looks
for a div with id 'refs' rather than one with class 'references'.
|
|
Allow decimal points, preceding space.
Also require text 1.1+.
|
|
|
|
|
|
|
|
Parse as raw, but know that these font changing commands
take no arguments.
|
|
Some libraries include custom elements in their FB2 files.
|
|
Meta value strings (MetaString) and booleans (MetaBool) are now
converted to the literal string and the lowercase boolean name,
respectively. Previously, all values of these types were converted to
the empty string.
|
|
Closes #5079.
|
|
Closes #5080.
|
|
See #5080.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See #5014.
Note that this doesn't address the original issue in #5014,
only an unrelated side-issue.
|
|
|
|
even if `writerIncremental` is True.
See #5072.
|
|
See #5057.
|
|
The parameter is Extensions. This allows these functions to
be sensitive to the settings of `Ext_gfm_auto_identifiers` and
`Ext_ascii_identifiers`.
This allows us to use `uniqueIdent` in the CommonMark reader,
replacing some custom code.
It also means that `gfm_auto_identifiers` can now be used
in all formats.
Semantically, `gfm_auto_identifiers` is now a modifier of
`auto_identifiers`; for identifiers to be set, `auto_identifiers`
must be turned on, and then the type of identifier produced
depends on `gfm_auto_identifiers` and `ascii_identifiers` are set.
Closes #5057.
|
|
GitHub doesn't seem to strip non-ascii characters.
|
|
This partially addresses #5057, fixing a bad interaction between
the `ascii_identifiers` extension and the `gfm_auto_identifiers`
extension, and creating identifiers that match the ones GitHub
produces.
This code still needs to be put somewhere common, so the
`gfm_auto_identifiers` extension will work with other formats.
|
|
The condition was from an earlier version.
|
|
|
|
Docx image and code block bookmarks
|