How to debug CSL output?

[Aaron Wenner]

I'm working on changes to the McGill Style Guide, which uses the CSL-M specification. I'm having trouble getting a set of authors to output correctly, and I'd like to be able to look under the hood to see which variables citeprocjs is grabbing. Is there a way to trace variables in a running instance of zotero to do this? 

Thanks!

AW

[Sebastian Karcher]

Not as live debug, but you can export CSL-JSON, which is what Zotero
passes on to citeproc.js
It's probably easiest, though, if you just ask. Note that for CSL-m
styles to work properly you should be using MLZ. Using vanilla Zotero
with CSL-m styles can cause all types of weird behavior.

> --
> You received this message because you are subscribed to the Google
> Groups "zotero-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to zotero-dev+...@googlegroups.com
> <mailto:zotero-dev+...@googlegroups.com>.
> To post to this group, send email to zoter...@googlegroups.com
> <mailto:zoter...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/zotero-dev.
> For more options, visit https://groups.google.com/d/optout.

[Frank Bennett]

As adamsmith says, the MLZ styles should be run in MLZ. To check the
variables seen by the processor, you can refer to the mapping table,
which live here:

http://fbennett.github.io/z2csl/diffMap.html

You can also view the CSL JSON for an item by selecting it in the MLZ
center pane, right-clicking, and selecting "CSL JSON" as the export
format.

Frank

>
> --
> You received this message because you are subscribed to the Google Groups
> "zotero-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to zotero-dev+...@googlegroups.com.
> To post to this group, send email to zoter...@googlegroups.com.