About this plugin
Georg-Kloster Slavonic Translator adds a compact translation form through the [wp_cu_translator] shortcode. It accepts Russian and German text, supports automatic language detection and lets the visitor choose accents, titlo, breathings and Slavonic numbers.
The plugin works without an API key using the free public Bible Desktop API tier. The free tier has usage limits to protect the service and control external AI processing costs. An optional API key can be configured for higher limits and additional authorized functionality.
No secret API credentials are bundled with the plugin.
The browser sends the form to WordPress. WordPress then contacts Bible Desktop server-to-server, so an optional Bible Desktop API key is never included in the page HTML or JavaScript.
The plugin name, description, settings page, messages and public form are available in English, Russian, German, Ukrainian and Polish. WordPress selects the language from its current locale.
Biblical references, exact verses, confidently recognized quotations and cached results can be returned without a new paid OpenAI request. Other texts use the model and spending limits configured by the Bible Desktop administrator.
Dictionary
The Dictionary tab searches the complete Church Slavonic dictionary supplied by Bible Desktop from Azbyka. Search by original or civil spelling, by Russian meaning, or by alphabet chapter. Definitions remain in Russian.
Meaning matches are dictionary references, not automatic sentence translations. Original spelling and source links are retained; morphology and audio are not generated.
Use [wp_cu_dictionary] for the standalone dictionary, [wp_cu_translator] for both tools, or [wp_cu_translator dictionary="no"] for translation only. Custom title attributes are supported.
Dictionary searches and article requests are sent by WordPress to the configured Bible Desktop service only after user interaction: /api/dictionaries/AZBYKA_CU_FULL/search, /api/dictionaries/AZBYKA_CU_FULL/alphabet and /api/dictionaries/AZBYKA_CU_FULL/entries/{key}. They transmit the search, mode, chapter or article key and the existing plugin client and installation headers; an optional configured API key also stays server-side. Successful responses may be cached by WordPress for five minutes.
The dictionary does not call OpenAI. ru/otechnik/Spravochniki/polnyj-pravoslavnyj-tserkovnoslavjanskij-slovar/. Clicking a source link opens Azbyka directly.
Shortcodes and settings
The plugin has its own WordPress admin menu. Georg-Kloster Slavonic Translator → Settings contains the Bible Desktop URL, optional API key, timeout and connection check. Georg-Kloster Slavonic Translator → Shortcodes lists each supported shortcode with a ready-to-copy example and explanation.
The same shortcode reference is also available at the bottom of the settings page.
External Services
This plugin relies on the external Bible Desktop service to translate text into Church Slavonic. com/api/v1/church-slavonic/translate. Request headers include the plugin client name, a non-secret installation UUID for usage quotas and a per-visitor HMAC identifier derived from the visitor’s IP address using a WordPress secret for rate limiting.
If configured, the optional Bible Desktop API key is also sent server-to-server. The visitor’s original IP address is not sent to Bible Desktop by the plugin; the service receives the WordPress server’s IP address as part of the network connection.
com/api/v1/church-slavonic/status. This request includes the plugin client name, installation UUID and optional API key, but no translation text or visitor identifier, and does not invoke OpenAI. Activation and viewing the translation form do not send requests to Bible Desktop.
ttf directly from Bible Desktop. This download reveals the visitor’s IP address and ordinary browser request information to that service. The plugin does not automatically load the remote font.
Bible Desktop may send submitted text to OpenAI to generate a translation. Biblical references, matching quotations and cached results may be processed without a new OpenAI request. The plugin itself does not connect directly to OpenAI.
com/policies/privacy-policy/.
If an administrator changes Bible Desktop URL, the API and font requests use that configured service instead. The administrator must check that service’s data handling and inform site visitors before offering the form.
The service is operated by Bible Desktop. com/pages/api-terms. com/pages/api-privacy.
These documents cover the API, translation data and optional OpenAI processing.
Privacy
The plugin does not create its own database tables and does not store translation text. The Bible Desktop URL, optional external API key, timeout and non-secret installation UUID are stored in the WordPress options table. Requests are subject to the logging, retention and AI settings configured on the connected Bible Desktop server.