Age | Commit message (Collapse) | Author | Files | Lines |
|
Table width in relation to text width is not natively supported
by docbook but is by the docbook fo stylesheets through an XML
processing instruction, <?dbfo table-width="50%"?> .
Implement support for this instruction in the DocBook reader.
|
|
in cases where we run into trouble parsing inlines til the
closing `]`, e.g. quotes, we return a plain string with the
option contents. Previously we mistakenly included the brackets
in this string.
Closes #6869.
|
|
Closes: #6687
|
|
`commonmark_x` never actually supported `auto_identifiers` (it
didn't do anything), because the underlying library implements
gfm-style identifiers only.
Attempts to add the `autolink_identifiers` extension to
`commonmark` will now fail with an error.
Closes #6863.
|
|
|
|
|
|
|
|
Put quotes around `controlsLayout`, `controlsBackArrows`,
and `display`, since these require strings.
Add `showSlideNumber`, `hashOneBasedIndex`, `pause`.
|
|
Previously we only self-contained attributes for
certain tag names (`img`, `embed`, `video`, `input`, `audio`,
`source`, `track`, `section`). Now we self-contain any
occurrence of `src`, `data-src`, `poster`, or `data-background-image`,
on any tag; and also `href` on `link` tags.
Closes #6854 (which specifically asked about
`asciinema-player` tags).
|
|
Closes #6857.
|
|
...and put it in a div with class `formalpara-title`, so that
people can reformat with filters.
Closes #6562.
Thanks to rdmuller.
|
|
This should fix spacing problems between entries
with numeric styles.
|
|
|
|
We now better handle `.IP` when it is used with non-bullet,
non-numbered lists, creating a definition list.
We also skip blank lines like groff itself.
Closes #6858.
|
|
This isn't really necessary and can be misleading
(e.g. on macOS, where a fully static build isn't
possible). cabal's new option
`--enable-executable-static` does the same. On stack
you can add something like this to the options for your
executable in package.yaml:
ld-options: -static -pthread
|
|
|
|
|
|
|
|
Closes #6771.
|
|
All `<table>` elements are put inside `<table-wrap>` elements, as the
former are not valid as immediate child elements of `<body>`.
|
|
|
|
As of ~2 years ago, lower case keywords became the standard (though they
are handled case insensitive, as always):
https://code.orgmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0
Upper case keywords are exclusive to the manual:
- https://orgmode.org/list/871s50zn6p.fsf@nicolasgoaziou.fr/
- https://orgmode.org/list/87tuuw3n15.fsf@nicolasgoaziou.fr/
|
|
according to the current list contained in
https://orgmode.org/worg/org-contrib/babel/languages/index.html
|
|
This reproduces earlier pandoc-citeproc behavior.
Closes jgm/citeproc#26.
|
|
This affects example list references followed by dashes.
Introduced by commit b8d17f7.
Closes #6855.
|
|
|
|
This makes it easier to split the module into smaller parts.
|
|
|
|
It is no longer necessary, because ghc, cabal, and stack are
pre-installed.
|
|
|
|
Closes #6841.
|
|
now that we permit extensions on formats other
than markdown.
|
|
- use real minus sign
- use tests contributed by Igor Pashev.
|
|
The commit a157e1a broke negative numbers, e.g.
`\SI{-33}{\celcius}` or `\num{-3}`. This fixes the regression.
|
|
changed: MANUAL.txt
|
|
|
|
Prevously, if we had `@foo [p. 33; @bar]`, the `p. 33` would be
incorrectly parsed as a prefix of `@bar` rather than a suffix
of `@foo`.
|
|
Previously a path beginning with a drive, like
`C:\foo\bar`, was translated to `C:\/foo/bar`, which
caused problems.
With this fix, the backslashes are removed.
Closes #6173.
|
|
|
|
|
|
|
|
|
|
|
|
Previously we used Setext (underlined) headings by default.
The default is now ATX (`##` style).
* Add the `--markdown-headings=atx|setext` option.
* Deprecate `--atx-headers`.
* Add constructor 'ATXHeadingInLHS` constructor to `LogMessage` [API change].
* Support `markdown-headings` in defaults files.
* Document new options in MANUAL.
Closes #6662.
|
|
Background: syntactically, references to example list items
can't be distinguished from citations; we only know which they
are after we've parsed the whole document (and this is resolved
in the `runF` stage).
This means that pandoc's calculation of `citationNoteNum`
can sometimes be wrong when there are example list references.
This commit partially addresses #6836, but only for the case
where the example list references refer to list items defined
previously in the document.
|
|
in note citation styles. See #6835.
|
|
|
|
|
|
|
|
Previously YAML metadata would sometimes not get recognized if a
field ended with a newline followed by spaces. Closes #6823.
|