| Age | Commit message (Collapse) | Author |
|---|
|
Preserve them: otherwise we can get unwanted results if there's
a `%` comment. Closes #9193.
|
|
Closes #8979.
|
|
Closes #9171.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
...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.
|
|
See #9120.
We need to use `\c` before a `.UR` or `.MT`, to avoid
an extra space, and also after. To ensure that a space
at the beginning of the following line doesn't get swallowed
up, we escape it with `\`.
|
|
This improves the man and ms writer output, preventing
sentence breaks after initials.
|
|
Closes #9120.
|
|
Closes #9088.
|
|
Allow the HTML reader to parse task lists of the sort produced by pandoc.
Closes #9047
|
|
See #4475.
+ PDFPIC is now used for PDF images in figures.
+ Inline images that are postscript or PDF are rendered using
PSPIC or PDFPIC. This isn't ideal, because they will still be
rendered as if in a separate paragraph, but it's probably
better than just printing the image name.
+ Units are included in height.
For further improvement, we might consider in Text.Pandoc.PDF
using something like `convertImages` (which we currently use for
converting to PDF via LaTeX) to convert SVG (and other?) images
to PDF so they can be rendered in this way.
|
|
According to the CSL manual, the default entry spacing is 1.
We were treating it as 0.
T.P.Citeproc: always include an entry-spacing attribute
in the Div if the bibliography element contains an entry-spacing
attribute (previously we omitted it when it was 0).
LaTeX writer: use entry spacing 1 if no entry-spacing
attribute is present.
Update tests.
See #9058.
|
|
|
|
In 3.1.7, pandoc added two labels to LaTeX figure environments,
one with a phantomsection.
Closes #9045.
|
|
In general, the ID prefix makes it possible to combine multiple pieces
of Pandoc-generated HTML with no possibility that IDs will conflict. One
exception to this was that the footnotes were always put into an element
like
<aside id="foonotes" ...>
This commit applies the ID prefix to this ID as well.
|
|
In 3.1.6.1 the `~` was handled properly (either literally or with
`%E7`). This broke in 3.1.6.2, which used URI encoding in both
cases and didn't escape the `\` before `%E7`. This patch restores
the former behavior: `~` isn't escaped if it isn't escaped in the
original URL, and if it is, a backslash is added before `%`.
Closes #9043.
|
|
...unless the `fancy_lists` extension is enabled.
Closes #9042.
|
|
This revises the earlier support for `<permissions>`: now metadata objects
with multiple fields are created, matching the structure in JATS.
|
|
E.g. `![[foo|bar]]`. (This requires enabling one of the `wikilinks`
extensions.)
Closes #8853.
|
|
Closes #8254.
|
|
In e.g. `![foo]` the `!` would be silently dropped if `[foo]`
wasn't a reference link label.
Closes #9038.
|
|
|
|
Signed-off-by: Amneesh Singh <natto@weirdnatto.in>
|
|
+ Use `\phantomsection` and `\label` instead of `\hypertarget`.
+ Use `\hyperref` for LaTeX internal links, `\hyperlink` for
beamer (since `\hyperref` doesn't seem to work).
Closes #9022.
|
|
This is at best a no-op (in groff man and mandoc) and at worst
(in some formatters) may create extra whitespace.
See #9020.
|
|
The aim here (see #9020) is to produce more standard and more
portable man pages. To that end:
- We revert the fanciness introduced in #7506, which employs a
custom font name V and a macro that makes this act like boldface
in a terminal and monospace in other formats. Unfortunately,
this code uses a mechanism that is not portable (and does not
work in mandoc).
- Instead of using V for inline code, we simply use CR.
Note that `\f[CR]` is emitted instead of plain `\f[C]`,
because there is no C font in man. (This produces warnings
in recent versions of groff.)
- For code blocks, we now use the `.EX` and `.EE` macros,
together with `.IP` for spacing and indentation. This gives
more standard code that can be better interpreted e.g. by mandoc.
|
|
regardless of setting of `hyphenate` variable. See #9020.
|
|
...when no title is specified for the reference section.
(In this case we place it in `back` with an empty title.)
Closes #9017.
|
|
This improves the fix to #9017 in commit
7c4354646b57aa0d505dc955f856b8c3443c8db4
An alternative would be to avoid backslash escaping `#` and `%`
in URLs, and instead always add `fragile` to the slide environment.
|
|
Targets typst 0.7.
|
|
And escape literal `~`.
Closes #9010.
|
|
We no longer wrap section headings in a `\hypertarget`.
This is unnecessary (hyperref creates an anchor based on the
label) and it interferes with tagging.
In addition, we now use `\hyperref` rather than `\hyperlink`
for internal links.
Currently `\hypertarget` is still being used for link anchors
not on headings.
Closes #8744. Thanks to @u-fischer.
|
|
Closes #9002.
|
|
See the regexp at https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/lisp/org-element.el?h=d1e4b9351941aa9241ab3aa0a34256376b7eca94#n2420.
|
|
The docx reader was overzealous in detecting indented
paragraphs as block quotes, leading to list items sometimes
being put in block quotes (especially in docx created by
Google Docs).
Closes #8836.
|
|
|
