Nick Bart

Perhaps unsurprisingly, I’d vote for the schema-oriented translation. This would indeed mean staying with the cleanest YAML, though I would dispute that it is the least transparent. At the risk...

A word of caution, though: In CSL, the `language` variable is supposed to hold one single language tag only, and the variable’s current unique role is to switch on conversion...

I’d still recommend not throwing away information, so I’d always import something like `american` as `en-US` rather than just `en`. (I wouldn’t add information, though, so `english` should just remain...

Right. From a CSL (processor) perspective, it currently does not matter if it’s `en` or `en-US`. That being said, `en-US` is a perfectly valid CSL `language` tag (see quote from...

Yes, an item with both `title` and `maintitle` would seem to be the right approach here.

> But then why not lodge this as a bug at the biblatex-apa project? This seems to be a clear omission in the package if this can only be achieved...

Try `Makie.jl` (see https://www.zotero.org/support/kb/rich_text_bibliography)

Late to the party, but one fundamental point was overlooked: treating `address` and `location` as distinct fields isn’t correct — in biblatex `address` is an alias of `location`. And the...

- `container-editor` for the editor(s) of a multivolume work (in the sense of CMOS 17e, 14.116–14.122) - `container-date` - Note that `collection-editor` already exists, but since CMOS strictly differentiates between...

@adunning Thank you. Fair enough. I’m still concerned that once users start populating the ‘Series Editor’ field in the Zotero GUI, or `collection-editor` in CSL-JSON or CSL-YAML with what by...