Laurenz

I'm not sure we'd want to support this, but the semantics of `selector.replacing(emph).or(strong)` could be well-defined: If it matches an `emph`, replace it, if it matches a `strong`, do not...

> I [already had the idea to make it a package](https://github.com/withoutboats/heck) Probably meant to link https://github.com/alerque/decasify/issues/10 instead of `heck` again.

Another thing is that `lower` and `upper` also work on content, not just strings. This would be harder to support for `capitalize`, but not supporting it is inconsistent.

I think, while not impossible, adding built-in capitalization is quite complex (due to both language support _and_ because it should support content for consistency). This would need more upfront design...

Having `.before()` and `.after()` for an unknown location result in empty output instead of the full list _might_ work. It's honestly hard to judge the consequences, but probably this would...

We could also have `before` give the empty list and `after` the full list, so that they are still dual. That would be consistent with returning position `(page: 0, x:...

It is new in 0.12 and documented on staging.typst.app/docs (since 0.12 is not out yet).

@gabriel-araujjo Nothing to do on your end, I just didn't get to reviewing this yet.

From an initial look: - It seems a bit inconvenient that the background does not fill the bleed area by default. This means creating a proper bleed-aware background effectively forces...

I don't remember all of the context anymore, but I remember looking into this a bit and I think they don't all really make sense for us. This warrants further...