Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This was somehow missed in 884aef31c55e375cd62fcb55a71829d005087cae.
|
|
Add all titling commands to existing definition for `\dedication`.
|
|
PR #5884.
+ Use pandoc-types 1.20 and texmath 0.12.
+ Text is now used instead of String, with a few exceptions.
+ In the MediaBag module, some of the types using Strings
were switched to use FilePath instead (not Text).
+ In the Parsing module, new parsers `manyChar`, `many1Char`,
`manyTillChar`, `many1TillChar`, `many1Till`, `manyUntil`,
`mantyUntilChar` have been added: these are like their
unsuffixed counterparts but pack some or all of their output.
+ `glob` in Text.Pandoc.Class still takes String since it seems
to be intended as an interface to Glob, which uses strings.
It seems to be used only once in the package, in the EPUB writer,
so that is not hard to change.
|
|
...to ensure that space is left between a control seq and
a following word that would otherwise change its meaning.
Closes #5836.
|
|
Closes #5836.
|
|
These were formerly omitted (though they still affected macro
resolution if `latex_macros` was set). Now they are included in
the document.
|
|
when `latex_macros` is disabled. (When `latex_macros` is enabled,
we omit them, since pandoc is applying the macros itself.)
Previously, it was documented that the macro definitions got
passed through as raw latex regardless of whether `latex_macros`
was set -- but in fact they never got passed through.
|
|
We were using `grouped blocks` instead of `grouped block`.
This caused the reader to hang in an infinite loop
(with a memory leak) on e.g. `\parbox{1em}{#1}`.
Closes #5845.
|
|
This allows us to avoid retokenizing multiple times in
e.g. rawLaTeXBlock. (Unexported module, so not an API change.)
|
|
|
|
This allows it to be processed by filters, in the same way that
one can do for 'tikzpicture'
|
|
When the `raw_tex` extension is set, we just carry through
`\usepackage`, `\input`, etc. verbatim as raw LaTeX.
Closes #5673.
|
|
Closes #5682.
|
|
Closes #5711.
|
|
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.
|
|
like latex does, if an extension is not provided.
Closes #4933.
|
|
When `+raw_tex` is enabled, these are passed through literally.
Otherwise, they are handled in a way that emulates LaTeX's behavior.
|
|
They are now ignored if the corresponding command or environment
is already defined.
Closes #5635.
|
|
|
|
Closes #3523.
|
|
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.
|
|
|
|
These seem to be needed for xelatex but not pdflatex.
Closes #5441.
|
|
These are parsed as a Span with class `underline`, as with other readers.
|
|
|
|
The haddock module header contains essentially the
same information, so the boilerplate is redundant and
just one more thing to get out of sync.
|
|
Quite a few modules were missing copyright notices.
This commit adds copyright notices everywhere via haddock module
headers. The old license boilerplate comment is redundant with this and has
been removed.
Update copyright years to 2019.
Closes #4592.
|
|
|
|
Previously the `.0` was interpreted as a file extension,
leading pandoc not to add `.tex` (and thus not to find the
file).
The new behavior matches tex more closely.
|
|
|
|
* These were added by the RST reader and, for literate Haskell,
by the Markdown and LaTeX readers. There is no point to
this class, and it is not applied consistently by all readers.
See #5047.
* Reverse order of `literate` and `haskell` classes on code blocks
when parsing literate Haskell. Better if `haskell` comes first.
|
|
Closes #5149.
|
|
|
|
|
|
Allow decimal points, preceding space.
Also require text 1.1+.
|
|
|
|
|
|
|
|
Parse as raw, but know that these font changing commands
take no arguments.
|
|
Closes #5010.
Expose trimMath from T.P.Shared.
|
|
|
|
|
|
|
|
rather than after. This has some performance penalty
but is more reliable.
Closes #4408.
|
|
This solves some of the issues in #4408, but it is fragile and may
introduce new problems. We really need to change the approach
fundamentally and expand macros before pulling tokens from the stream,
rather than after.
|
|
for macros
|