更新日志
v0.8.1
A patch release with fixes and a few corrections to behaviour that 0.8.0 introduced.
Behaviour changes
-
An em dash between inline content no longer splits slides
A
—or---with inline content on both sides, such asText —code``, stays part of the sentence. Before, it was read as a horizontal line, which started a new slide and dropped the dash. A dash next to a blank line, a heading, any other block or a touying marker or wrapper such as#pauseor#alert[..]still splits slides.Migration: where a break is wanted, put a blank line around
---. -
A bare waypoint label picks its last subslide in three places
A bare label in
handout-subslideskeeps the last subslide of the waypoint, as the label oftouying-recallon labelled content does.measuretakes the largest size over the waypoint's range. The range markersfrom-wp,until-wpandnot-wpkeep every subslide they span, sonot-wp(not-wp(<a>))is exactly the range of<a>.handout-subslides: "waypoints"selects the last subslide of every waypoint.Migration: where you need other subslides than the last one, use a range marker such as
from-wp,until-wpornot-wp. -
Footnote numbering restarts per slide, not per page
reset-footnote-number-per-slidenow restarts the numbering only at the start of a slide, andcounter(footnote)is one of the default frozen counters, so the numbers stay the same on every subslide. Before, the counter was reset on every page. A breakable slide that overflowed onto a second page restarted at 1 there, and withreset-footnote-number-per-slide: falsethe numbers of a slide ran ahead from one subslide to the next. Now overflow pages keep counting, and withfalsethe numbering continues across slides while staying identical across the subslides of one slide. -
touying-reduceworks with alchemist 0.2.0A package's own
touying-reducer-bindingsare used whenreduceandcoverare both functions. Otherwise touying uses the bindings it has for the package'sname. -
Slide Preambles are now called again and preambles will be reworked soon together with more external hooks
slide-preambleanddefault-slide-preambleare called again (they were silently dropped in March 2026). A slide now starts withpreamble(first slide only), thenslide-preamble, then the content a deferred config change collected in front of the slide, which used to run first. And finally the subslide preamble. These all run after the header is constructed, only thepage-preambleis run before the header (old behaviour).Bc preambles were not easy to use for external packages they will be reworked soon in a rework that aims to allow better 3rd party package integration. The touying-reducer-bindings will stay, but other hooks will be added.
Fixes
#heading[..]outside a slide call no longer fails withfield "depth" in heading is not known at this point(#434, #437).- A
#figurewithout a caption that is hidden by a#pauseno longer fails withfield "caption" in figure is not known at this point(#437). animate,animate-hidden,animate-removedanditem-by-item-fnare now listed in default methods throughself.methodsandutils.methods(self)just likeuncoverandonly.capitalizeandtitlecasework on non-ASCII input (#436).- Reducers announce the inner minimum repetitions and function wrappers of their content (#431).
- Aligned content no longer shifts when paused list items are revealed (#442).
measureof a list applies the row gap, so show-set rules take effect (#443).- The numbers of an enum with a
#pausestay aligned: the covered and the visible part get the same number column width, so items no longer move sideways when the covered part is revealed (#438). touying-mitexkeeps the height of a line break that is still hidden, so the visible lines no longer move sideways when the next line is revealed.- A
#meanwhilebetween list items after an earlier#pauseno longer splits the list, so the rows no longer move when the next subslide is shown (#439). - The ctheorems 2.x states are frozen across subslides (#452, #454). Support for ctheorems 1.x is deprecated and will be removed in v0.9.0.
- The documentation of
until-wpandfrom-wpnow says what they do:until-wpstops before the first subslide of the waypoint,from-wpincludes it and runs to the end. - The API reference lists the functions of
src/core/*.typandtouying-slides, and the documentation of each release is published by the newdocs-releaseworkflow.
v0.8.0
A big release, and the first that requires Typst 0.15.
The main new feature is article mode: the same source file compiles either to slides or to a flowing prose document, with animations collapsed to their final state and images optionally floated to the side. Two new animation entry points come with it. touying-render renders a piece of content at chosen animation stages, and animate combines visibility and styling on one piece of content. touying-recall was extended from whole slides to any labelled element. touying-fn-wrapper-raw now parses and nests its body, so #alert[.. #pause ..] works, and much more besides. .pdfpc files can be written directly as bundle assets instead of through a separate typst query step. The footnote bibliography was rebuilt on real Typst bibliographies, and the speaker-note panel is now a theme-supplied function with documentation to match. Internally, src/core.typ (6288 lines) was split into modules and the content handling was unified and several functions (mainly out of utils) moved places.
Things to watch when upgrading: a #pause after uncover/only/alternatives no longer skips the subslides they reserve (they wrongfully did so with v0.7.0), the footnote-bibliography config changed shape, semi-transparent-cover is deprecated, and on a second screen the page background is confined to the slide half. There is a migration guide below, and a separate one for theme authors at the end. Most documentation pages were rewritten or corrected.
Breaking Changes
-
feat!: Touying now requires Typst 0.15.0
typst.toml'scompilerfield goes from0.12.0to0.15.0. Bundle export for.pdfpcassets and the reworked cover methods both need it. All reference renders were regenerated against Typst 0.15 / tytanic 0.4. -
fix!: a
#pauseafteruncover/only/alternativesno longer skips the subslides they reserve#uncover("2")[Only on subslide 2]
On subslide one
#pause
On subslide two // v0.7.0-v0.7.4: on subslide *three*Up to v0.6.x a relative jump advanced the counter by one. v0.7.0 changed it to snap past the highest subslide any preceding fn-wrapper had reserved. That was meant for
item-by-item, which stands in for a run of pauses and should push a later#pausepast its whole animation. Butitem-by-itemreports its extent through the same channel as every other wrapper, so the change caughtuncover,onlyandalternativesas well. No test asserted it and it slipped past. Reserving subslides and consuming them are separate things again.Waypoint placement gets the same correction.
#waypoint(<w>)after an#uncover("5")now lands one past the current flow position, not one past subslide 5.Migration: if you relied on the snap, add the extra
#pause(or#jump(n, relative: true)or waypoints) yourself.item-by-itemanditem-by-item-fnare unaffected. They still push later pauses past their last item, and they now match the hand-written#pausesequence they abbreviate, including for content that follows them without any#pause. -
feat!:
show-bibliography-as-footnoteis a boolean, andmagic.bibliography()is goneThe old mechanism took the bibliography element itself, as
config-common(show-bibliography-as-footnote: bibliography("ref.bib")), hid it in the preamble, collected the entries into a state, and re-rendered them throughmagic.bibliography(). That state is gone. Set the flag and call a real#bibliography(..)in the presentation:#show: simple-theme.with(
config-common(show-bibliography-as-footnote: true),
)
== References
#bibliography("ref.bib")The bibliography has to be part of the document for the footnote citations to resolve. Use
hide(bibliography(..))if you do not want the reference list shown. Multiple bibliographies work now, and #395, where a footnote bibliography that overflowed its slide stopped the document converging, is fixed as a result. If your citation style already produces notes, such as"chicago-notes", leave the flag atfalse. See the FAQ.magic.bibliography-as-footnoteloses itsbibliographyparameter and gainsfootnote-style, a dictionary ofsuperproperties for the citation markers. The default(typographic: false, baseline: 0em, size: 1em)makes them read as normal text. -
feat!: the speaker-note panel is customizable through
config-common(notes-fn: ..); theconfig-methods(show-only-notes: ..)renderer is removed (#353)show-only-noteswas two separate options in v0.7.4 and only one of them changes.config-common(show-only-notes: true), the flag that turns on presenter view, works as before, and is documented for the first time in Speaker Notes. What is gone isconfig-methods(show-only-notes: ..), the function that drew the panel. Only theme authors ever overrode it.The panel is now produced by a theme-supplied function, the way slides are produced by
slide-fn.notes-fn(self: none, note: none, slide-preview: none) -> contentmirrorsslide-fn, andtouying-notesis the counterpart oftouying-slide: it owns the rough layout, the theme passes colours and arranges the content. All six bundled themes register their own, so the notes panel matches the deck in spirit. Some alignment bugs will be fixed later.show-only-notesmode was restructured along with it. The slide's parts, previously shown on the top right, are reassembled into one page-sized box and handed to the theme asslide-previewcontent to place where and scale how it likes. The oldcutout/cutout-height/(background, foreground)return protocol is gone, andslide-preview: nonetells a theme it is on a second screen. This also fixes #281: the panel background was placed from the page header and nearly all of it fell off-page, so the declared#CCCCCC/#E6E6E6colours never rendered.See Customizing the Speaker-Note Panel and Build Your Own Theme.
-
fix!: the page background and foreground are confined to the slide half on a second screen (#219)
With
show-notes-on-second-screen, Touying doubles the page along one axis and pushes the extra half into the margin (Now all four alignments are supported).page(background: ..)covers the whole page, so a background sized100%, or an image withfit: "cover", was stretched across the slide and the notes half together.backgroundandforegroundare now each placed in a box the size of one slide, on the slide's own half, so percentage sizes andfit: "cover"behave as they do without a second screen. -
feat!:
touying-recall'ssubslide:parameter becomessubslides:, and itsnone/autovalues swapThe parameter is now plural because it takes ranges (since v0.6.3) rather than a single subslide, matching
visible-subslidesonuncover/only/effect. It accepts a superset of the old values.subslides: autois the new default. It recalls all subslides of a whole-slide target, or the final animation state of a labelled element.subslides: nonerecalls only the last subslide. v0.7.4 had these the other way round, withnoneas the default, so the default behaviour is unchanged. Only code that passed either value explicitly needs the value swapped as well as the key renamed.
Minor Breaking Changes
-
feat!:
utils.semi-transparent-coveris deprecated — useutils.alpha-changing-coverorutils.color-changing-coverIt worked by overlaying a semi-transparent rectangle on the covered content, which does not hold up in general: the overlay dims the slide background along with the content, and it stacks where covered regions overlap. It still renders, (slightly worse than the last iterations) so presentations keep compiling. Builds that use
--warnings promotewill however fail.// Before
config-methods(cover: utils.semi-transparent-cover)
// After: a real alpha cover, with an automatic fallback for content it cannot recolour
config-methods(cover: utils.alpha-changing-cover)
// Or, cheaper to compile, flattening everything to one colour
config-methods(cover: utils.color-changing-cover.with(color: gray))