| Age | Commit message (Collapse) | Author |
|---|
|
A number of block elements, like disp-quote, list, and disp-formula, were always treated as inlines if appearing inside paragraphs, even if their usage granted a separate block. The function isElementBlock has been refined to prevent this, and a number of specific parse cases have been added to parseBlock.
Also, some minimal cleanup of the test file, in order for it to pass XML validation against the JATS DTD 1.3 (it was not compliant with the current or any previous versions of JATS).
Closes #8889.
|
|
Closes #8992.
|
|
Closes #8991.
Previously we were putting the label at the beginning of
the Div's contents, but according to the documentation such a
label gets attached to the *preceding* element. We now use an
explicit `#block` and add the label at the end.
|
|
Closes #8991.
|
|
The previous algorithm did not handle rowspans; this one does.
Closes #8984.
|
|
|
|
parser (#8634).""
This reverts commit acbc382ff4b45b9818884779b1e7100de445383d.
|
|
Previously we used the max. #8634 switched to the min, but this
had bad results. This commit sets the RowHeadColumns to the consensus
value from all rows, or 0 if there is no consensus.
See #8984.
|
|
(#8634)"
This reverts commit f257c97170ba8db3b771135b98b198d5de2bdb5b.
For the reason, see #8984. The change caused the "grid shape"
of some tables to change.
|
|
(#8634)."
This reverts commit 52d352a5ae5d66ec74a2c73aa95a8b2abc7ade3c.
|
|
Still unimplemented: global background colors, line numbers.
Closes #6710, obsoletes #6717.
|
|
Currently only colors are supported, not other text styles.
This change includes a new default opendocumnet template.
See #6710.
|
|
when referring to another svg's content using `<use>`.
Closes #8969.
|
|
We were computing width and height from viewBox incorrectly.
See #8969.
|
|
Suggested at #8969.
|
|
- Ensure that width and height attributes don't get specified
twice is both the img tag and the svg include them.
- Omit unnecessary attributes xmlns, xmlns:xlink, and version on
svg element.
- Use 20 character rather than 40 character hashes for generated IDs.
Closes #8965.
|
|
So it doesn't get interpreted as a comment.
Closes #8966.
|
|
Guilhem Moulin noticed that the fix to CVE-2023-35936 was incomplete.
An attacker could get around it by double-encoding the malicious
extension to create or override arbitrary files.
$ echo '' >b.md
$ .cabal/bin/pandoc b.md --extract-media=bar
<p><img
src="bar/2a0eaa89f43fada3e6c577beea4f2f8f53ab6a1d.lua+%2f%2e%2e%2f%2e%2e%2fb%2elua" /></p>
$ cat b.lua
print "hello"
$ find bar
bar/
bar/2a0eaa89f43fada3e6c577beea4f2f8f53ab6a1d.lua+
This commit adds a test case for this more complex attack and fixes
the vulnerability. (The fix is quite simple: if the URL-unescaped
filename or extension contains a '%', we just use the sha1 hash of the
contents as the canonical name, just as we do if the filename contains
'..'.)
|
|
The substantive change here is the `-strue` will now work
instead of being interpreted as `-s -true`.
This is somewhat ad hoc, but I don't think we'll ever have
an output format named `rue`, so it's probably okay.
|
|
|
|
See #8889. The Taylor and Francis guide to JATS says that
`<code>` is block level and not intended to be used inline
within standard text.
|
|
|
|
This fixes a number of regressions from pandoc 2.x.
Properly handle caption, alt attribute in figures.
No longer treat a paragraph with a single image in it as a figure
(we have a dedicated Figure element now).
Closes #8930, closes #8871.
|
|
for SVG images in HTML5. Closes #8948.
Note that SelfContained does not have access to the writer
name, so we check for HTML5 by determining whether the document
starts with `<DOCTYPE! html>`. This means that inline SVG
won't be used when generating document fragments.
An API change could be contemplated to give more flexibility,
but this is okay for now.
|
|
The last release caused all math to be parsed as inline math.
Closes #8949.
|
|
Closes #8942.
|
|
|
|
|
|
The AsciiDoc community now regards the dialect parsed by `asciidoctor`
as the official AsciiDoc syntax, so it should be the target of our
`asciidoc` format.
Closes #8936.
The `asciidoc` output format now behaves like `asciidoctor` used to.
`asciidoctor` is a deprecated synonynm. For the old `asciidoc` behavior
(targeting the Python script), use `asciidoc_legacy`.
The templates have been consolidated. Instead of separate
`default.asciidoctor` and `default.asciidoc` templates, there is
just `default.asciidoc`.
Text.Pandoc.Writers.AsciiDoc API changes:
- `writeAsciiDoc` now behaves like `writeAsciiDoctor` used to.
- `writeAsciiDoctor` is now a deprecated synonym for `writeAsciiDoc`.
- New exported function `writeAsciiDocLegacy` behaves like
`writeAsciDoc` used to.
|
|
Closes #8933
|
|
Closes #8931.
|
|
|
|
This change sets RowHeadColumns to the minimum value of each row, which
gives better results in cases where rows have different numbers of leading th tags.
|
|
Ensure that the current directory is not changed up if a test fails,
and fix messages for the assertion failures.
|
|
|
|
While converting dokuwiki syntax to gfm, the query parameters of images were stripped from the output.
In general this makes sense, as the parameters' semantics are specific to dokuwiki. But it makes it impossible
to access the query in a filter. This change retains the query parameters of image urls in the dokuwiki reader,
by adding it as an extra query attribute.
|
|
Textile supports what it calls "link alias", which are analogous to
Markdown's reference-style links.
|
|
Closes: #8743
|
|
Support for this (introduced in #6350) disappeared when we made an
architectural change.
|
|
|
|
Closes #8765.
|
|
Closes #8365.
|
|
Previously the reference title ended up in a separate
section at the back of the body instead of in the ref-list
in the back matter.
Closes #8364.
|
|
New module Text.Pandoc.Readers.Typst [API change].
|
|
Closes #8718.
|
|
Closes #8893.
|
|
|
|
Improves on the last commit; closes #8831.
|
|
This commit introduces support for the Intense Quote in Docx Conversion.
Previously this was converted to a regular paragraph, but Intense Quote
should be interpreted as a Quote in conversion.
|
|
|
