ensko
January 2, 2026, 10:34am
1
This is equal parts a template you can copy if you plan to make your own 2026 Bingo card, and a whimsical unofficial Typst Bingo card. It’s too small for a Universe template, but you can simply copy the project:
The entries were drafted yesterday on the Discord; if one of these comes to pass, use either the app’s comment function (the link has review permissions), this topic, or the Discord thread to make me aware, and I will strike through the box.
You can also customize the bingo card (if you copy the project); check out the code wrapped in //////////// at the start of the file:
replace seed = none with e.g. seed = "SillyFreak" to shuffle the entries around. (If you want to later claim “Bingo” here, I suggest you use your Forum or Discord username, to prove you didn’t just brute force a good seed)
Color boxes according to how likely you think they are: in prediction(none)[...], change the nones to a string or percentage; "" means 0%, "#####" means 100% (only the length counts, makes it easier to adjust percentages quickly)
Hope you like the idea
23 Likes
ensko
January 17, 2026, 7:38pm
2
First square is crossed off!
(And another will be marked after the meetup at the end of February!)
5 Likes
Andrew
March 1, 2026, 10:43am
4
6 Likes
ensko
March 1, 2026, 12:43pm
5
I already forgot that square existed
ensko
April 11, 2026, 9:24pm
6
Typst is on Wikipedia [1]
5 Likes
ensko
May 12, 2026, 1:49pm
7
Major feature contributed by community:
main ← mkorje:mathml
opened 09:35AM - 22 Nov 25 UTC
Supersedes #7206.
## Notes
### Stylesheet
To have the output in a brows… er match Typst's paged output exactly, we'd ideally override parts of the [user agent stylesheet](https://www.w3.org/TR/mathml-core/#user-agent-stylesheet) instead of having to supply things to each instance of an element. Since doing the former isn't possible yet and the latter isn't great (we are initially focusing on semantics after all), I'm ignoring all of this stuff. There is one exception, though: I need to disable the `text-transform: math-auto` property for `mi` (by using the `mathvariant="normal"` attribute) to stop the browser from auto italicizing things.
## Questions
### What Should the Width of a Space Be?
We occasionally need to emit a single space, but we cannot obtain the font's space width! So we may need to choose something. Some choices I've found elsewhere:
- `4/18em` in https://github.com/jgm/texmath/blob/aee6b494595a58dbbf769264061876778f7aa269/src/Text/TeXMath/Shared.hs#L251C1-L251C37
## Resources
### Specifications
- [MathML Core](https://www.w3.org/TR/mathml-core/)
- [MathML 4.0](https://www.w3.org/TR/mathml4/)
- [MathML 3.0](https://www.w3.org/TR/MathML3/)
### Other Implementations
- [LuaMML](https://github.com/latex3/luamml/)
- [LaTeXML](https://math.nist.gov/~BMiller/LaTeXML/)
- [MathJax](https://www.mathjax.org/)
- [KaTeX](https://katex.org/)
- [Temml](https://temml.org/)
- [AsciiMath2ML](https://johtela.github.io/asciimath2ml/)
- [TeXZilla](https://fred-wang.github.io/TeXZilla/)
- [texml-to-html](https://github.com/AmerMathSoc/texml-to-html)
### Fonts
- https://mathfonts.github.io/
## Browser Problems
Below I collect issues in the main 3 browser engine's MathML implementations that cause the MathML generated by this PR to display incorrectly. Whilst I do think we should work around these where possible, for my initial implementation I have not done so.
### Gecko
### Blink
### WebKit
4 Likes
Don’t forget to check “Docs rewritten in Typst”
main ← docs-in-typst
opened 05:05PM - 20 Apr 26 UTC
This PR ports the official documentation to be itself written in Typst. This aff… ects both the longer-form content (like language explanations and guides) and in-source documentation for the standard library.
### The highlights of this work
- There is now an official PDF version of the documentation. You can view a [preview version here](https://files.typst.org/typst-docs-preview.pdf) (Note: The file weighs ~30MB).
- Both the website and PDF version of the documentation can now be fully built from the open-source code in this repository.
- Both versions can now be edited with hot reload, even for in-source (i.e. in-Rust) documentation. The previous (closed source) build process was a much larger hassle. This helps both with contributing and reviewing docs changes.
- We are not anymore limited by Markdown for documentation content. While this PR's focus is purely infrastructural, this paves the road for expanding and improving the docs content in various ways.
### How to use it?
Analogously to the test runner shell alias `cargo testit`, there is now a `cargo docit` command that lets you work with and build the docs. There are more details in `docs/README.md` (in the PR branch), but here are the most relevant things you'll want to do:
```bash
# Build HTML version into docs/dist/site
cargo docit compile
# Build PDF version into docs/dist/docs.pdf
cargo docit compile --format pdf
# Serve HTML version on http://localhost:3000
cargo docit watch
# Continuously build PDF version into docs/dist/docs.pdf
cargo docit watch --format pdf
```
The docs build system is its own crate with a small subslice of the main CLI's command surface because it can't be built with a stock Typst CLI. It depends on various docs-specific additions.
### Status
The PR is almost finished. There are four main things left to be done:
- I have to integrate this into typst.app's build process.
- The PR is sort-of blocked on https://github.com/typst/typst/issues/5907. Since this issue is crucial to fix anyway, I'll try to do so before landing this. The PR contains a workaround in a WIP commit, but I'd like to drop that one.
- I wanted to get the PR up today, but I do want to self-review and polish some more. There'll probably be lots of typos.
- Adding new fonts affected some tests. I'll need to double-check those. The relevant commit is marked as WIP.
### On the implementation
The PR (and its commit history) is roughly structured into the following steps:
- Preparatory work: Minor changes across the codebase that I needed.
- Fixes for various minor issues with the old docs content that I noticed during conversion.
- Deletion of the old docs infrastructure.
- Mass conversion of the docs (both the Markdown files and the in-source doc comments). I wrote a custom tool to perform the mass conversion, which I've published at https://github.com/typst/docs-md-to-typ for posterity.
- The Rust side of the new docs infrastructure.
- Typst-based docs components. There's some supporting Rust code in `docs/src`, but the bulk is implemented in Typst.
- Typst markup/code that ties together the mass-converted contents and new components to realize the docs content.
- CI + README
I've documented the more complex subsystems (e.g. the cross referencing system) in the Typst sources where they are implemented (e.g. `docs/components/linking.typ`). Ideally, we'd want to add more docs on subsystems relevant for docs writing and also on how to _write_ good docs in the first place to the docs README. I've left this as future work.
### How can you help?
Play around with it and let me know about issues! I've tried my best to avoid regressions in the HTML version and to have the PDF version somewhat polished, but there will definitely be issues with both versions that went unnoticed. If you spot something, just leave a review comment here or, if the PR is already merged, open an issue.
### Linked issues
- Closes https://github.com/typst/typst/issues/2089
- Closes https://github.com/typst/typst/issues/6704
- Closes https://github.com/typst/typst/issues/7200
- Fixes https://github.com/typst/typst/issues/6930
- Fixes https://github.com/typst/webapp-issues/issues/551
- Fixes https://github.com/typst/webapp-issues/issues/741
- Fixes https://github.com/typst/webapp-issues/issues/813
ensko
May 12, 2026, 8:19pm
9
It counts when the new docs are published, on the next release. At least that’s how I decided to handle it
3 Likes
