Age | Commit message (Collapse) | Author | Files | Lines |
|
* Org reader: allow the `-i` switch to ignore leading spaces.
* Org reader: handle awkwardly-aligned code blocks within lists.
Code blocks in Org lists must have their #+BEGIN_ aligned in a
reasonable way, but their other components can be positioned otherwise.
|
|
|
|
|
|
|
|
|
|
We now allow groups where the closing `\\}` isn't at the
beginning of a line.
Closes #5410.
|
|
When the `raw_tex` extension is set, we just carry through
`\usepackage`, `\input`, etc. verbatim as raw LaTeX.
Closes #5673.
|
|
Closes #5682.
|
|
Closes #5711.
|
|
Closes #5714.
|
|
Now that it is polymorphic, this is possible, and it's a
better choice because it resets last string pos.
|
|
* T.P.Parsing: Change type of `setLastStrPos` so it takes a
`Maybe SourcePos` rather than a `SourcePos`. [API change]
* T.P.Parsing: Make `parseFromString'` and `gridTableWith` and
`gridTableWith'` polymorphic in the parser state, constraining it with
`HasLastStrPosition`. [API change]
Closes #5708.
|
|
This puts RST reader into alignment with docbook reader.
|
|
Fixes #1234.
This parses admonitions not as a blockquote, but rather as a div with an
appropriate class. We also handle titles for admonitions as a nested div
with the "title" class.
(I followed the behaviour of other docbook-to-html converters in this -
there are clearly other ways you could encode it.)
In general, the handling of elements with nested title elements is very
inconsistent. I think we should make it consistent, but I'm leaivng that
for later to make this a small change.
Example:
```docbook
<warning xml:id="someId">
<title>My title</title>
<simpara>An admonition block</simpara>
</warning>
```
goes to
```html
<div id="someId" class="warning">
<div class="title">My title</div>
<p>An admonition block</p>
</div>
```
|
|
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!
|
|
|
|
According to https://github.com/jgm/pandoc/issues/4725#issuecomment-399772217 not only the `lilypond` environment but also `ly` should be included in the verbatim list.
@jperon
https://github.com/jperon/lyluatex/issues/203
|
|
Closes #5659.
|
|
Closes #5654.
|
|
Attributes for LaTeX output are accepted as valid block attributes;
however, their values are ignored.
Fixes: #5648
|
|
like latex does, if an extension is not provided.
Closes #4933.
|
|
Closes #4442.
|
|
Closes #4439.
|
|
Closes #5551
|
|
When `+raw_tex` is enabled, these are passed through literally.
Otherwise, they are handled in a way that emulates LaTeX's behavior.
|
|
Add support for EPUB2 covers (fix #3992)
|
|
Improve the parsing of frames in ODT documents
|
|
They are now ignored if the corresponding command or environment
is already defined.
Closes #5635.
|
|
Closes #5619.
|
|
Closes #5627.
|
|
|
|
Closes #3523.
|
|
|
|
|
|
|
|
|
|
Sometimes custom elements are used, and the reader should
not abort but skip them with a warning. (For example,
id element in author.)
Closes #5560.
|
|
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.
|
|
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 #5545.
|
|
Closes #5549.
|
|
- With epub extensions, check for epub:type in addition to type.
- Fix problem with noteref parsing which caused block-level
content to be eaten with the noteref.
- Rename pAnyTag to pAny.
- Refactor note resolution.
|
|
add `onlySimpleTableCells` to `Text.Pandoc.Shared`
[API change]
This fixes an inconsistency in the HTML reader, which did not treat tables with `<p>` inside cells as simple.
|
|
|
|
|
|
Planning info is now always placed before the subtree contents.
Previously, the planning info was placed after the content if the
header's subtree was converted to a list, which happens with headers of
level 3 and higher per default.
Fixes: #5494
|
|
Unknown export options are properly ignored and omitted from the output.
|
|
Closes #5493
|
|
|
|
|