Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes #5705.
|
|
the token string is modified by a parser (e.g. accent when
it only takes part of a Word token).
Closes #5686. Still not ideal, because we get the whole
`\t0BAR` and not just `\t0` as a raw latex inline command.
But I'm willing to let this be an edge case, since you
can easily work around this by inserting a space, braces,
or raw attribute. The important thing is that we no longer
drop the rest of the document after a raw latex inline
command that gobbles only part of a Word token!
|
|
Closes #5684. (Note that #5685 is NOT closed by previous commit.)
|
|
Closes #5685.
|
|
The web service passed in to `--webtex` may render formulas using inline
or display style by default. Prefixing formulas with the appropriate
command ensures they are rendered correctly.
This is a followup to the discussion in #5656.
|
|
We add `\textstyle` to the beginning of the formula to ensure it will be rendered in inline style.
Closes #5655.
|
|
|
|
Closes #5654.
|
|
Previously we just omitted these. Now we render them
using `\hfill\break` instead of `\\`. This is a revision
of a PR by @sabine (#5591) who should be credited with the
idea.
Closes #3324.
|
|
like latex does, if an extension is not provided.
Closes #4933.
|
|
Closes #4442.
|
|
The `raw_attribute` will be used to mark raw bits, even HTML
and LaTeX, and even when `raw_html` and `raw_tex` are enabled,
as they are by default.
To get the old behavior, disable `raw_attribute` in the writer.
Closes #4311.
|
|
Closes #5650.
|
|
Closes #5107.
|
|
When `+raw_tex` is enabled, these are passed through literally.
Otherwise, they are handled in a way that emulates LaTeX's behavior.
|
|
Now we boldface code but not other things. This matches the
most common style in man pages (particularly option lists).
Also, remove a regression in the last commit in which 'nowrap'
was removed.
|
|
Previously the bold-facing would be interrupted by
other formatting, because we used `.B`.
Closes #5620.
|
|
They are now ignored if the corresponding command or environment
is already defined.
Closes #5635.
|
|
|
|
Also document addition of data- prefix to unknown attributes.
Closes #5646.
|
|
Closes #5619.
|
|
Closes #5627.
|
|
Closes #3523.
|
|
This causes compilation errors, and I don't know how
to work around them. Closes #5574.
|
|
Closes #5529.
|
|
Closes #5566.
|
|
Closes #5565.
|
|
Previously if the language was not in the list of listings-
supported languages, it would not be added as a class, so
custom syntax highlighting could not be used.
Closes #5540.
|
|
Closes #5420.
|
|
Change is in rawLaTeXInline in LaTeX reader, but
it affects the markdown reader and other readers
that allow raw LaTeX.
Previously, trailing `{}` would be included for
unknown commands, but not for known commands.
However, they are sometimes used to avoid a trailing
space after the command. The chances that a `{}`
after a LaTeX command is not part of the command
are very small.
Closes #5439.
|
|
Closes #5549.
|
|
e.g. ordered list item, in Markdown writer.
Closes #554.
|
|
depending on file extension of the image path
|
|
We need a better test that works cross-platform.
Until then, removing this.
Closes #5528.
|
|
The same text is already in the <figcaption> and
screen-readers would read it twice, see #4737
|
|
|
|
Move up the pattern match to be reachable, closes #5517.
Previously `file:/` URLs were handled wrongly and pandoc attempted
to make HTTP requests, which failed.
|
|
|
|
Previously too few backticks were used when the code block
contained an indented line of backticks. (Ditto tildes.)
Cloess #5519.
|
|
Previously if labels had integer names, it could produce a conflict
with auto-labeled reference links. Now we test for a conflict and find
the next available integer.
Note that this involves adding a new state variable `stPrevRefs` to
keep track of refs used in other document parts when using
`--reference-location=block|section`
Closes #5495
|
|
Emacs always uses two spaces when indenting the content of src blocks,
e.g., when exiting a `C-c '` edit-buffer. Pandoc used to indent contents
by the space-equivalent of one tab, but now always uses two spaces, too.
Closes: #5440
|
|
Regression! The fix for #4683 broke this case.
|
|
iOS chooses to render a number of Unicode entities,
including '↩', as big colorful emoji. This can be
defeated by appending Unicode
VARIATION SELECTOR-15'/'VARIATION SELECTOR-16'.
So we now append this character when escaping
strings, for both '↩' and '↔'.
If other characters prove problematic, they can
simply be added to needsVariationSelector.
Closes #5469.
|
|
Previously an Emph inside a Span was being treated as
nested markup and ignored. With this patch, the Span
is just ignored.
Closes #5446.
|
|
|
|
fixes #5416
|
|
These are upside down ? and !, resp.
Closes #5407.
|
|
For
::: {.cell}
---
:::
|
|
This fixes a bug wherein footnotes appeared in the wrong
order, and with duplicate numbers, when in table captions
and cells.
We now use regular `\footnote` commands, even in the table
caption and the minipages containing cells. Apparently
longtable knows how to handle this.
Closes #5367.
|
|
|