| Age | Commit message (Collapse) | Author |
|---|
|
Update the test so it reflects the right output, and fix the
solution.
Really closes #11006.
|
|
These require an additional blank line in some cases.
Closes #11006.
|
|
[API change]
This will prevent unnecessary conversion of units.
Closes #8957.
|
|
Previously fenced divs were not used in this case, causing the writer to fall back to raw HTML.
Closes #10955.
|
|
Org doesn't reliable display these as links if they have hard breaks.
Closes #9000.
|
|
This solves the problem of unwanted capitalization of names
at the beginning of citations in footnotes.
Closes #10983.
|
|
|
|
Closes #10983 by allowing `nocase` spans to be used to suppress
capitalization of initial word in a footnote.
|
|
Closes #10984.
|
|
Previously, the first line of a definition details item always used a
colon and three spaces instead of respecting the tab-stop setting, which
could lead to round-tripping issues.
Likewise, the indentation of continuation paragraphs in definition lists
now matches the two-characters leader of the first line for Markua
output.
Fixes: #10890
|
|
|
|
It was meant to test subsequent author substitution, but the
new chicago-author-date doesn't do this. So we use a different CSL.
|
|
When we updated to the latest chicago-author-date.csl, this test
no longer tested what it was supposed to; so we use a different csl.
|
|
from the latest chicago-author-date.csl. (Note that this goes
from the 17th to the 18th edition.)
Update tests.
|
|
Closes #10965.
|
|
Omit the wrapper sourceCode divs added by pandoc around code blocks.
More intelligently identify which class to use for the one class
allowed in GFM code blocks. If there is a class of form `language-X`,
use `X`; otherwise use the first class other than `sourceCode`.
Closes #10926.
|
|
on ordered lists. Closes #10912.
|
|
Closes #10915
|
|
Closes #7691.
|
|
If the `four_space_rule` extension is not enabled,
figure out the indentation needed for child blocks dynamically,
by looking at the first nonspace content after the `:` marker.
Previously the four-space rule was always obeyed.
Remove the old `compact_definition_lists` extension. This was
neded to preserve backwards compatibility after pandoc 1.12
was released, but at this point we can get rid of it.
T.P.Extensions: remove `Ext_compact_definition_lists` constructor
for `Extension` [API change].
Fix tight/loose detection for definition lists, to conform to
the documentation.
Closes #10889.
|
|
Fix headings with colspans. If the heading contains a colspan, we still
need to include information in the header line about the colspecs.
Fix headerless tables. The top line should encode colspan information.
Closes #10855.
|
|
In commit 9190b19fc, we began to use the ID prefix for the <aside>
holding the footnotes. In commit 41da8ad9e, we started to use a
<section> for this instead and the ID-prefix functionality was lost.
This commit resumes using the ID prefix in the ID of this element so
that multiple documents can be combined into one without ID conflicts.
|
|
0d2114e introduced a bug where Markdown writer would ignore attributes
on the figure if it has class or key-value attributes set.
This commit fixes that and adds a regression test.
Closes #10867
|
|
Closes #6095.
|
|
Previously in this case the closing tag was dropped.
Closes #10862.
|
|
See #10848.
|
|
Closes #10848.
|
|
See #10848.
|
|
|
|
|
|
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`.
|
|
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.
|
|
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 #10781.
|
|
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.
|
|
Convert newlines to spaces as we do in other formats.
Closes #10730.
|
|
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.
|
|
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.
|
|
|
|
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.
|
|
It should not accept escaped newlines.
See #10672.
|
|
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.
|
