Typst is a new markup-based typesetting system that is designed to be as powerful as LaTeX while being much easier to learn and use. [1.1]

References
  1. Type: Webpage. Title: “typst/typst”. Publisher: “GitHub”. Published (Modified): 2026-03-16T09:39:55.000Z. Accessed: 2025-03-18T08:55Z. URI: https://github.com/typst/typst.
    1. Type: File. Title: “README.md”.
      • Type: Text. Location: ¶1.
  • pastermil@sh.itjust.works
    link
    fedilink
    arrow-up
    4
    ·
    2 days ago

    The ability to load custom fonts comes to mind. I remember when I was converting my document from TeX to Typst was that I wasn’t able to just specify my .ttf file path.

    • Kalcifer@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      I don’t know what Typst’s custom font support was like in the past, but, currently [1], Typst does allow the usage of custom fonts:

      • The Typst CLI can use installed system fonts [1.2].
      • The Typst CLI can be passed directories that should be scanned for fonts through the --font-path argument or the TYPST_FONT_PATHS environment variable [1.3].
      • Fonts can also be uploaded directly to the web app [1.1].
      References
      1. Type: Text. Publisher: [Type: Webpage. Title: “text”. URI: https://typst.app/docs/reference/text/text/#parameters-font. Publisher: “Typst”. Location: “Reference”>“Text”>“Text”]. Accessed: 2026-03-19T04:32Z. Location: §“Parameters”>§“font”>¶4.
        1. In the web app, […] You can provide additional fonts by uploading .ttf or .otf files into your project. […]

        2. Locally, [in the CLI,] Typst uses your installed system fonts […]

        3. Locally, […] in the CLI, […] you can use the --font-path argument or TYPST_FONT_PATHS environment variable to add directories that should be scanned for fonts.