Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes #2397.
This patch also adds `shortcut_reference_links` to the list
of mmd extensions.
|
|
|
|
|
|
Markdown reader now consults this to determine what is an
abbreviation.
Eventually it will be possible to specify a custom list
(see #256).
|
|
When multiple YAML metadata blocks are used, and two define
the same field, the value defined first takes precedence,
according to the manual. This was changed briefly in
ba3ee62323644134f2a5dd3277e3349d3681111a. This commit
reverts to the original behavior and adds a test case.
|
|
defined in the body of the document.
Closes #1279.
|
|
Added test cases.
Fixed HTML reader to parse a span with class "smallcaps" as
SmallCaps.
Fixed Markdown writer to render SmallCaps as a native span
when native spans are enabled.
|
|
This allows users to specify small caps in Markdown this way:
[my text]{.smallcaps}
See #1592.
|
|
|
|
The citations appear at the end of the document as a definition
list in a special div with id `citations`.
Citations link to the definitions.
Added stateCitations to ParserState.
Closes #853.
|
|
Closes #1166.
|
|
You might have a `|` character inside math.
(Or for that matter something that the parser might mistake
for raw HTML.)
See #3481.
|
|
|
|
Cloess #3475.
|
|
It now adds a `dedication` field to metadata.
It is up to the user to supply a template that uses this
variable.
Closes #1845.
|
|
|
|
Closes #2662.
|
|
Previously we would refuse to parse anything as raw inline if
it was in the blockCommands list. Now we allow exceptions
if they're listed under ignoreInlines in inlineCommands.
This should make it easier e.g. to include an \hspace
between two side-by-side raw LaTeX tables.
|
|
This reverts commit 2873cd82886d1fa557bf3abde37b5ceb3cadf40c.
|
|
Closes #736.
|
|
This all works behind the scenes in CommonState plumbing.
|
|
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.
|
|
Including when they're in tables or other list items.
Closes #2606.
|
|
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.
|
|
We constrain it to the state used in the HTML reader.
Otherwise we can get overlap with the general instance
for ParserState m.
|
|
|
|
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)
|
|
|
|
|
|
|
|
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).
|
|
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
|
|
|
|
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.
|
|
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.
|
|
This can be used in several different modules, not just
LaTeX reader.
|
|
|
|
These were confusing.
Now we rely on the +raw_tex or +raw_html extension with latex
or html input.
Thus, instead of
--parse-raw -f latex
we use
-f latex+raw_tex
and instead of
--parse-raw -f html
we use
-f html+raw_html
|
|
Previously we didn't recognize math, for example, when
the xmlns declaration occured on the element and not the root.
Now we recognize either.
Closes #3365.
This patch defines findChildByName, findChildrenByName,
and findAttrByName in Util, and uses these in Parse.
|