-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typst - do not hardcode #figure()
in Table writer?
#9777
Comments
I think it would make sense to omit the The only other thing needed, then, would be a way to affect the |
Ok. I can make that change in my PR. For what's worth, that's what I used in my original attempt, but I realized two things:
I think using colons would be great. I like that
I hear you. I should have remembered that our earlier Typst properties work used colons instead of dashes. I'll definitely fix that. |
In #9778:
|
…#9778) This extends support for fine-grained properties in Typst. If the `typst:no-figure` class is present on a Table, the table will not be placed in a figure. If the `typst:figure:kind` attribute is present, its value will be used for the figure's `kind`. These features are documented in `doc/typst-property-output.md`. Closes #9777.
Would Pandoc take a PR that enabled the Typst writer to disentangle the emission of
#figure()
from#table()
? Or, minimally, a PR that would stop Pandoc from emitting#figure()
when no caption or identifier are present?Explain the problem.
Pandoc currently is unable to emit table code in Typst without also emitting a
figure()
: https://github.com/jgm/pandoc/blob/main/src/Text/Pandoc/Writers/Typst.hs#L276-L294This makes it quite hard to write Pandoc documents that put a Typst table inside a crossref environment of any other kind, or that would include a table without incrementing the
table
typst counter by virtue of the surrounding#figure()
.Typst figures accept
kind
variables other thantable
andfigure
. Notably, we use that in Quarto for subfigures and custom crossrefs ("Supplemental Table..."). In Pandoc 3.2, counters will be necessarily incorrect (and hard to fix) when users refer to tables in different environments.Pandoc version?
The text was updated successfully, but these errors were encountered: