Laurenz
Ideally, I'd like to have neither a log file nor a littered terminal. It's not yet completely clear to me whether that is fundamentally in conflict with supporting a printing...
For more convenient inspection of values there is already the IDE integration with hover tooltips. The tracing would be specifically for people that want to work in the terminal or...
@nikhilweee If you don't already use them, I suggest trying the hover tooltips in the web app or Typst LSP for debugging. A logging function would still be useful of...
In the web app or if your editor supports LSP, you can view the values by hovering over a variable. Not sure what the neovim situation is.
That's odd. It might be that multiple consecutive uses of the same font family are ignored by the text processing pipeline, regardless of `covers`.
> I think the default behavior for them should be carefully thought out (might depend on text's lang property) What would be the default behaviour you propose, i.e. what would...
How would ```typ #let zh = langEnv(lang: ..., font: ..., ...) #lang(env: zh)[今天天气“很好”] ``` be different from ```typ #let zh = text.with(lang: ..., font: ..., ...) #zh[今天天气“很好”] ```
This is in principle intentional as it mirror Typst's paragraph behavior in paged export (observable via `show par` and in accessibility tags). You can use CSS to tweak it to...
This sounds like something Typst should transparently to optimize file size, without any user intervention. Also of note: If the objects are on the same page, then the compression algorithm...