Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This allows groups of theorem environments to be
put in the same numbering sequence.
|
|
|
|
Includes numbering and labels and refs.
Note that numbering support is not complete; we don't
reset numbers with sections for example.
|
|
|
|
|
|
Closes #1413.
|
|
Closes #6549.
|
|
We need to reduce the size of the LaTeX reader to ease
compilation on resource-limited systems. More can be done
in this vein.
|
|
Otherwise unsmartify doesn't catch quotes that have
already been turned to entities.
|
|
Instead rely on the markdown writer with appropriate extensions.
Export writeCommonMark variant from Markdown writer.
This changes a few small things in rendering markdown,
e.g. w/r/t requiring backslashes before spaces inside
super/subscripts.
|
|
when possible if the superscript or subscript extension or
raw_html aren't available.
|
|
when `Ext_table_caption` not enabled.
|
|
commonmark with a number of useful extensions (more than gfm).
|
|
Previously it included all of the following, which make
sense for the legacy markdown_github but not for gfm,
since they are part of base commonmark and thus
can't be turned off in gfm:
- `Ext_all_symbols_escapable`
- `Ext_backtick_code_blocks`
- `Ext_fenced_code_blocks`
- `Ext_space_in_atx_header`
- `Ext_intraword_underscores`
- `Ext_lists_without_preceding_blankline`
- `Ext_shortcut_reference_links`
`
These have been removed from `githubMarkdownExtensions`, though
they're still turned on for legacy `markdown_github`.
|
|
This allows attributes to be added to any block or inline
element, in principle. (Though in many cases this will be
done by adding a Div or Span container, since pandoc's
AST doesn't have a slot for attributes for most elements.)
Currently this is only possible with the commonmark and gfm
readers.
Add `Ext_attributes` constructor for `Extension` [API change].
|
|
...instead of cmark-gfm (a wrapper around a C library).
We can now support many more pandoc extensions for
commonmark and gfm.
Add fenced_code_attributes to gfm/commonmark extensions.
|
|
HTML writer: improve alt-text/caption handling for HTML5
|
|
Closes #6542.
Note that you'll need to put releaseinfo somewhere in your
template if you want this to be part of the converted output.
|
|
Fixes #6529
|
|
suggesting that releaseinfo is handled. It isn't.
|
|
[Docx Reader] Only use bCs/iCs on runs with rtl or cs property
|
|
Fixes #6514
|
|
Escape starting periods in ms writer code blocks
|
|
[Docx Reader] Refactor/update Text.Pandoc.Readers.Docx.Combine.smushInlines
|
|
Previously blank lines were simply omitted from highligted code.
|
|
|
|
|
|
If a line of ms code block output starts with a period (.), it should
be prepended by '\&' so that it is not interpreted as a roff command.
Fixes #6505
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit efbc2050315b60c8a753dee6255465f1083019ab.
|
|
This reverts commit 2d009366cef2358ec2c99612ae2c73068841306c.
|
|
See #5408.
|
|
Screen readers read an image's `alt` attribute and the figure caption,
both of which come from the same source in pandoc. The figure caption is
hidden from screen readers with the `aria-hidden` attribute. This
improves accessibility.
For HTML4, where `aria-hidden` is not allowed, pandoc still uses an
empty `alt` attribute to avoid duplicate contents.
Closes: #6491
|
|
Tables can be removed from the final document with the `#+OPTION:
|:nil` export setting.
|
|
Footnotes can be removed from the final document with the `#+OPTION:
f:nil` export setting.
|
|
The reader now parses the contents of the markdown cell to a Pandoc
structure, but *also* stores the raw markdown in a `source`
attribute on the cell Div. When we convert back to markdown,
this attribute is stripped off and the original source is used.
When we convert to other formats, the attribute is usually
ignored (though it will come through in HTML as a `data-source`
attribute, not unhelpfully).
I'll note some potential drawbacks of this approach:
- It makes it impossible to use pandoc to clean up or
change the contents of markdown cells, e.g.
going from `+smart` to `-smart`.
- There may be formats where the addition of the `source`
attribute is problematic. I can't think of any, though.
Closes #5408.
|
|
MathML-like entities, e.g., `\alpha`, can be disabled with the
`#+OPTION: e:nil` export setting.
|
|
Unify defaults metadata and markdown metadata parsers
|
|
The lines of unknown keywords, like `#+SOMEWORD: value` are no longer
read as metadata, but kept as raw `org` blocks. This ensures that more
information is retained when round-tripping org-mode files;
additionally, this change makes it possible to support non-standard org
extensions via filters.
|
|
Handling of export settings and other keywords (like `#+LINK`) has been
combined and unified.
|
|
These export settings are treated like their non-extra counterparts,
i.e., the values are added to the `header-includes` metadata list.
|
|
The values of all lines are read as inlines and collected in the
`subtitle` metadata field.
|
|
|
|
|
|
|