| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to here (T.P.Readers.Typst.Math, T.P.Readers.Typst.Parsing).
|
|
New module Text.Pandoc.Readers.Typst [API change].
|
|
The transition to crypton is causing some problems.
|
|
Closes #8718.
|
|
|
|
Closes #8893.
|
|
Closes #8886.
|
|
|
|
This fixes a bug in RST documents that have anonymous links.
Closes #8877.
|
|
Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 20 to 21.
- [Release notes](https://github.com/cachix/install-nix-action/releases)
- [Commits](https://github.com/cachix/install-nix-action/compare/v20...v21)
---
updated-dependencies:
- dependency-name: cachix/install-nix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <[email protected]>
|
|
|
|
Closes #8856.
In this case we don't want to try to parse the data at the URL.
Instead, create an image inside a div.
|
|
Remove old `.c` alias that mimics the JSON representation:
- Since 2.15ish, the lua structure no longer closely resembles that
JSON representation
- even if it did, introductory examples should be explicit. Using
an undocumented alias creates ambiguity.
|
|
|
|
|
|
|
|
We don't need the workarounds any more.
We no longer include pandoc-cli, pandoc-server, or pandoc-lua-engine
in the packages. Instead, add some of the heavier dependencies to
the list of build inputs.
This is at least a temporary solution to #8818.
|
|
|
|
Block-level formatting is not allowed inside .TL.
Closes #8835.
|
|
Improves on the last commit; closes #8831.
|
|
This should help with #8831. I'm not sure this is the
best solution, but it's certainly better than what we had before!
|
|
This commit introduces support for the Intense Quote in Docx Conversion.
Previously this was converted to a regular paragraph, but Intense Quote
should be interpreted as a Quote in conversion.
|
|
|
|
|
|
Note on how CommonMark's fenced divs differ.
|
|
The writer no longer searches the list of classes for a known programming
language but always uses the first class in that list as the language
identifier.
Closes: #8814
|
|
|
|
This matches the behavior of the legacy `markdown.pl` as well as what is
described in the manual.
Fixes: #8777
|
|
The `\multicolumn` command takes the column type as the second argument.
Types like `p` take an additional argument, which is now ignored and no
longer causes the table parser to fail.
Fixes: #8789
|
|
|
|
The previous commit prevented header column cells from being dropped on
the floor, this one changes the paragraph style to "Table_20_Heading".
Note that for the test input, the result is not correct: the
AnnotatedTable type cannot represent the HTML input properly, as it only
has a concept of header rows and header columns, but HTML can have an
individual cell that is a header (not 100% sure but they way i read
https://html.spec.whatwg.org/#header-and-data-cell-semantics the <th>
cell here is both a row header cell and a column header cell while the
other cells in the row and column are not header cells), and header
cells may even appear "in the middle" of a table (see example in
https://html.spec.whatwg.org/#the-th-element).
So while this appears like it's the right thing to do for
Writer.OpenDocument, it's not clear if this is going to make things
better or worse overall.
Fixes: #8764
|
|
While ODF 1.3 part 3 does specify a 9.1.11 <table:table-header-columns>
element, in practice it's only implemented by spreadsheet applications,
not word processors.
So simply treat the row header columns as ordinary table columns, at
least they don't get lost then.
Fixes: #8764
|
|
The only element in meta for which data/templates/default.opendocument
allows block element content appears to be "abstract", which is already
filtered out of meta' at this point, so simply convert all blocks to
linebreak-separated inlines.
Fixes: #8256
|
|
Commonmark supports these.
|
|
The way "ooo:configuration-settings" work is that if LibreOffice Writer
loads a file in which it exists, it assumes that an old version of
itself has produced it and it defaults any config-item that it knows but
that doesn't exist in the file to the "backward-compatible" value, which
usually means to enable some layout or text formatting bugs so that the
document looks the same as in the old LO version that created it.
If there is no "ooo:configuration-settings" then it will use the default
values for a new document, which should give the best formatting
results.
Pandoc's documents are obviously not created by LO, so it doesn't make
sense to produce ooo:configuration-settings.
Regarding the "ooo:view-settings", IIRC these mainly set to the
document view to the position where the document was last edited (by
default only if the user in meta.xml matches the user data in LO's
configuration), which is also irrelevant for Pandoc.
So just leave out the settings.xml; only content.xml/styles.xml are
required (see ODF 1.3, part 3, 2.2.1 OpenDocument Document, A.2).
(The settings.xml that is produced for formulas by the documentSettings
function hopefully isn't problematic because LO Math works a bit
differently and stores important formatting attributes in settings.xml
because MathML doesn't allow it in content.xml.)
|
|
This empty file is some ancient OOo wart and it's quite pointless here.
|
|
Quite pointless to add a hardcoded image that doesn't show the
document content.
|
|
See ODF 1.3 part 2, 4.16.14.1 <manifest:file-entry>:
The manifest:version attribute specifies the format version of a file
entry. For documents that are composed from multiple files, this
attribute is specified at the manifest entry that references the
folder that contains these files.
|
|
The ODF validator complains about an invalid attribute
style:contextual-spacing in styles.xml, ultimately an implementation
error in whatever old version of LibreOffice that produced the
data/odt/styles.xml (should have put it into an extension namespace).
Fortunately the attribute was added to ODF 1.3, which was released a
couple years ago.
So the easiest fix is to simply produce ODF 1.3 instead of 1.2; it's
supposed to be fully backward compatible.
|
|
|
|
|
