Nick Bart

> Order is then determined by the `a/b/c` postfix, not the `editortype`? Right. (In fact, `editor` without a postfix comes first, so the order is, `editor`, `editora`, `editorb`, `editorc`; same...

FWIW, “CSL-M styles”, aka “Juris-M styles: extended CSL styles with jurisdiction support”, aka “jm-styles“ from the [official repository](https://github.com/Juris-M/jm-styles) whose names start with `jm-` all contain ``, and it seems [this...

I agree.

My view is that (at least) URL and DOI fields should be verbatim fields in any biblio database format. They certainly are in biblatex and in CSL JSON. Actually, I...

> [YAML] isn't a dedicated bibliography format. True, but citation data including `URL` and `DOI` fields can only ever appear inside a `references` field – isn’t that as dedicated a...

> But I like to avoid surprising special exceptions when possible; consistency is good. I won’t argue with that. However, it seems two different, conflicting ideas of concistency are involved...

Going minimalist would be a start. `URL` and `DOI` are the obvious ones. (ISBN, ISSN, PMID, and PMCID all follow standardized patterns not likely to be (mis-)parsed as markdown, but...

I tried this both with the Zotero add-in for LibreOffice, and by right clicking on an item in Zotero, choosing “Create bibliography from item“, and pasting this into a LibreOffice...

I still think that allowing markdown in URL and DOI fields is not ideal. Continuing to parse these fields as markdown would mean that all users would have to check...

Many thanks for providing some background. Actually, I didn't realize that it's not entirely trivial to prevent pandoc parsing specific parts of the input as markdown. > A slightly less...