Denis Maier

I don't know about other common combinations besides volume and page. > How could something like this be approached within the CSL framework? Biblatex knows `pagination` and `bookpagination` fields. We...

Looks like there is one major caveat: volume can be part of the item metadata, or it can be one of the locators. Both situation may require different solutions. Regarding...

> I don't think that's necessary. It's covered by my example above. If there is volume+page, it will render "volume:page". If there is volume as metadata and page as locator,...

> > I don't think that's necessary. It's covered by my example above. If there is volume+page, it will render "volume:page". If there is volume as metadata and page as...

Yeah, a changelog is necessary. I'm not sure doing this automatically is the best way in that case.

Question @bdarcus: Is this about a changelog for the released version (like the linked release notes)? Or about a work in progress log?

> * **deprecate** (patterns or strings dropped from schemas, with processing implications) We'll need to settle on the meaning of "deprecate"... Is it: "Removed and invalid from now on." Or:...

Marking this as deferred for now. I think the idea is interesting and ambitious, but I don't really know how a good solution could look like.

> But another way to solve the labor problem is what I've long advocated: #244. MakeCSl is certainly useful, but I think it solves a different problem, i.e. quickly building...

> This might have promise, but what about a first step, which is simply to load the macros for reuse? Maybe a start, but does that really help? You'd still...