Best way to develop/bugfix translators?

1 view
Skip to first unread message

Michael Risch

unread,
Mar 21, 2026, 4:06:42 PM (18 hours ago) Mar 21
to zotero-dev
Hi all -

I finished an alpha of my juris-m indigobook replacement plugin. I am going to test it out on a non-syncing repository (though it's pretty non-invasive, but I don't want to mess up anyone's juris-m extra fields data). If anyone wants to give that a shot, let me know.

In the meantime, I was all excited to use the new version and all the updated translators, except they are all just as bad for legal stuff as they are with Juris-m - lexis, westlaw, and hein are all broken. 

What is the best way to develop/debug these? Do I have to fork all of zotero? All of the translators directory? Can I just fork the files I want to work on and somehow patch them locally to test before making a pull request without having to compile all of them?

Thoughts appreciated.

Regards,
Michael Risch

Dan Stillman

unread,
Mar 21, 2026, 4:34:44 PM (17 hours ago) Mar 21
to zoter...@googlegroups.com
https://www.zotero.org/support/dev/translators

(Short version: Clone the translators and point the Translator Editor
within Zotero at it.)

Michael Risch

unread,
Mar 21, 2026, 4:52:12 PM (17 hours ago) Mar 21
to zotero-dev
haha, rtfm. Thanks. I'll do more research next time
Reply all
Reply to author
Forward
0 new messages