Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes #1905.
Removed stateChapters from ParserState.
Now we parse chapters as level 0 headers, and parts as level -1 headers.
After parsing, we check for the lowest header level, and if it's
less than 1 we bump everything up so that 1 is the lowest header level.
So `\part` will always produce a header; no command-line options
are needed.
|
|
|
|
This allows us to display error information returned by the
skylighting library.
Display a warning if the highlighting library throws an error.
|
|
Also added identifiers on `<div>` elements. These were commented
out before, not sure why?
|
|
The values of the following meta variables are now interpreted using
org-markup instead of treating them as pure strings:
- *keywords*: comma-separated list of inlines
- *subtitle*: inline values
- *nocite*: inline values; using it multiple times accumulates the
values.
|
|
|
|
|
|
As noted in the previous commit, an autogenerated identifier
may still coincide with an explicit identifier that is given
for a header later in the document, or with an identifier on
a div, span, link, or image. This commit adds a warning
in this case, so users can supply an explicit identifier.
* Added `DuplicateIdentifier` to LogMessage.
* Modified HTML, Org, MediaWiki readers so their custom
state type is an instance of HasLogMessages. This is necessary
for `registerHeader` to issue warnings.
See #1745.
|
|
Previously only autogenerated ids were added to the list
of header identifiers in state, so explicit ids weren't taken
into account when generating unique identifiers. Duplicated
identifiers could result.
This simple fix ensures that explicitly given identifiers are
also taken into account.
Fixes #1745.
Note some limitations, however. An autogenerated identifier
may still coincide with an explicit identifier that is given
for a header later in the document, or with an identifier on
a div, span, link, or image. Fixing this would be much more
difficult, because we need to run `registerHeader` before
we have the complete parse tree (so we can't get a complete
list of identifiers from the document by walking the tree).
However, it might be worth issuing warnings for duplicate
header identifiers; I think we can do that. It is not
common for headers to have the same text, and the issue
can always be worked around by adding explicit identifiers,
if the user is aware of it.
|
|
This reverts commit 0ef1e51211cd35b1ddb54a5fe8bee4247f1e1801.
|
|
This will be used to help with #1745.
|
|
* Previously we got overlong lists with `--wrap=none`. This is fixed.
* Previously a multiline list could become a simple list (and would
always become one with `--wrap=none`).
Closes #3384.
|
|
Makes the benchmark go from 40 to 36 ms.
|
|
|
|
Rewrote functions in RST reader and writer to avoid the need
for it.
Closes #1530.
|
|
Replacing trimLineBreaks. This does the work of
normalizeSpaces as well, so we avoid the need for that
function here.
See #1530.
|
|
...not just spaces.
|
|
* Add Muse writer
* Advertise new Muse writer
* Muse writer: add regressions tests
|
|
This is newly exported in texmath 0.9.3.
Note that this means that `macro` will now parse one
macro at a time, rather than parsing a whole group together.
|
|
Closes #987.
Depends on still unreleased texmath 0.9.3.
|
|
Closes #2115.
|
|
|
|
Closes #3486.
|
|
|
|
|
|
Otherwise we get invalid RST. There seems to be no
way to escape the space.
Closes #3496.
|
|
Fixes: #3499
|
|
after tables and list, for example.
|
|
Closes #3487.
|
|
Closes #3499.
|
|
to avoid false interpretation as a list.
Also handle `|`, and refactor code for escaping `%`.
Closes #3497.
|
|
Closes #3495.
|
|
when they occur without space surrounding them.
E.g. equation, math.
This avoids incorrect vertical space around equations.
Closes #3309.
Closes #2171.
See also rstudio/bookdown#358.
|
|
E.g. an HTML table with two cells in the first row and one
in the second (but no row/colspan).
We now calculate the number of columns based on the longest
row (or the length of aligns or widths).
Closes #3337.
|
|
as well as block contexts.
Closes #3494.
|
|
Now we properly escape things that would otherwise start ordered
lists, such as
---
title: 1. inline
...
Closes #3492.
Closes #1685.
|
|
where XX = rm, tt, up, md, sf, bf.
Spans with a class are used when there is nothing better.
Closes #3488.
|
|
Closes #2397.
This patch also adds `shortcut_reference_links` to the list
of mmd extensions.
|
|
...if the `pandoc_title_blocks` extension is enabled.
Otherwise in a document starting with a literal percent sign
the first line is wrongly interpreted as a title.
Closes #3454.
|
|
|
|
|
|
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.
|
|
|
|
Rather than using a style attribute directly.
This gives the user more flexibility in styling small caps
in CSS.
See #1592.
|
|
See #1592.
|
|
Instead of a style attribute as before.
See #1592.
|
|
This allows users to specify small caps in Markdown this way:
[my text]{.smallcaps}
See #1592.
|