word could not communicate with zotero chrome

A list of translators and their code isįetched either from Zotero (c) or (d). Translators whose target regexp matches the URL of a given webpage are then further tested by running detectWeb() The background process maintains a cache of translators and performs the initial translator detection using URL matching. Which works as a middle-layer between the translation framework running in inject scripts (a) and Zotero (c) or (d). These custom classes talk to the background process (b) of the Zotero Connector for functionality outside the translationįramework, such as retrieving translator code and sending translated items either to Zotero (c) or (d). The translation framework shares some code with the Zotero codebase and provides custom classes concerning Instance orchestrates running individual translators for detection and translation. With a full Zotero translation framework. The Zotero Connector itself is split into two components:Ĭode running on the webpage and a background process.Ī) Injected scripts for individual webpagesĮach webpage is injected ( Chrome/ Firefox/ Safari) Saving resources to Zotero library is facilitated by two major components: the Zotero Connector running in the browserĪnd either the Zotero client or web api. The Connectors share code with Zotero desktop application, to support translation.Ī basic understanding of how translation works or at least the handlers it exposes in Zotero will be highly useful in

Safari Extension Frameworkįor Safari specifics see Zotero Translator Framework See Chrome Extension docsĪnd Firefox Extension docs for more information. The functionality exposed on Chrome and Firefox is provided by the Chrome extension framework, Technologies Chrome/Firefox Browser Extension Framework This section is a short overview of some of the complexities, to make it more accessible for newcomers. Zotero Connectors are built with standard tools, such as browser extension APIs, but the architecture is quite complex. Test files are located at src/common/test.

To run tests locally, build the extension with the -d flag, and then run

xar with patch for building Safari extensions.

Copy config.sh-sample to config.sh and modify as necessary.

Requirements for packaging extensions from the command line You will need to manually reload the extension OthersĪs files are changed, the connectors will be rebuilt automatically. scripts/firefox/run_xpi (in a different terminal window)Īs files are changed, the connectors will be rebuilt automatically and Firefox will reload the extension. See Automatic rebuilding/reloading Chrome on MacOSĪs files are changed, the connectors will be rebuilt automatically and Chrome will reload the extension.

Get and install the Mozilla web-ext tool.

Click 'Load Temporary Add-on' and select the build/browserExt/manifest.json file.

Click 'Load unpacked extension…' and select the build/browserExt directory.

Word could not communicate with zotero chrome