Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
The multicols environment has a mandatory argument - number of columns.
It is incorrectly parsed as plain string.
Wrap multicols content into nested divs.
Signed-off-by: Igor Pashev <pashev.igor@gmail.com>
|
|
Closes: #6312
|
|
The contents of the `center` environment are put in a `Div`
with class `center`.
|
|
- `<tfoot>` elements are no longer added to the table body but used as
table footer.
- Separate `<tbody>` elements are no longer combined into one.
- Attributes on `<thead>`, `<tbody>`, `<th>`/`<td>`, and `<tfoot>`
elements are preserved.
|
|
|
|
This removes the `foldOrElse` function from the internal Text.Pandoc.CSS
module.
|
|
|
|
|
|
|
|
Reducing module size should reduce memory use during compilation.
This is preparatory work to tackle support for more table features.
|
|
Fixes: #6845
|
|
Improves on 9a40976. Closes #6873.
|
|
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.
|
|
...and put it in a div with class `formalpara-title`, so that
people can reformat with filters.
Closes #6562.
Thanks to rdmuller.
|
|
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.
|
|
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/
|
|
This reproduces earlier pandoc-citeproc behavior.
Closes jgm/citeproc#26.
|
|
This affects example list references followed by dashes.
Introduced by commit b8d17f7.
Closes #6855.
|
|
|
|
- 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.
|
|
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`.
|
|
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.
|
|
|
|
Previously YAML metadata would sometimes not get recognized if a
field ended with a newline followed by spaces. Closes #6823.
|
|
* Remove unused LANGUAGE pragmata
* Apply HLint suggestions
* Configure HLint to ignore some warnings
* Lint code when committing to master
|
|
Previously this confused the table parser. Closes #6811.
|
|
(LaTeX reader)
Closes #6802.
|
|
If `\cL` is defined as `\mathcal{L}`, and `\til` as `\tilde{#1}`,
then `\til\cL` should expand to `\tilde{\mathcal{L}}`, but pandoc
was expanding it to `\tilde\mathcal{L}`. This is fixed by
parsing the arguments in "verbatim mode" when the macro expands
arguments at the point of use.
Closes #6796.
|
|
Also add unit test to ensure the behavior stays consistent.
|
|
See #6770.
|
|
...unless `raw_html` is set in the reader (in which case
the svg is passed through as raw HTML).
Closes #6770.
|
|
Also do some minor refactoring - bibliodiv without
a title no longer results in an empty Header.
|
|
Typos reported by
https://fossies.org/linux/test/pandoc-master.tar.gz/codespell.html
See: #6738
|
|
`\acl`, `\aclp`, and capitalized versions of already
supported commands.
Closes #6746.
|
|
Otherwise we get bad results for non-table, non-paragraph
lines containing pipe characters.
Closes #6739.
See also jgm/commonmark-hs#52.
|
|
|
|
Previously we were just treating it as a string and
ignoring accents and formatting. See #6734.
|
|
|
|
Instead, include it after the emphasis. Closes #6719.
Same fix was made for other inline elements, e.g. strikethrough.
|
|
|
|
|
|
|
|
Closes #6730.
Previously the command would succeed, returning empty metadata,
with no errors or warnings.
API changes:
- Remove now unused CouldNotParseYamlMetadata constructor for
LogMessage (T.P.Logging).
- Add 'Maybe FilePath' parameter to yamlToMeta in T.P.Readers.Markdown.
|
|
For security reasons, some legal firms delete the date from comments and
tracked changes.
* Make date optional (Maybe) in tracked changes and comments datatypes
* Add tests
|
|
Parsing of YAML bibliographies was broken; this fixes it.
|
|
T.P.Readers.Markdown now exports yamlToRefs. [API change]
T.P.Readers.Metadata exports yamlBsToRefs. [API change]
These allow specifying an id filter so we parse only references
that are used in the document. Improves timing with a 3M
yaml references file from 36s to 17s.
|