Age | Commit message (Collapse) | Author | Files | Lines |
|
Otherwise things like `\noindent foo` break and turn into
`\noindentfoo`.
Affects `-f latex+raw_tex` and `-f markdown` (and other formats
that allow `raw_tex`).
Closes #1773.
|
|
`imageSize img` is now `imageSize opts img`
|
|
|
|
Including when they're in tables or other list items.
Closes #2606.
|
|
Closes #2652.
|
|
This allows display math to be rendered properly.
Closes #3452.
|
|
Closes #2649.
|
|
See #2649.
|
|
I didn't see this documented anywhere, but it seems to be allowed
(and common).
See #2649. This addresses some of the cases there, but not all.
|
|
Now 'r' gets you `<source>` rather than `<code>` (among others).
Closes #3461.
|
|
* In HTML writer, with reveal.js we use data-src instead of src
for images.
* In SelfContained, we also load resources from data-src.
Closes #2283.
|
|
|
|
We constrain it to the state used in the HTML reader.
Otherwise we can get overlap with the general instance
for ParserState m.
|
|
This reverts commit 3c427fc17d53a564305aadde015dd2f048d9ff71.
|
|
in hopes that this will help the ghc 7.8.4 build...
|
|
|
|
|
|
|
|
|
|
|
|
See #3447. To complete fixes on this issue, we need to
do the same for the other readers. Note that the changes
required are minimal -- add reportLogMessages to the end
of the main parser, and replace report with logMessage.
(except for trace)
|
|
We need to do logging by updating parser state, or we'll get
inappropriate and repeated log messages when there is parser
backtracking.
See #3447.
|
|
|
|
|
|
because ZimWiki does not support it (#3446)
|
|
|
|
|
|
|
|
For example, in
\begin{tabular}{>{$}l<{$}>{$}l<{$} >{$}l<{$}}
each cell will be interpreted as if it has a `$`
before its content and a `$` after (math mode).
|
|
Links with # are perfectly valid according to http://orgmode.org/manual/Internal-links.html#Internal-links
|
|
|
|
This is deprecated but may still be in older documents.
|
|
Currently the support for the `.. table` directive is a bit
limited; we don't yet support the `widths` field. But at least
you can have a proper captioned table.
|
|
This allows adding captions to tables.
|
|
See #3432. Previously the parser didn't handle properly this
case:
* - a
- b
* - c
- d
|
|
Use a deterministic order for fields.
|
|
See #3392.
|
|
Verbosity level only affects which are printed to stdout.
(Exception: DEBUG messages are only printed, never saved to
state.)
|
|
|
|
|
|
This gives us the possibility of both machine-readable
and human-readable output for log messages.
See #3392.
|
|
This now contains the Verbosity definition previously
in Options, as well as a new LogMessage datatype that
will eventually be used instead of raw strings for
warnings.
This will enable us, among other things, to provide
machine-readable warnings if desired.
See #3392.
|
|
|
|
|
|
See #3392.
|
|
See #3392.
|
|
This was not actually being used. Since it adds considerable
complexity, it's best not to include it unless we are
actually going to use it.
The original thought was that we could do all loading in the
readers, always deferred and thus costless. This was supposed
to eliminate the need to traverse trees loading resources in
the docx, epub, odt writers and in PDF and SelfContained.
(It would also have the side effect that --extract-media could
be used with all input formats. This wasn't an intended side
effect, and it could be debated whether it's desirable, since
--extract-media was originally designed to extract the media
contained in a docx or odt or epub container.)
However, we never actually took the step of moving all of this
work to the readers, for a couple of reasons. The main reason
is that we'd still need to fetch resources in the docx,
epub, odt, pdf and self-contained writers, since the Pandoc AST might
have been built programatically and hence not generated by a reader.
So it's not clear that doing lazy loading in the readers would have
any real advantage.
I'm still not completely sure about this --- if we change our
minds it would be easy to undo this commit.
@jkr comments welcome.
|
|
Closes #2116.
|
|
* We no longer add an "admonition" class, we just use the
class for the type of admonition, "note" for example.
* We put the word corresponding to the label in a paragraph
inside a div at the beginning of the admonition with class
"admonition-title".
* This is about as close as we can get to RST's own output.
See #223.
|
|
* Export readFileFromDirs from Class.
* Export insertIncludedFile from Parsing.
Simplified code in LaTeX/RST readers.
|