kamiel79

WordPress has the function wp_localize_scripts for translation, but the strings passed to it have to be hard-coded. Until you parse the .js-files and scan for occurrences of _e() with a fast regexp, and localize them with the data using the WordPress _e-function to localize from a .po file. *Note*. Your po-file has to include strings from javascript files. To do this in Poedit, see http://stackoverflow.com/questions/16557327/how-to-generate-po-file-from-js-file-using-poedit.

Localize js

Provide translation function _e("") in javascript files.

ipetru21

iPoLlama gives you full control over WordPress translations without leaving your admin panel. Browse, edit, add, and delete translation strings for any installed plugin, theme, or WordPress core. Optionally connect to a locally running Ollama instance for AI-powered automatic translation.
Key features:
<ul>
<li>Browse and edit translations for any installed plugin or theme</li>
<li>Manage WordPress core translations</li>
<li>Add, edit, and delete individual translation entries (.po/.mo files)</li>
<li>Safe Mode (recommended): Store translations in the WordPress languages directory (<code>wp-content/languages/</code>), keeping original plugin and theme files completely untouched — translations survive plugin and theme updates</li>
<li>Direct Mode: Edit translation files inside the plugin or theme directory</li>
<li>Ollama AI Integration: Connect to a locally running Ollama instance to auto-translate strings (optional, disabled by default — all communication stays on your local machine)</li>
<li>Bulk auto-translation: Translate all untranslated strings for any plugin or theme in one operation, with live progress bar</li>
<li>Supports English (en_US), Romanian (ro_RO), and Russian (ru_RU) locales</li>
<li>Clean, WordPress-native admin interface</li>
<li>Works with standard <code>.po</code> and <code>.mo</code> gettext files</li>
</ul>
Translation modes explained:
Safe Mode stores your translations inside <code>wp-content/languages/plugins/</code> and <code>wp-content/languages/themes/</code>. WordPress loads from this location first, so your translations take effect immediately and are never overwritten by plugin or theme updates.
Direct Mode saves translation files inside the plugin or theme’s own <code>languages/</code> folder. This is useful when you control the plugin and want to ship translations with it, but translations may be overwritten on updates from the plugin author.
Ollama AI Translation (optional):
If you have <a href="https://ollama.com" rel="nofollow ugc">Ollama</a> installed and running locally, iPoLlama can connect to it for automatic AI-powered translation using local LLM models (such as Llama 3, Mistral, etc.). This feature is completely optional and disabled by default. When enabled, the plugin sends translation requests only to the Ollama URL you configure (default: <code>http://localhost:11434</code>). No data is sent to any external server or third-party AI service.
<h3>External Services</h3>
This plugin can optionally connect to a locally running Ollama instance for AI-powered translation. This connection is:
<ul>
<li>Disabled by default — must be manually enabled in Settings.</li>
<li>User-configured — you set the URL (default: <code>http://localhost:11434</code>).</li>
<li>Local only — Ollama runs on your own machine or server; no data is sent to any external server or third party.</li>
</ul>
<a href="https://ollama.com" rel="nofollow ugc">Ollama website</a> | <a href="https://ollama.com/privacy" rel="nofollow ugc">Ollama privacy</a>
No other external services are contacted by this plugin.

iPoLlama — AI Translation Editor

Manage translations for WordPress core, plugins, and themes directly from your admin panel. Optional Ollama AI auto-translation support.

Localize js vs iPoLlama — AI Translation Editor