zanmaitypstlisted

# typst A browser paginates a web page. It was never a typesetting system, and the one thing it cannot do is the thing a document is made of: a full-width element that no longer fits is pushed to the next page and the rest of the current page is left white, because text does not flow around it. Measured on a real 62-page piece: 22 pages under 70 percent coverage, one of them 97 percent white. That is not a composition problem to work around, it is the wrong tool, and this is the right one. Everything below was compiled and looked at, not read somewhere. Where a version matters, the pin in the tool register is the one it was verified on. ## What it gives you that a browser does not - **Page floats.** A block placed with `float: true` moves to where it fits while the text keeps filling the page it came from. - **Columns with real flow**, so content continues from one column to the next. - **Hyphenation from dictionaries**, per language, correct German breaks. - **Folios and totals** without stamping a second file over the first. - **Colour to the page edge** without the silent full-document downscale a browser does when a padded box exceeds the page. - Seconds per run for a document of this size. ## The two traps **The font is silently the wrong one.** Set the family and pass the brand's own font folder: `typst compile --font-path <brand fonts> in.typ out.pdf`. Without it Typst falls back to its own default face, and if the brand font happens to be installed on the ma