Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
|
|
|
|
|
|
Closes #6483.
|
|
Closes: #6480
|
|
The value is stored in the `institute` metadata field and used in the
default beamer presentation template.
|
|
The behavior of the `#+AUTHOR` and `#+KEYWORD` export settings has
changed: Org now allows multiple such lines and adds a space between the
contents of each line. Pandoc now always parses these settings as meta
inlines; setting values are no longer treated as comma-separated lists.
Note that a Lua filter can be used to restore the previous behavior.
|
|
|
|
`#+DESCRIPTION` lines are treated as text with markup. If multiple such
lines are given, then all lines are read and separated by soft
linebreaks.
Closes: #6485
|
|
The `tex` export option can be set with `#+OPTION: tex:nil` and allows
three settings:
- `t` causes LaTeX fragments to be parsed as TeX or added as raw TeX,
- `nil` removes all LaTeX fragments from the document, and
- `verbatim` treats LaTeX as text.
The default is `t`.
Closes: #4070
|
|
|
|
We'll need this to store table attributes until all writers
are adjusted to react to attributes on the Table element.
|
|
This fixes #6481, allowing grid tables to be enclosed
in fenced divs with no intervening blank lines.
|
|
(Instead of old Span with underline class.
Spans with `underline` will no longer be rendered
as underlined text.)
|
|
|
|
wkhtmltopdf changed in recent versions to require this for
access to local files.
This fixes PDF via HTML5 with `--css`.
Closes #6474.
|
|
Fixes: #6472
|
|
Closes #6460.
|
|
Exceptions: name (which becomes the id), class (which becomes the
classes), and number-lines (which is treated specially to fit
with pandoc highlighting).
Closes #6465.
|
|
Per the EPUB 3.2 spec, "application/x-font-truetype" is no longer a
valid identifier for TrueType (.ttf) fonts [1]. This fixes warnings when
validating pandoc-generated EPUBs using `epubcheck` [2].
References [3].
[1]: https://www.w3.org/publishing/epub3/epub-spec.html#sec-core-media-types
[2]: https://github.com/w3c/epubcheck
|
|
A `<procedure>` contains a sequence of `<step>`'s, or `<substeps>`
that themselves contain `<step>`'s.
|
|
A `<phrase>` has no semantic meaning. It is only useful to hang an
`id` or other attributes around a piece of text.
|
|
|
|
A `<replaceable>` is a placeholder that a user is instructed to
replace with a value of their own, like
`<replaceable>prefix</replacable>/bin/foo`. In the standard Docbook
toolchain, this typically appears emphasized, and no other adornement.
But a `<replaceable>` is nearly always in a code element, where
emphasis won't work. So we do the same thing as for `<optional>`:
decorate the content with brackets.
|
|
A <simplesect> is a section like any other, except that it never
contains an subsection, and is typically rendered unnumbered.
|