← 返回日报
精读 预计 20 分钟

Typst 0.15.0

摘要

本次更新涵盖多项核心增强:支持可变字体及其轴配置;HTML 导出原生支持 MathML 公式并优化段落逻辑;新增实验性 Bundle 导出,允许单项目输出多网页或文件;支持在单文档中使用多个参考文献表及专色(Spot colors);引入新的文件路径类型(路径中不再允许使用反斜杠);此外还改进了数学公式布局的一致性,并支持同时导出多种 PDF 标准。

荐读理由

针对技术文档工程,你可以利用新增的 bundle 导出功能将单个 Typst 项目直接生成多页面网站,并通过原生 MathML 支持解决 AI/技术文档在 Web 端公式渲染的兼容性与无障碍问题。

原文

Typst 0.15.0 (June 15, 2026)

This section documents all changes to the Typst language and compiler between Typst 0.14.2 and 0.15.0. If you are migrating an existing document to Typst 0.15, make sure to check out the Migration guide. It walks you through changes you may need to make to your existing documents to ensure compatibility with Typst 0.15.

Highlights

  • Typst now supports variable fonts

  • HTML export now supports equations out of the box via MathML

  • With the new, experimental bundle export target, a single Typst project can output multiple files (e.g. a multi-page website)

  • A single document can now contain multiple bibliographies

  • Typst can now target multiple PDF standards at once

  • The new within selector simplifies many introspection use cases

  • The new divider element represents a thematic break that templates can style

  • Spot colors enable use of custom pigments in offset printing

  • With the new file path type, project-relative paths can be passed to packages

  • The new, more general typst eval CLI subcommand supersedes typst query

  • Layout convergence issues now result in detailed diagnostics

  • Two long-standing list layout issues with marker alignment and centering were fixed

  • Paragraph handling in HTML export is improved, preventing unexpected paragraphs from appearing

  • This documentation now has a print version

Language

Syntax

  • File paths (e.g. in imports or image function calls) may not contain backslashes anymore; instead forward slashes must be used Link (Breaking change)

  • Added hints for invalid characters in code mode Link

  • Added hint when trying to use a unary operator directly in an embedded expression using a hash (e.g. #-30deg) Link

  • Fixed potential stack overflow crashes by enforcing a maximum parsing depth Link

  • Fixed incremental parsing of unclosed strings Link

Styling

  • Text show rules now have tracebacks that include the matched text Link

  • Fixed a crash with text show rules that match on multi-character symbols Link

Scripting

  • Extended hint when built-in definitions are shadowed to set and show rules Link

  • Added hint when trying to spread one or multiple dictionaries into an array Link

  • Improved diagnostics for invalid method calls Link

  • Improved hint for unknown variables in math that are available in std Link

  • Fixed a misleading error message when trying to assign to a temporary return value Link

Library

Foundations

  • Added file path type that is now accepted in all places where paths were previously only represented as strings Link

    • A path constructed in one file can be used in another file, but will be resolved relative to its original file

    • Likewise, paths can be passed across package boundaries

    • The initial path type is very minimal, but additional features like file existence checks or directory walking are planned

  • Collections

  • Calculation

    • Added asinh, acosh, atanh, and erf functions to calc module Link Link

    • Added int.min and int.max constants for the minimum and maximum representable integer, respectively Link

    • Fixed behavior of quo for negative integers Link

    • Fixed potential overflows in norm, abs, gcd, and lcm Link Link

    • Floating-point calculations are now consistently deterministic across platforms Link

  • Date & time handling

    • The offset parameter of datetime.today now accepts durations as an alternative to integers, allowing for sub-hour precision offsets Link

    • Addition and subtraction of datetimes and durations now retains precision instead of clamping to full days in some cases Link

    • The datetime constructor now emits more precise errors when components are missing Link

  • Conversions

    • Added base parameter to int constructor to configure in which base to parse a string Link

    • Fixed that the base parameter of the str constructor was accepted for non-integer values if its value was 10 Link (Minor breaking change)

    • Added hint when trying to construct a string with base 1 Link

  • The panic function now displays strings as-is instead of showing their repr, making it more suitable for friendly, user-facing messages Link

  • Changed repr of styles and locations to be more distinct Link

Model

  • Added divider element representing a thematic break that templates can style Link

  • Bundle-related elements

    • The document element can now be constructed to produce individual documents in bundle export Link

    • Added path and format parameters to document element Link

    • Added experimental asset element Link

  • Bibliography management

    • A single document can now contain multiple bibliographies Link

    • Added target parameter to bibliography element to configure which citation is picked up by which bibliography Link

    • Added group parameter to bibliography element to configure how numbers are shared/reset across bibliographies Link

    • Added support for numeric values for the month key in .bib files Link

    • Added support for BibLaTeX name options in .bib files Link

    • Added support for propagating non-numeric volume fields in .bib files to bibliographies Link

    • Improved sorting in bibliographies to take into account language conventions Link

    • Improved interoperability with CSL styles; for a full listing of changes, review the Hayagriva 0.10.0 changelog

    • Added support for setting directors on videos without a parent in Hayagriva YAML files Link

    • Improved handling of Anthos entries in Hayagriva YAML files by treating them as chapters in CSL Link

  • Footnotes

    • The link of a footnote is now within the superscript instead of around it, improving PDF tagging and HTML output Link

    • The thickness of the default footnote separator is now specified in font-relative instead of absolute units Link

  • Numbering

    • Added numbering support for Armenian numerals Link, Arabic Abjad numerals Link, and Tibetan numerals Link

    • Greek numbering now uses the modern Greek style Link

  • The par.first-line-indent property will now fold, meaning that partial dictionaries across different set rules or par calls are combined Link

  • Added list.marker-align property for defining how to align list markers Link

    • When omitted, it will default to the new baseline alignment (vertically), combined with end alignment (horizontally)

Text

  • Added support for variable fonts Link

    • The well-known variation axes ital, slnt, wght, wdth, and opsz are automatically set based on text weight, stretch, style, and size

    • Custom variations can be configured via the new variations parameter of the text function

    • When using a variable font with Typst, the suffixes “Variable”, “Var”, and “VF” should be omitted as Typst trims them to unify static and variable fonts into a single family Link (Minor breaking change)

  • Font features

    • The text.alternates parameter now accepts an integer in addition to a boolean to select stylistic alternates other than 0 and 1 Link

    • Parsing of tag names in text.features is now more strict Link (Minor breaking change)

  • Fixed that context text.font did not reflect the covers field Link

  • Fixed uneven CJK-Latin spacing in justified paragraphs Link

  • Fixed a bug where the lorem function would not produce the exact number of requested words Link

  • Improved translations for Swedish Link, Portuguese Link, Czech Link, Latvian Link, Slovak Link, Polish Link, Vietnamese Link, Finnish Link Link, and Welsh Link

  • Added font exception to avoid SimSun-ExtB being incorrectly merged with SimSun Link

  • Updated New Computer Modern fonts to version 8.1.0 Link Link Link Link Link

    • This update changes the default look of calligraphic letterforms in the math font; the previous style can be restored through show math.equation: set text(stylistic-set: 6)
  • Updated Unicode components Link

    • In particular, this fixed an issue with linebreaking of guillemets

Math

  • Layout

    • Improved layout of under/over elements like underbrace Link

    • Slightly improved spacing around math.op elements Link

    • In which situations cramped styles (with tighter spacing) are applied is now fully consistent with TeX and MathML Core Link

    • The size parameter of the lr function now consistently applies to middle delimiters in the same way it does to outer delimiters Link

    • The size parameter of the lr function now resolves relatively to the height of just the inner content; it does not take the delimiters into account anymore Link (Minor breaking change)

    • Glyph stretching is now always relative to the base glyph rather than a potentially already scaled version (e.g. due to display sizing) Link (Minor breaking change)

    • Fixed left/right alignment not being applied correctly due to spacing next to alignment points Link Link

    • The binom element now uses different OpenType constants for layout; though this does not lead to visible changes with most fonts Link

    • The default length and stroke width of math.cancel lines is now specified in font-relative instead of absolute units Link

    • Fixed potential misalignment in cases function Link

  • Text handling

    • Improved handling of multi-character symbols in math Link

    • Fixed that some glyphs did not stretch correctly in script sizes Link

    • Fraction, root, and under/over lines now respect text.stroke Link

    • Accents in math are now always rendered in front of their base if they overlap Link

  • The class function now applies the class only to its direct body rather than recursively Link (Minor breaking change)

  • More delimiter symbols (e.g. chevron.l) are now callable to produce an lr element Link (Minor breaking change)

  • Fixed various bugs with rendering of mathematical expressions that look like function calls but in reality aren’t (e.g. $pi(1, 2)$, since pi is not a function) Link

  • Fixed a bug with ordering of primes and nested attachments Link

Symbols

Layout

  • Baseline information is now retained in many more parts of the layout engine Link (Breaking change)

    • In particular, text contained in a box with an inset is now aligned with the text surrounding the box

    • This also fixes a bug where wrapping an inline equation in a box would shift its baseline

    • Similarly, using a block in an equation will keep the baseline intact

    • Last but not least, the marker/number and item of a list or enum are now properly baseline-aligned with the first line of the item even if the item is vertically larger than a normal line Link

  • Centering something in a list now centers based on the full available width rather than based on the maximum width of other list content Link

  • Page layout

    • Added bleed parameter to page element to set up bleed margins Link

    • Fixed the size of "us-executive" paper Link

    • Added warning for show page rules as they are unsupported Link

  • Paragraph layout

    • Fixed a bug where justified text could accidentally protrude into the margin when it ends with certain kinds of characters (e.g. a zero-width space) Link

    • Fixed a bug where first-line indent was applied at the start of a column even if all: false is set Link

  • Added support for spacing that is both weak and fractional Link

Visualize

  • Added support for spot colors (also called separation colors) Link

  • Tilings

  • Gradients

    • Added color.map.coolwarm for use with gradients Link

    • Fixed interpolation of gradient stops in Oklab color space Link

    • Fixed gradient angle handling for negative-size shapes Link

    • Fixed gradient strokes for lines and curves Link

    • Fixed parent-relative placement for stack and polygon Link

  • Fixed various bugs with rectangle strokes in combination with radii Link Link

  • Fixed a potential deadlock with font fallback in SVGs Link

  • Various improvements to SVG image handling (see the resvg 0.46 and 0.47 changelogs); in particular:

    • Added support for SVGs without top-level xmlns attribute

    • Added support for variable fonts in SVG using the font-variation-settings CSS property

  • Various improvements to PDF image handling (see the commits between d0b540f and 3483462 on hayro); in particular:

    • Added support for JPEG2000 (JPXDecode) and JBIG2 (JBIG2Decode) images

    • Improved parsing robustness for non-compliant files

    • Added support for blend modes

Introspection

  • Layout convergence issues now result in detailed diagnostics that help pin down the cause Link

  • Added within selector that matches elements that are contained within any elements matching an ancestor selector Link Link Link

  • Added at parameter to counter.display function Link

  • Improved how counter.display auto-selects the numbering to use Link

Data Loading

  • Added support for namespaces to xml function Link

  • Added hint when trying to read from a path that looks like a URL Link

  • Diagnostics for binary file loading failures now include file paths Link

  • The json function now emits a friendly error when the loaded JSON has a leading UTF‑8 BOM Link

Export

Bundle

HTML

  • Mathematical equations are now automatically exported to MathML (thanks to @mkorje) Link

    • MathML defines how to render an equation, but also preserves its semantics

    • If you’ve previously relied on show rules that use html.frame to render equations to SVG, try MathML output. Switching to it will improve the accessibility of your document (though rendering will be somewhat less consistent across browsers).

  • The box and block elements’ purpose is now aligned with paged export Link (Breaking change)

    • box is used to bring block-level content inline

    • block ensures inline-level content becomes block-level

    • Depending on the contained content, this may be achieved by setting the CSS display property or by wrapping in an additional <span> or <div>.

  • The rules of how paragraphs are grouped in HTML have been adjusted to fix cases where paragraphs would appear unexpectedly Link Link (Breaking change)

    • The list of HTML elements that can be grouped into paragraphs was tweaked (it now includes all phrasing content with the exception of elements that default to display: none)

    • This default can be controlled by wrapping an element in a box or block as appropriate

    • HTML elements that cannot be part of paragraphs (like a <div>) do not immediately force adjacent inline-level Typst content to be wrapped in a paragraph; rather, they are considered neutral for paragraph grouping

    • Paragraph creation is only forced by block-level Typst elements (as opposed to HTML elements). Built-in block-level elements like headings or images wrap the HTML elements they create in block elements to force adjacent inline content into paragraphs. Package authors should do the same to ensure paragraph creation is consistent between HTML and paged export.

  • The target function can now be used without the html feature flag (the rest of HTML export remains feature-flagged) Link

  • DOM structure and built-in show rules

    • The root <html> element now receives a lang attribute respecting what was configured for text.lang Link

    • The Typst image element now always emits width and height attributes on the generated HTML <img> element Link

    • Code in <pre> tags will now prefer raw newlines over <br> elements to encode line breaks Link

    • Fixed generated HTML for quote attributions Link

    • Fixed table cell show rules not working in HTML export Link

  • Serialization

    • HTML is now minified by default; use the --pretty CLI flag or the checkbox in the web app to pretty-print it Link
  • HTML elements

    • The attrs parameter on html.elem will now fold, meaning that partial attributes across different set rules or html.elem calls are combined Link

    • html.script and html.style only accept a string and not arbitrary content anymore Link (Breaking change)

  • Whitespace handling

    • HTML <br> elements now collapse adjacent Typst spaces Link

    • Fixed spans being emitted to protect whitespace from collapsing unnecessarily in some cases Link

PDF

  • Typst can now target multiple (compatible) PDF standards at once, e.g. PDF/UA-1 and PDF/A-2a Link

  • PDFs are now a bit more space-optimized at the cost of being harder to inspect with a text editor; use the --pretty CLI flag or the checkbox in the web app to pretty-print them Link Link Link

  • Labelled headings now result in named destinations even if they are not referenced Link

  • Graphics

    • Added support for more compositing features of COLRv1 fonts Link

    • Fixed rendering of gradients in LinearRGB, CMYK, and Luma color spaces Link

    • Fixed excessive sampling of linear gradients Link

  • Tagging

    • Added support for more specific artifact kinds in pdf.artifact; these are now internally used when appropriate Link

    • Fixed “invalid document structure” errors with complex list markers Link

    • Fixed wrong PDF tagging order for inline content outside of paragraphs Link

    • Fixed bounding box computations for stroked shapes in tagged PDFs Link

  • Standards compliance

    • Fixed potentially incompliant PDF files by emitting an error when PDF/UA-1 is requested but complying with PDF/UA-1 would require newer features than available in the current PDF version Link

    • Fixed potentially incompliant PDF 1.4 files by emitting errors when implementation limits are exceeded Link

SVG

  • SVGs are now minified by default; use the --pretty CLI flag or the checkbox in the web app to pretty-print them Link

  • Somewhat reduced the size of generated SVGs Link Link Link

  • SVG elements do not have the classes typst-frame, typst-doc, typst-group, typst-shape, and typst-text anymore Link (Minor breaking change)

  • Graphics

    • Fixed a bug where tilings could be incorrectly reused in multiple places Link

    • Fixed rendering of gradients in LinearRGB, CMYK, and Luma color spaces Link

    • Fixed handling of conic gradient angles Link

    • Fixed excessive sampling of linear gradients Link

  • Fixed positioning and sizing of color bitmap glyphs Link Link

  • Fixed sources of non-determinism in SVG export Link

PNG

  • Fixed handling of conic gradient angles Link

  • Fixed positioning and sizing of color bitmap glyphs Link

  • Fixed that negatively scaled text with equal x and y scale would turn invisible in PNG export Link

Command Line Interface

  • Added new typst eval subcommand to evaluate a Typst code expression from the CLI; this command supersedes typst query Link

  • Tracebacks for diagnostics are now more compact and readable Link

  • Added --pretty flag for producing human-readable output; output is otherwise minified by default (applies to HTML, SVG, and PDF, but not PNG) Link

  • Fonts

    • The output of typst fonts --variants is now more readable and informative; in particular, it also displays the paths of font files and, for variable fonts, variation axes Link Link

    • The CLI now discovers fonts lazily, saving time on operations that do not need fonts (like HTML export without frames) Link

    • Adobe Creative Cloud fonts are now discovered as system fonts Link

  • Dependency output

    • When writing to stdout while using --deps-format make (which is incompatible and thus fails), no empty Make dependency file will be emitted anymore Link

    • The JSON dependency format now includes information about outputs in addition to inputs Link

  • Path handling fixes on Windows Link

    • Reading from a path that contains a drive letter now results in an explicit error instead of the drive letter being silently ignored

    • Attempting to read from a path that contains a reserved filename (like COM1) now results in an explicit error

  • Non-Unicode input paths are not supported anymore Link (Breaking change)

  • The experimental --timings argument now requires an explicit file name instead of defaulting to record-{n}.json Link (Breaking change)

  • Added colors to --help/-h and typst info output Link Link

  • Fixed inconsistency in environment variable handling between typst info and typst compile Link

  • Fixed a bug with the injection of a live reload script when using typst watch with HTML export Link

  • Fixed a bug where local timezone information was taken into account even if a fixed date is set via --creation-timestamp or SOURCE_DATE_EPOCH, leading to irreproducible results Link

Tooling

  • Syntax highlighting

    • In math, parentheses used for grouping are now highlighted differently than ones intended for display Link
  • Autocomplete and tooltips

    • Autocompletion and tooltips are now aware of parameters of user-defined functions Link

    • Autocomplete descriptions and tooltips for font families are now more detailed and, for variable fonts, include variation axes Link

    • Function autocompletions in math mode now always prefer round parentheses over square brackets (which are not supported in math) Link

    • Fixed autocompletion and tooltips not working with argument lists in math mode Link

Deprecations

  • Certain unclear/ambiguous ways to write a raw language tag; these will now emit a warning in anticipation of an upcoming change to how they are parsed Link

  • Fallback to Arabic numerals for numbering systems that do not support the number zero (e.g. for "⓵") Link

  • Various symbols were renamed, see the deprecation section in the dedicated changelog for a full listing

  • Some citation styles that were renamed or superseded Link Link Link

    • council-of-science-editors is now called cse-citation-sequence-brackets-8th-edition

    • council-of-science-editors-author-date is now called cse-name-year

    • modern-language-association-8 / mla-8 is superseded by modern-language-association / mla

    • vancouver is now called nlm-citation-sequence

    • vancouver-superscript is now called nlm-citation-sequence-superscript

  • Undocumented array forms of enum and terms items Link

Removals

  • The path element, use curve instead Link (Breaking change)

  • The pattern type, use tiling instead Link (Breaking change)

  • The pdf.embed element, use pdf.attach instead Link (Breaking change)

  • The scoped functions cbor.decode, csv.decode, json.decode, toml.decode, xml.decode, yaml.decode, and image.decode; directly pass bytes to the top-level functions instead Link (Breaking change)

  • Various previously deprecated symbols, see the removals section in the dedicated changelog for a full listing (Breaking change)

Development

  • The typst-kit crate was completely reworked to make it easier to create a Typst World implementation Link Link

  • Diagnostic hints can now have spans (though typically they will be detached, which just means there isn’t a span) Link

  • Increased minimum supported Rust version to 1.92 Link

  • Moved Nix flake from typst/typst to typst/typst-flake, where it is now maintained by the community as a best effort Link

Migration guide

This section walks you through changes you may need to make to your existing documents to ensure compatibility with Typst 0.15.

Typst 0.15 removes definitions from the Typst standard library that were already deprecated in previous Typst versions. If you are still relying on those, also refer to the Typst 0.14 and Typst 0.13 migration guides.

Baselines

Typst now retains baseline information in more parts of the layout engine (most importantly for boxes, blocks, list items, and equations). This may lead to silent layout shifts. These are generally improvements, but if you’ve previously counter-acted bad-looking output through explicit adjustments, you may need to revisit those.

In particular, Typst will now set the baseline of a box to the baseline of its first line of content and use it to align the box with its surrounding text. This yields better-looking output out of the box.

// Typst 0.15+
Lorem #box(inset: 0.3em, stroke: 1pt)[ipsum] dolor.

// Typst 0.14 and below
Lorem #box(inset: 0.3em, stroke: 1pt)[ipsum] dolor.

File paths

If you are using Typst on Windows, you may have used backslashes in your file paths. This syntax is not supported anymore. Consistent use of forward slashes ensures your document compiles on all supported platforms.

// Typst 0.15+ ✅
#include "chapters/introduction.typ"

// Typst 0.14 and below ❌
#include "chapters\\introduction.typ"

Moreover, the Typst CLI does not support non-Unicode input paths anymore. Such paths are exceedingly rare today.

Math glyph stretching

In mathematical typesetting, glyphs frequently need to be stretched to the size of some part of an equation. This primarily applies to brackets, but also accents, arrows, and more. In Typst, this happens implicitly through matched delimiters or explicitly through the lr and stretch functions.

Typst 0.15 makes some adjustments to how ratios passed to these functions are resolved. Previously, a size of 200% passed to lr.size or stretch.size would be interpreted relative to a glyph size that was potentially already affected by display sizing. Now, ratios are always resolved relative to the base glyph size. In practice, this means that, to retain the same appearance, you may need to increase the target sizes you’ve configured for glyphs that are already larger out of the box in display style (e.g. integrals).

Math delimiters as functions

In Typst’s math mode, various symbols defined in General Symbols can be called like a function, either to be applied as an accent or to delimit body content. Typst 0.15 extends this handling to additional delimiters like chevron.l. This can change the output of existing calls, which would previously fall back to displaying the parentheses (which would rarely have produced desirable output in the case of delimiters).

// Typst 0.15+ ✅
$ chevron.l(x) $

// Typst 0.14 and below ⚠️
$ chevron.l(x) $

Math classes

The class function defines how part of an equation should be laid out (primarily the spacing around it). In Typst 0.14 and below, the class function applied recursively: If applied to a larger piece of content, all items in it would receive the class. In Typst 0.15, the class is only applied to the directly wrapped content. This is mostly a bug fix, but can lead to subtle layout changes.

Calligraphic letterforms in the default math font

With the update to New Computer Modern Math 8.1.0, the default calligraphic letterforms were changed. The previous letterforms can still be accessed by selecting stylistic set 6.

// Typst 0.15, default style.
$ R != cal(R) $

// Typst 0.15, with stylistic set 6.
// Reproduces the default style from Typst 0.14 and below.
#show math.equation: set text(stylistic-set: 6)
$ R != cal(R) $

Paragraphs, boxes, and blocks in HTML

Typst automatically collects inline-level content into paragraphs. In Typst 0.14 and below, the exact same rules were used to collect inline-level HTML elements (e.g. a <span>) into Typst paragraphs, which in turn result in <p> elements. This had the unfortunate effect that even use of the low-level typed HTML API could result in <p> elements appearing automatically. Consider the example below:

#html.div({
  html.span[Hello]
  html.div[World]
})

Where Typst 0.14 would insert an unexpected additional <p> element, Typst 0.15 yields the expected result:

<!-- Typst 0.14 and below ⚠️ -->
<div>
  <p><span>Hello</span></p>
  <div>World</div>
</div>

<!-- Typst 0.15+ ✅ -->
<div>
  <span>Hello</span>
  <div>World</div>
</div>

This change in output is achieved through a few new rules for how paragraphs are collected in HTML export. Previously, Typst would always categorize elements into either inline-level or block-level. It would then force inline-level elements into a paragraph whenever at least one block-level element was present in the same flow of content. In Typst 0.15, elements can instead be considered inline-level, block-level, or neutral:

  • Text, Typst box elements and HTML phrasing content (elements that are allowed as children of <p> elements) are considered inline-level1

  • All other HTML elements are considered neutral

  • Typst block elements are considered block-level

Neutral elements don’t force adjacent inline-level content into paragraphs. They can co-exist with inline-level content in a mixed flow. This ensures that usage of the typed HTML API does not result in extraneous paragraphs.

Meanwhile, Typst elements that are block-level out of the box (e.g. heading) now explicitly use a block in their default show rule to ensure that they still force adjacent inline-level elements into paragraphs. This ensures consistency in paragraph grouping across paged and HTML export. Package authors should also explicitly use blocks when creating HTML components that Typst should consider block-level.

To make this change possible, the way boxes and blocks behave in HTML export has been adjusted: Instead of unconditionally wrapping their contents in a <span> or <div>, they now do just what is necessary to ensure their contents are considered inline- or block-level by browsers. If they contain multiple children, they still create a wrapper element, but for just a single child, they instead configure the CSS display property. And if the single child already has the appropriate display property by default, it is fully omitted. Then, the effect of the box or block is limited to influencing Typst’s paragraph grouping.

HTML script and style elements

The typed HTML functions for the HTML script and style element previously accepted arbitrary body content and then only failed during HTML serialization if the content resulted in non-textual elements. In Typst 0.15, they instead only accept strings in the first place. Note that you can also use them with raw syntax by accessing the .text field.

// Typst 0.15+ ✅
#html.style("a { color: red }")
#html.style(
  ```css
  a { color: red }
  ```.text
)

// Typst 0.14 ❌
#html.style[
  a { color: red }
]

Classes in SVG export

Typst 0.14 and below would generate the class attributes typst-frame, typst-doc, typst-group, typst-shape, and typst-text on SVG elements in SVG export. These are no longer emitted. If you are using the typst-frame class to style html.frame elements in HTML export, you’ll need to adapt your style sheet.

Variable font family names

Typst aims to unify different fonts from the same family under a single family name. To that effect, it automatically trims common style suffixes like “Bold” or “Condensed” from font family names. Instead of selecting these through the name, they should be accessed through Typst’s built-in mechanisms (such as the weight and stretch parameters).

In Typst 0.15, the additional suffixes “Variable”, “Var”, and “VF” are trimmed to unify static and variable fonts into a single family. If you’ve previously used a font with any of these suffixes in its family name, you should now omit the suffix when specifying the font.

Upcoming raw language tag changes

In the next Typst version, we will make a change to how raw language tags are parsed. Should this upcoming change have an effect on your document, the compiler will already warn you today and suggest how to adjust your document to future-proof it against the change.

Numbering fallback for the number zero

Not all numbering systems can express the number zero. In Typst 0.14 and below, those would silently fall back to Arabic numerals for 0. This behavior is deprecated in Typst 0.15. Using zero with these systems will become a hard error in the future.

Tightened validation in some functions

The array.slice function, str constructor, and text.features parameter now perform stricter validation on their inputs. If you’ve previously passed invalid or nonsensical input, you will now receive an error.

Renamed citation styles

Typst 0.15 renames some citation styles to stay aligned with upstream CSL changes. If you are relying on any of these, the compiler will warn you and suggest the new name.

Renamed symbols

Typst 0.15 also renames a few symbols in General Symbols. If you are using any of these, the compiler will warn you and suggest the new name.

Contributors

Thanks to everyone who contributed to this release!

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  • GitHub avatar of {login}

  1. 1There are a few exceptions: Some elements like <script> are considered phrasing content by the HTML specifications, but don’t make sense in paragraphs as they default to display: none.
←

ChangelogPrevious page

→

0.14.2Next page

Hacker News · 131 赞 · 23 评 讨论 → 阅读原文 →

这条对你有帮助吗?