| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
|
|
In certain cases, text before a table was being incorporated into
the table itself.
Closes #8767.
|
|
Otherwise our code can fail to determine image size.
|
|
With this change, the typst writer will omit the `#bibliography`
command when `citations` is not enabled. (If you want to use
pandoc's own `--citeproc`, you should combine it with
`-t typst-citations` to disable native typst citations.
Closes #8763.
|
|
The role "bf" is taken to indicate "bold face", i.e., "strongly emphasized"
text, while "underline" leads to underlined text.
|
|
Internal links to labels are now supported.
|
|
Partially addresses #8408
|
|
One must now use `typst compile` rather than `typst`.
Closes #8754.
|
|
Co-authored-by: Wout Gevaert <wout@wikibase.nl>
|
|
Closes: #8578
|
|
|
|
Closes: #8729
|
|
This reverts commit b208eb2a560b8571af577667d5df8706f4ba8892.
|
|
The `<label>` element ensures that the item description is associated
with the checkbox, which is important for accessibility.
See: #8729
|
|
It's an aesthetic issue only; the first line had an
extra space indent after the list marker.
|
|
|
|
|
|
|
|
+ Update manual with variables for Typst.
+ Split `lang` metadata into separate `lang` and `region` for Typst.
+ Fix label positioning in Divs.
+ Fix text customizations (lang, region, font, size) so they actually
work.
+ Update tests and man page.
|
|
+ Fix non-decimal enumerated lists.
+ Fix endnotes ending with code blocks.
+ Improve default template to use a typst template.
+ Factor out definitions and typst template into partials.
+ Properly escape backslash and quote inside double quotes.
+ Update tests.
|
|
|
|
See #8713.
|
|
This prevented users to use custom writers with uppercase characters in
their filenames. Format-normalization, including lower-casing of
format identifiers, happens during format parsing.
|
|
Allow the character U+200B to be used as an escape character as described
in the Org-mode documentation https://orgmode.org/manual/Escape-Character.html
Closes issue #8716.
|
|
This also adds a test xref to book and part. See also 4ea0508e6 / #8712.
|
|
Closes #8712.
|
|
* T.P.Format: export `formatFromFilePaths` [API change]
* Lua: add function `pandoc.format.from_path`
* Update lua-filters.md
* The old T.P.App.FormatHeuristics module has been removed.
This is an alternative to #8693.
|
|
Previously with this configuration, `<span>`s were not treated
as inline elements at all.
Closes #8711.
|
|
Now that we're doing `nubOrd` on classes at the end (when changing
pandoc attributes to HTML attributes), we don't need to do it here.
|
|
|
|
Closes #8705.
|
|
Closes #8702.
Uses localized term for abstract.
|
|
and .png.gz etc.
Closes #8699.
|
|
When `--reference-location=section` or `=block`, use an
`aside` element for the notes rather than a `section`.
When `--reference-location=section`, include the `aside`
element inside the section element, rather than outside.
(In slide shows, this option causes footnotes on a slide
to be displayed at the bottom of the slide.)
Closes #8695.
|
|
|
|
Closes: #8689
|
|
The title of a jira panel is added in a nested div as the first element
of the div panel.
Fixes: #8681
|
|
|
|
The Ms writer was never updated to handle the new
Figure element now produced by the markdown reader.
See #8660.
|
