| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Closes #7276. Note: currently we still get unwanted
white space around the minus; this needs to be addressed
with a change in texmath.
|
|
Closes #7266.
|
|
Closes #7273.
|
|
The settings we can carry over from a reference.docx are
autoHyphenation, consecutiveHyphenLimit, hyphenationZone,
doNotHyphenateCap, evenAndOddHeaders, and proofState.
Previously this was implemented in a buggy way, so that the
reference doc's values AND the new values were included.
This change allows users to create a reference.docx that
sets w:proofState for spelling or grammar to "dirty,"
so that spell/grammar checking will be triggered on the
generated docx.
Closes #1209.
|
|
for Content, Element, Attr, CDataKind.
[API change]
|
|
Now we also handle the case where they're embedded in other
elements, e.g. spans. Closes #7272.
|
|
The epub writer previously used the same XML id for both the book
identifier and the epub collection. This causes an error on epubcheck.
|
|
This should make svgnames and x11names work properly.
Closes #6109.
|
|
See failure at https://github.com/jgm/pandoc/runs/2541449722
|
|
...of the file containing the include directive, as
RST requires.
Closes #6632.
|
|
...the directory containing the file containing the
INCLUDE directive. Closes #5501.
|
|
|
|
instead of reproducing much of its code.
|
|
Remove old `insertIncludedFileF`. [API change]
Give `insertIncludedFile` a more general type, allowing it
to be used where `insertIncludedFileF` was.
|
|
Previously, when multiple file arguments were provided, pandoc
simply concatenated them and passed the contents to the readers,
which took a Text argument.
As a result, the readers had no way of knowing which file
was the source of any particular bit of text. This meant that
we couldn't report accurate source positions on errors or
include accurate source positions as attributes in the AST.
More seriously, it meant that we couldn't resolve resource
paths relative to the files containing them
(see e.g. #5501, #6632, #6384, #3752).
Add Text.Pandoc.Sources (exported module), with a `Sources` type
and a `ToSources` class. A `Sources` wraps a list of `(SourcePos,
Text)` pairs. [API change] A parsec `Stream` instance is provided for
`Sources`. The module also exports versions of parsec's `satisfy` and
other Char parsers that track source positions accurately from a
`Sources` stream (or any instance of the new `UpdateSourcePos` class).
Text.Pandoc.Parsing now exports these modified Char parsers instead of
the ones parsec provides. Modified parsers to use a `Sources` as stream
[API change].
The readers that previously took a `Text` argument have been
modified to take any instance of `ToSources`. So, they may still
be used with a `Text`, but they can also be used with a `Sources`
object.
In Text.Pandoc.Error, modified the constructor PandocParsecError
to take a `Sources` rather than a `Text` as first argument,
so parse error locations can be accurately reported.
T.P.Error: showPos, do not print "-" as source name.
|
|
Fixes: #6564
Thanks to @denismaier.
|
|
Tabs in plain-text inputs are now handled correctly, even if the
`--file-scope` flag is used.
Closes: #6709
|
|
See: #6315
|
|
|
|
|
|
Closes #7252
As specified in https://orgmode.org/manual/LaTeX-fragments.html, an
inline \begin{}...\end{} LaTeX block must start on a new line.
|
|
Closes: #6865
|
|
* Support toc-title in revealjs
* Add semantic HTML "nav" tag
Closes #7170.
As with default.html5
|
|
Fix bad vertical spacing after the bibliography.
|
|
They represent images, the same way as other images in vml format.
|
|
Improves heuristic for detection of an "open double quote."
Closes #2103.
|
|
Treat a leading " with no closing " as a left curly quote.
This supports the practice, in fiction, of continuing
paragraphs quoting the same speaker without an end quote.
It also helps with quotes that break over lines in line
blocks.
Closes #7216.
|
|
|
|
If the element has a content-type attribute, or at least one class, then
that value is used as `content-type` and the span is put inside a
`<named-content>` element. Otherwise a `<styled-content>` element is
used instead.
Closes: #7211
|
|
|
|
|
|
Since it seem to be a common source of confusion, this commit adds a note in
org-mode documentation referring users to consult org-mode's export
documentation when they find themselves in a pinch.
|
|
|
|
|
|
|
|
Also taking this opportunity to note, for the record, that
the commit for #7241 should be marked [API change].
It changes the type of `languagesByExtension` in Highlighting,
adding a parameter for a `SyntaxMap`.
|
|
Languages defined using `--syntax-definition` were not recognized by `languagesByExtension`.
This patch corrects that, allowing the writers to see all custom definitions.
The LaTeX still uses the default syntax map, but that's okay in that context, since
`--syntax-definition` won't create new listings styles.
|
|
When a block only has a single class and no other attributes,
it is not necessary to wrap the class attribute in curly braces –
the class name can be placed after the opening mark as is.
This will result in bit cleaner output when pandoc is used
as a markdown pretty-printer.
|
|
This fixes a bug, which caused the writer to look at the LAST
rather than the FIRST character in determining whether quotes
were needed. So we got spurious quotes in some cases and
didn't get necessary quotes in others.
Closes #7245. Updated a number of test cases accordingly.
|
|
It is basically the same as biblaetx-quotes.md.
|
|
|
|
|
|
|
|
|
|
Previously we exited with an error status but (due to a bug)
no message.
Closes #7231.
|
|
This gives better results in converting to e.g. pandoc markdown.
Ref: <https://groups.google.com/d/msgid/pandoc-discuss/9728d1f4-040e-4392-aa04-148f648a8dfdn%40googlegroups.com>
|
|
|
|
|
|
|
