| Age | Commit message (Collapse) | Author |
|---|
|
This fixes a regression introduced by af57648.
We are now preserving the ids from the reference doc's
document.xml.refs, so we shouldn't renumber them or references
introduced by the user (e.g. in a template) will fail.
Closes #10769.
|
|
Closes #10764.
|
|
This should allow one to include an image in a reference.docx and
reference it in an openxml template.
Closes #10759.
|
|
|
|
Closes #10758.
When the alt differs from the caption, but only as regards
formatting, we still use an implicit figure.
|
|
Also, when falling back to a Div with class `figure` for a figure
that can't be represented any other way, include a Div with class
`caption` containing the caption.
Closes #10755.
|
|
Closes #10747.
|
|
|
|
Closes #10744.
|
|
`split` has been deprecated.
|
|
...to determine what to do about `.pdfhref` macros in `ms`
output.
When no PDF engine is specified, we don't use the `.pdfhref`
macros at all. This gives better results for links in formats
other than PDF, since the link text would simply disappear if
it exists only in a `.pdfhref` macro.
When a PDF engine is specified, escape the argument of
`.pdfhref O` in a way that is appropriate.
Remove `groff` extension.
Text.Pandoc.Extensions: remove `Ext_groff` constructor.
See #10738. This revises the earlier commit
3adcb4bd8089cdb8408da5f17780cd49513b7cec.
|
|
If `--pdf-engine` is specified or if a PDF is being produced,
we set the `pdf-engine` variable. This allows writers and
templates to behave differently depending on the PDF engine.
|
|
When `groff` is used as a PDF engine, the `groff` extension
to `ms` is automatically enabled.
Limitations:
- `groff` currently produces larger PDFs than `pdfroff`.
- With `groff`, a table of contents produced with
`--table-of-contents/--toc` will always be placed at the end of
the document.
- Certain characters (e.g. Greek characters) may be dropped in
the PDF outline.
Closes #10738.
|
|
When this extension is enabled, the `ms` writer won't
escape `.pdfhref O` macros in the way that is required
when `pdfroff` is used (octal-encoded UTF-16).
The extension is not enabled by default.
Text.Pandoc.Extensions: add `Ext_groff` constructor [API change].
|
|
Convert newlines to spaces as we do in other formats.
Closes #10730.
|
|
because v4 on unpkg.com is no longer available.
|
|
AVIF is an image extension. This commit enables the Org reader to recognise
AVIF files as images to be displayed, and not simply links.
|
|
`impage` -> `image`.
|
|
We now use the plain writer to render these, so that Greek characters
etc. will show up properly.
Note: the ms output this produces works well with pdfroff but not
with `groff -Tpdf`.
|
|
...are not dropped. Closes #10705.
|
|
The form `\[e aa]` works for groff but not for all roff's (not for
macOS man for instance). So instead we'll emit `e` followed by
an escape for a unicode combining accent.
See #10716.
|
|
This affects T.P.RoffChar, T.P.Writers.Roff,
and the Man and Ms writers.
That is, `\(xy` instead of `\[xy]`. This was the original AT&T troff
form and is the most widely supported. The bracketed form causes
problem for some tools, e.g. `makewhatis` on macOS.
Closes #10716.
|
|
In GFM, you need to use `\\{` rather than `\{` for a literal brace.
Closes #10631.
|
|
Closes #10708.
|
|
This avoids a double slash in the URL's path component, which
sometimes causes problems with CDNs. See #8749.
|
|
In LaTeX's tabular environment, the tabular newline takes an optional
argument that we skip. But it only takes a single optional argument, and
any further square-bracketed text that follows shouldn't be skipped.
Fixes #7512, and also adds a test for the original problem raised in
that issue which was already fixed at some point.
|
|
...instead of defining it again.
|
|
See #10704.
|
|
This improves efficiency. See #10704.
|
|
See #10704.
|
|
...to allow (a) URI escapes, (b) whitespace (which will be ignored).
Partially addresses #10704.
|
|
|
|
E.g. instead of rendering `x<em> space </em>y` as `x* space *y`
we render it as `x *space* y`.
Closes #10696.
|
|
[API change]
|
|
`\phantomsection` is used for anchors. When these occur inside a caption,
a LaTeX error is raised unless the `\phantomsection` is protected using `\protect`.
So we now `\protect` every `\phantomsection` (even outside of captions -- this
seems to be harmless).
|
|
Otherwise the multirow will be excessively wide.
Closes #10685.
|
|
Previously we tried to handle things like commented out list
items:
- one
<!--
- two
-->
- three
and also things like:
- one `and
- two` and
But the code we added to handle these cases caused problems with
other, more straightforward things, like:
- one
- ```
code
```
- three
So we are rolling back all the fanciness, so that the markdown
parser now behaves more like the commonmark parser, in which
indicators of block-level structure always take priority over
indicators of inline structure.
Closes #9865. Closes #7778. See also #5628.
|
|
Otherwise we get `**content**` which means strong emphasis.
This is a more robust solution than using `_`, which won't work
for intraword emphasis.
Closes #10642.
|
|
They are invalid but do occur in the wild.
Closes #10643.
|
|
See #10673.
|
|
It should not accept escaped newlines.
See #10672.
|
|
Users commonly complain about the warning when producing HTML
documents without an explicit title. It seems that an info message
is more appropriate, since pandoc's default here (using the input's
base name) ensures compliance with the standard and many users
are happy with that default. Those who want to make sure the
message is seen can use `--verbose`.
Closes #10671.
|
|
Otherwise we get undesirable results, as the format's native
citation mechanism is used instead of (or in addition to) the
citeproc-generated citations. Closes #10662.
|
|
Closes #10661.
|
|
|
|
Closes #10659.
|
|
Closes #10650.
|
|
This reverts commit cbe67b9602a736976ef6921aefbbc60d51c6755a.
Word sets `w:firstColumn="1"` by default for tables. You have to find
the Table Design tab and explicitly uncheck "First Column" to make this
go away. In most cases, I don't think writers intend to designate
the first column as a row head, so this commit is going to produce
unexpected results. In addition, because of the table normalization
done by pandoc-type's `tableWith`, any table containing a colspanned
cell in the left-hand column will get broken if the first column is
designated a row head. For these reasons it seems best to revert this
change, which was made in response to #9495.
Closes #10627.
|
|
with a YAML exception. See #10231.
|
|
This seems to be required for iOS books app to display the space.
|
