Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
|
|
closes #3239
|
|
Cloess #3475.
|
|
* Removed writerEpubStylesheet in WriterOptions.
* Removed `--epub-stylesheet` option.
* Allow `--css` to be used with epub.
* Allow multiple stylesheets to be used.
* Stylesheets will be taken both from `--css` and from
the `stylesheet` metadata field (which can contain either
a file path or a list of them).
Closes #3472, #847.
|
|
It now adds a `dedication` field to metadata.
It is up to the user to supply a template that uses this
variable.
Closes #1845.
|
|
Direct users to open issues in jgm/pandoc, not jgm/pandoc-templates.
|
|
|
|
|
|
|
|
|
|
|
|
Closes #2662.
|
|
|
|
You can leave an external link as it is by adding the attribute
data-external="1" to the element. Pandoc will then not try to
incorporate its content when `--self-contained` is used. This is
similar to a feature already supported by the EPUB writer.
Closes #2656.
|
|
Introduced by 9d91b8825f6338e415eceb1163bba95d3178a49a.
|
|
|
|
|
|
|
|
|
|
|
|
Previously variables set on the command line were included in
e.g. YAML metadata, contrary to documentation and intentions.
|
|
It was previously not allowing multiple values to become lists.
|
|
Closes #3431.
|
|
This allows us to add the variables AFTER using the metadata
to generate a YAML header (in the Markdown writer).
Addresses the problem shown by
https://travis-ci.org/jgm/pandoc/jobs/205154181#L705
See #3439
|
|
Now we handle metadata first, then variables.
This way, meta-json variable will not contain representations of
variables, only proper metadata.
|
|
Issues info messages for non-rendered raw content.
|