PgBiel
PgBiel
Added some thoughts to the original issue (let's discuss there first): https://github.com/typst/typst/issues/6276#issuecomment-2973264952
This appears to be because the APA styles specify the term `editor-translator` in `...` as well as `editortranslator`, while we only support the latter. This is also the reason why...
Worth noting that fontdb is intentionally seeking to keep fontconfig support very minimal as they want to avoid depending on the full thing (which would lead to a C dependency)....
I was thinking about this before after a discussion in the Typst server. This could be a way to achieve what's proposed in #2403; in general, you could have "configure"...
For comparison and further discussion, there is already support for destructuring in the form of ```typ #let (name1, name2, name3: renamed) = dictionary ``` However, that doesn't allow for wildcard...
Regarding the design, in principle this is already possible for arbitrary content in any context using `state`, at least for the outline. I wonder, therefore, if the only further step...
Sure, we can have that.
I've recently had an idea and found that `{ set text(red) }` is actually pretty convenient to be able to "transport" rules... Maybe we should only warn if this is...
Thank you!
> There is a single drawback I could think of: previously, synthesized fields could be used in where selectors. Imo, this is a pretty significant drawback. And not all show-set...