Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
All templates now include `code{white-space: pre-wrap}`
and CSS for `q` if `--html-q-tags` is used.
Previously some templates had `pre` and others `pre-wrap`;
the `q` styles were only sometimes included.
See #3485.
|
|
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.
|
|
|
|
Removed tools/refactor.sh.
|
|
|
|
|
|
|
|
This makes them easier to read.
|
|
See #3473.
|
|
|
|
|
|
|
|
|
|
Polyglot markup is HTML5 that is also valid XHTML. See
<https://www.w3.org/TR/html-polyglot>. With this change, pandoc's
html5 writer creates HTML that is both valid HTML5 and valid XHTML.
See jgm/pandoc-templates#237 for prior discussion.
* Add xml namespace to `<html>` element.
* Make all `<meta>` elements self closing.
See <https://www.w3.org/TR/html-polyglot/#empty-elements>.
* Add `xml:lang` attribute on `<html>` element, defaulting to blank, and
always include `lang` attribute, even when blank. See
<https://www.w3.org/TR/html-polyglot/#language-attributes>.
* Update test files for template changes.
The key justification for having language values default to blank: it
turns out the HTML5 spec requires it (as I read it). Under
[the HTML5 spec, section "3.2.5.3. The lang and xml:lang
attributes"](https://www.w3.org/TR/html/dom.html#the-lang-and-xmllang-attributes),
providing attributes with blank contents both:
* Has meaning, "unknown", and
* Is a MUST (written as "must") if a language value is not provided ...
> The lang attribute (in no namespace) specifies the primary language
> for the element's contents and for any of the element's attributes that
> contain text. Its value must be a valid BCP 47 language tag, or the
> empty string. Setting the attribute to the empty string indicates that
> the primary language is unknown.
In short, it seems that where a language value is not provided then a
blank value MUST be provided for Polyglot Markup conformance, because
the HTML5 spec stipulates a "must". So although the Polyglot Markup spec
is unclear on this issue it would seem that if it was correctly written,
it would therefore require blank attributes.
Further justifications are found at
https://github.com/jgm/pandoc-templates/issues/237#issuecomment-275584181
(but the HTML5 spec justification given above would seem to be the
clincher).
In addition to having lang-values-default-to-blank I recommend that, when an
author does not provide a lang value, then upon on pandoc command execution
a warning message like the following be provided:
> Polyglot markup stipulates that 'The root element SHOULD always specify
> the language'. It is therefore recommended you specify a language value in
> your source document. See
> <https://www.w3.org/International/articles/language-tags/> for valid
> language values.
|
|
|
|
Closes #2434.
|
|
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 #3476.
|
|
Instead, resize to 1.
Note, this (together with earlier changes to the Markdown
writer) seems to fix #1785.
The table renders as garbage, but pandoc now completes the conversion
quickly and doesn't get tied up.
|
|
|
|
Closes #1166.
|
|
Closes #2704 (formatting problems in beamer citations).
See
http://tex.stackexchange.com/questions/22852/function-and-usage-of-leavevmode
|
|
|
|
|
|
|
|
|
|
You might have a `|` character inside math.
(Or for that matter something that the parser might mistake
for raw HTML.)
See #3481.
|
|
Previously the hypertargets were only added when there was actually
a link to that identifier. Closes #2719.
|
|
|
|
|
|
Closes #2834.
|
|
|
|
|