| Age | Commit message (Collapse) | Author |
|---|
|
This handles row and colspans. Partially addresses #6344.
It also ensures that cells won't wrap text in places where it
wouldn't normally wrap, even if this means making the cells wider
than requested by the colspec. (Closes #9001. Closes 7641.)
Parameters are different, so this is a breaking [API change].
Markdown, RST, and Muse writers have been adjusted to
use the new `gridTable`.
|
|
When the input is of the form
```
$$
x=y
$$
```
we would previously get:
````
``` math
x=y
```
````
which is ugly.
|
|
|
|
This allows non-string values (booleans, lists, maps)
to be given to template variables on the command line.
Closes #10341.
Supersedes #10342.
|
|
Previously inline TeX was handled in a way that was different
from org's own export, and that could lead to information loss.
This was particularly noticeable for inline math environments
such as `equation`. Previously, an `equation` environment
starting at the beginning of a line would create a raw block,
splitting up the paragraph containing it (see #10836).
On the other hand, an `equation` environment not at the beginning
of a line would be turned into regular inline elements
representing the math. (This would cause the equation number to
go missing and in some cases degrade the math formatting.)
Now, we parse all of these as raw "latex" inlines, which will be
omitted when converting to formats other than LaTeX (and other
formats like pandoc's Markdown that allow raw LaTex).
Closes #10836.
|
|
Internal module, not a change to the public API.
|
|
Closes #9896.
|
|
See #10825.
|
|
This is now only made a CodeBlock when there is a `monospaced`
class.
Otherwise it is made a LineBlock.
Closes #10825.
|
|
Allows using `-t plain+four_space_rule` to emulate the output of pandoc
before #7172. This is useful for users that use pandoc e.g. to
autoformat commit messages.
|
|
Closes #10805.
|
|
Closes #10805.
|
|
Character styles governing the position of the footnote
reference should not be imposed on the footnote text.
Closes #10791.
|
|
Closes #10782.
`\textbaht`, `\textblank`, `\textbigcircle`, `\textbrokenbar`,
`\textbullet`, `\textcentoldstyle`, `\textcopyright`, `\textdagger`,
`\textdegree`, `\textdollar`, `\textdong`, `\textlira`, `\textmu`,
`\textmusicalnote`, `\textonehalf`, `\textonequarter`,
`\textparagraph`, `\textpertenthousand`, `\textpeso`,
`\textquotesingle`, `\textregistered`, `\textsection`,
`\textsterling`, `\textthreequarters`, `\textthreesuperior`,
`\texttwosuperior`, `\textyen`.
|
|
Closes #10781.
|
|
Closes #10772.
|
|
This fixes a regression introduced by af57648.
We used to renumber the Relationships so they didn't conflict with
the set of fixed Relationships we imposed.
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]
|
