This changes the media type that's used for the file extension listed
below. The new types are either IANA approved, or so similar to the
override that is does not seem sensible to keep a separate entry.
For East Asian languages, we need to adjust `w:eastAsia`
rather than `w:val`. This allows normal fonts to be used
for any Latin-font text. Similarly, for bidi languages, we need
to adjust `w:bidi` rather than `w:val`.
We treat `he` and `ar` as bidi languages, `zh`, `ja`, `ko`
as East Asian languages.
Closes#7022.
This allows to specify a table foot by enclosing it with part separator
lines, i.e., row separator lines consisting only of `+` and `=`
characters. E.g.:
+------+-------+
| Item | Price |
+======+=======+
| Eggs | 5£ |
+------+-------+
| Spam | 3£ |
+======+=======+
| Sum | 8£ |
+======+=======+
The last row, containing "Sum" and "8£", is the table foot.
Closes: #8257
...bibliography type when the bibliography is fetched remotely.
This will help with cases where the URL ends in a parameter
or otherwise does not end with a file extension.
Closes#7151.
Otherwise the `?` character that is there as a fallback
for systems that can't process the unicode will be interpreted
as the paramater's delimiter, and the NEXT character will be
gobbled instead of `?`.
Closes#8264 (fixes a problem with disappearing characters
after unicode escapes).
If a document uses numbered headings, then headings without numbers are
marked with class `unnumbered`, the default class used by pandoc to
convey this kind of information. The classes are not added if none of
the headings in a document are. This change ensures good conversion
results when converting with `--number-sections`.
Closes: #8148
Previously we just returned a JSON-encoded string.
Now we return something like:
```
{
"output": "<p>hello</p>"
"base64": false,
"messages": [
{
"message": "Not rendering RawInline (Format \"tex\") \"\\\\noe\"",
"verbosity": "INFO"
}
],
}
```
This is a change in the pandoc-server JSON API.
These should not be generated by any pandoc readers, but they
might be produced programatically. Technically that's a misuse
of the AST, but since the expectation that the classes are
nonempty strigs is not encoded in the types, it can happen. This patch
limits the damage if it does, preventing invalid markdown attributes
like `{.}` from being written.
Cloess #8251.
Previously the content of each list cell was indented when
the table belonged to a list item. This is obviously unwanted.
With this patch, a table inside a list item will be formatted
just like a table outside the list.
One desirable improvement would be to add some left indentation
to the entire table, so it visually appears to belong to the
list item. But I'm not sure how to do that.
Albert Krewinkel