| Age | Commit message (Collapse) | Author |
|---|
|
* To conform to validator's expectations, `doc-footnote` role is used
with `aside` and `doc-endnotes` with `section`.
* `aside` is used only for notes at ends of sections or blocks;
if all the notes come at the end of the document, `section` is
used so we can have the `doc-endnotes` role.
|
|
Closes #9104.
|
|
...and language-name environments like
`\begin{french}...\end{french}`.
Closes #9202.
|
|
* #9214 text in shape format test document
* #9214 support Text in Shape Format
* #9214 remove irrelevant code
|
|
Add T.P.Readers.Docx.Symbols. This gives us a table to use to
resolve characters included in docx via w:sym element.
Use this table to resolve characters when symbol fonts are specified.
Closes #9220.
|
|
|
|
- Ensure unique ids for elements by prefixing SVG id.
- Ensure SVG `id` attribute except when `use` element is used.
- Remove `width`, `height` attributes from svg element when `use`
element is used. Instead, add `width` and `height` 100% to the
`use` element. This seems to get the sizing right.
Closes #9206.
Ref: #8948.
|
|
|
|
|
|
`\phantomsection` can't be used in this case, so we need `\hypertarget`.
Closes #9209.
|
|
Closes #9201.
|
|
Closes #8872.
In the current implementation , theorem labels in `theoremEnvironment` are
determined by the `LastLabel` in the current state.
This approach works well when the `\label{label_name}` is placed at the end
of the theorem body. However, when a label is placed at the beginning of the
theorem (another common practice) and additional labels follow in the theorem body,
`theoremEnvironment` incorrectly picks the last label (e.g., `\label{item2}` in #8872).
This patch addresses the issue by extracting the label extraction independently of the `LastLabel` state.
|
|
See #9195.
|
|
- Only treat as base64 if ';base64' is present.
- Otherwise treat as UTF-8 (not 100% reliable but should cover most
other cases).
- Strip off ';base64' (or ';charset=...' or whatever) from mime type.
This last change addresses #9195 (problems with data URIs in
conversion to docx).
|
|
We now put these in a figure with a caption argument.
Closes #9194.
|
|
This revises the fix to #8150 (and the test case) and closes #9187.
HTML in the (invalid) form:
<ul>
<li>L1</li>
<ul>
<li>L1.1</li>
</ul>
</ul>
is treated by browsers like
<ul>
<li>L1
<ul>
<li>L1.1</li>
</ul>
</li>
</ul>
not
<ul>
<li>L1
<li><ul>
<li>L1.1</li>
</ul>
</li>
</ul>
as pandoc previously assumed.
This change will give a similar treatment to
<ul>
<li>L1</li>
<p>foobar</p>
</ul>
which also seems to match browser behavior.
|
|
Preserve them: otherwise we can get unwanted results if there's
a `%` comment. Closes #9193.
|
|
Closes #9188.
|
|
Closes #9178.
|
|
Closes #8979.
|
|
Closes #9171.
|
|
[API change]
|
|
Previously in such cases the references were not being moved to
back matter. Closes #9166.
|
|
This package produces better PDF bookmarks than hyperref
and does it on the first pass.
As a consequence, we now default to running LaTeX only
once in producing a PDF (instead of twice). If a table
of contents is present, we still have to run three times
to get the page numbers.
|
|
The groff_man (7)` man page indicates that `-` characters will be
treated as typographic hyphens and are not appropriate for cases
where the output should be copy-pasteable as an ASCII
hyphen-minus character. (E.g. in command line options.)
However, until a recent update groff man did not actually do this;
it treated `-` and `\-` the same. With the new update (1.23.0)
the two are distinguished (see https://lwn.net/Articles/947941/
for background), so now it is important that pandoc escape `-`.
This reverts ee60ba5252360d2efbf9cf30197236a21a15a924.
That change was motivated by a problem with backslash-escaping
`-` in a filename for .PSPIC. That's simply a separate issue;
we shouldn't do the normal escapes in such a context. It has
been addressed in the previous commit.
|
|
for PSPIC etc.
Note: I haven't been able to figure out how to make it
work if the filename contains a `"` character.
|
|
For there will be nothing to link to. Closes #9163.
|
|
so that it recognizes an item containing only a list which is
itself tight as potentially an item in a tight list.
Closes #9161.
|
|
|
|
Closes #9021.
|
|
Document in MANUAL.txt.
|
|
Add provision for title-group, book, book-part-wrapper, book-meta,
book-part-meta, book-title, book-title-group, index, toc, legend,
title, collection-meta
|
|
Closes #9159.
|
|
Closes #9158.
|
|
Parse GFM-specific math constructions when `tex_math_gfm` enabled.
See <https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions>.
Closes #9121.
|
|
[API change]
This handles two GitHub-specific syntaxes for math.
And document in MANUAL.txt.
This is now default for `gfm`, in addition to `tex_math_dollars`.
See #9121.
|
|
Closes #9155.
|
|
using e.g. `https:%%//%%...`. Closes #9153.
This is not a fully general fix but it should be enough if
there's a convention of defeating autolinks by putting the
slashes in `%%..%%`.
|
|
Previously we treated them as inline code in some contexts,
but that is not how DokuWiki works.
Closes #9154.
|
|
hfill, vfill, hskip, vskip, etc.
Closes #9150.
|
|
An `#image` by itself in typst is a block-level element.
To force images to be inline (as they are in pandoc), we need
to add a box with an explicit width. When a width is not given
in image attributes, we compute one from the image itself, when
possible.
Closes #9104, supersedes #9105.
|
|
Previously `[^super^](#ref)` wasn't parsed as a link, due to
code that was meant to prevent footnote markers from being
recognized as reference links. This commit tightens up that
code to avoid this bad effect.
We have also added a new restriction on footnote labels: they
cannot contain the characters `^`, `[`, or `]`. Though this is
technically a breaking change, we suspect that the impact will
be minimal, as it's very unlikely people would be using these
characters in their note labels.
Closes #8981.
|
|
Closes #9090.
|
|
caused when the document used both a regular png and a png
in a data URI. (Similarly for any other image format.)
The problem was that duplicate entries in `[Content Types].xml`
were being created, one for the mime type `image/png`, one for
`image/png;base64`.
Closes #9113.
|
|
...so they use the width of the column (`=` as the width
parameter). Closes #9140.
|
|
This should help fix a problem wherein some grid tables with
colspans were overly wide. See #9140.
The example given there still produces suboptimal
output (overlapping text), so not closing yet.
|
|
Previously we were looking for an attribute that doesn't exist in
JATS; alt-text is provided by a child element.
Closes #9130.
|
|
If it occurs in certain contexts, it can be parsed as function
application. Simplest thing to do is to escape it always.
Closes #9137.
|
|
|
|
|
