| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The previous algorithm did not handle rowspans; this one does.
Closes #8984.
|
|
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.
|
|
We were adding up cells, not colspans.
Note: there may still be incorrect results in the presence of
rowspans.
See https://github.com/jgm/pandoc/issues/8984#issuecomment-1666467926
|
|
(#8634)"
This reverts commit f257c97170ba8db3b771135b98b198d5de2bdb5b.
For the reason, see #8984. The change caused the "grid shape"
of some tables to change.
|
|
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.
|
|
|
|
We still aren't injecting the style, but this will improve things.
See #6710.
|
|
See #8960.
This is a prelimary fix. A better fix would use a named style
so colors could be adjusted.
|
|
when referring to another svg's content using `<use>`.
Closes #8969.
|
|
Units are optional but allowed.
|
|
Fractional values are okay. See #8969.
|
|
We were computing width and height from viewBox incorrectly.
See #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.
|
|
The fix for #8620 caused the mathjax script to be included
when the table of contents but not the body text of a page
contains math. But it broke the case where the table of
contents doesn't contain math but the page does.
This patch fixes the issue.
Closes #8967.
|
|
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.
|
|
Previously if you did `pandoc -s -t bbb`, it would give you
an error about the missing bbb template instead of saying that
it's not a supported output format.
|
|
In 3.1.5 boolean arguments were allowed an optional argument
(true|false). This created a regression for uses of fused
short arguments, e.g. `-somyfile.html`, which was equivalent
to `-s -omyfile.html`, but now raised an error because
pandoc attempted to parse `o` as a boolean `true` or `false`.
This change adds a preprocessing step on the raw arguments
before they are sent to the option parser. In this preprocessing
step, `-somyfile.html` would be split into two arguments,
`-s` and `-omyfile.html`. The splitting happens when a
short boolean option is followed by another short option.
Closes #8956.
|
|
This was needed for old base versions only.
|
|
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.
|
|
Thanks @fsoedjede
|
|
|
|
|
|
It takes a boolean argument, and now that all of our boolean
flags take such an argument, we can make this one optional for
consistency.
|
|
Always give the name of the relevant argument.
See #8879.
|
|
Previously the backup PNG was exported even if an SVG was
present, but the SVG should be preferred.
Closes #7244.
|
|
|
|
Closes #8952.
|
|
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.
|
|
so the difference between line endings between Windows and Unix
is ignored.
This allows test output to be deterministic across OS versions.
|
|
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 #8946.
|
|
Affects LaTeX writer.
|
|
|
|
|
|
This structure should make it easier to add new block and inline
handlers.
|
|
|
|
Previously we only included ASCII letters. That is correct for
English but not for, e.g., Spanish (see comment in #8525).
A safer approach is to include all letters except those in the
CJK unified ideograph ranges.
|
|
|
|
|
|
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 #8941.
|
|
This supports package loading (as long as the package has been
cached or is local).
|
|
Closes #8933
|
|
|
|
This didn't work before because we were missing an attribute that
tells Word to used fixed widths rather than computing optimal ones.
|
