| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
|
|
Closes #8931.
|
|
|
|
This fixes the memory leak noted in #8762.
Closes #8762.
|
|
Close #8925.
|
|
The DokuWiki writer doesn't render Divs specially, so their presence in
a list (e.g. because of custom-styles) need not prevent a regular
DokuWiki list from being used. (Falling back to raw HTML in this case is
pointless because no new information is given.)
Closes #8920.
|
|
Default is true if no value is specified, so this is fully backwards-compatible.
Closes #8788.
|
|
Closes #8878.
|
|
|
|
|
|
We forgot to filter out CRs as we do in toText.
|
|
(That is, whenever we have the filename and are in a
PandocMonad instance.)
This will lead to more informative error messages for UTF8
encoding, indicating the file path and byte offset where the
error occurs. Closes #8884.
|
|
This is like `Text.Pandoc.UTF8.toText`, except:
- it takes a file path as first argument, in addition to
bytestring contents
- it raises an informative error with source position if
the contents are not UTF8-encoded
[API change]
This replaces `utf8ToText` in `Text.Pandoc.App.Input`.
See #8884.
|
|
|
|
|
|
|
|
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.
|
|
These changes recognize that parseURI does not unescape the path.
Another change is that the canonical form of the path used as the
MediaBag key retains percent-encoding, if present; we only unescape
the string when writing to a file.
See #8918.
Some tests are needed before the issue can be closed.
|
|
In the new code a comma mysteriously turned into a period.
This would have prevented proper separation of the mime type and
content in data uris. Thanks to @hseg for catching this.
|
|
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
|
|
This vulnerability, discovered by Entroy C, allows users to write
arbitrary files to any location by feeding pandoc a specially crafted
URL in an image element. The vulnerability is serious for anyone
using pandoc to process untrusted input. The vulnerability does
not affect pandoc when run with the `--sandbox` flag.
|
|
Closes #8915.
|
|
This message will also be triggered when media is being
extracted to a temporary location, e.g. in PDF production.
|
|
Support for this (introduced in #6350) disappeared when we made an
architectural change.
|
|
Fix for this SO question: https://tex.stackexchange.com/questions/563778/how-to-get-f-syntax-highlighting
|
|
This wasn't implemented before due to an oversight. Closes #8908.
|
|
Closes #8903.
|
|
Closes #8765.
|
