Laurenz

Feel free to report it upstream, though if you know a bit of Rust ideally check first that it indeed happens with just a bare fontdb as well.

> Would it be possible for typst to use fontconfig directly rather than relying on fontdb? I'm not sure whether it would be desirable to go our own ways as...

I am not per se against using system interfaces where appropriate (e.g. also using DirectWrite and Core Text on Windows/macOS), but I am concerned both with - Having heavily diverging...

> One pretty straightforward solution would be a module(dict) constructor to mirror the already existing dictionary(mod) constructor That appears like the much cleaner solution to me. A dynamic module, in...

I'll close this in favor of https://github.com/typst/typst/issues/6419 as, if at all, I'd like to support this through dynamic module construction rather than dictionaries.

The [alphanumeric](https://github.com/typst/hayagriva/blob/main/styles/alphanumeric.csl) CSL style doesn't have a `citation-locator`, which regressed this.

The reason is that invisible metadata is generated through `locate` to which the page set rule doesn't apply. It's a bit unfortunate interaction. Note that putting large parts of the...

Rawless reproduction (on main, not 0.11.1): ```typ #lorem(630) #block( fill: luma(230), inset: 10pt, width: 100%, block[a \ b], ) ``` (Raw also produces an internal block.) I think the cause...

Symbols aren't functions though. The fact that symbols are callable doesn't mean that function should be implicitly callable. There is no implicit calling in Typst so far.

Symbols and functions live in the same scope. There can only be one value with a given name in a scope.