EWA AI String Assistant for Loco Translate
| 开发者 | errorwebagency |
|---|---|
| 更新时间 | 2026年9月17日 23:21 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL v2 or later |
| 版权网址: | 版权信息 |
详情介绍:
EWA AI String Assistant for Loco Translate integrates state-of-the-art AI translation directly into the Loco Translate editor for WordPress plugins and themes.
On WordPress 7.0+, it seamlessly leverages the official, native WordPress AI Client (
wp_ai_client_prompt) and connectors configured centrally in WordPress Core, requiring zero plugin-level API keys. For WordPress 6.x or specialized setups, it provides an Advanced Direct Connection mode supporting OpenRouter (Anthropic Claude, OpenAI GPT, Google Gemini, DeepSeek, Meta Llama), locally hosted or remote Ollama instances, or any custom OpenAI-compatible API endpoint.
Key Features
- Native WordPress AI Client Support (WordPress 7.0+): Seamlessly uses the AI provider and credentials configured centrally in WordPress Core (Settings → Connectors) with zero plugin-level API keys required.
- Advanced Direct Connection Mode: Full support for OpenRouter, local or remote self-hosted Ollama instances, and custom OpenAI-compatible endpoints with idempotent settings retention.
- Direct Loco Translate Integration: Adds an "🤖 AI Translate" action panel to the Loco Translate PO file editor toolbar.
- Deterministic ID-Based AI Protocol: Uses stable entry IDs (
entry_X) and strict JSON envelope validation to guarantee 1:1 translation mapping without drift or alignment offset. - Strict Token & Placeholder Validation: Validates printf specifiers (
%s,%d,%1$s,%%), variable templates ({var},{{var}}), HTML tags, attributes (href,src), and HTML entities to prevent code corruption in translations. - Full Context Support (
msgctxt): Preserves gettext context disambiguation across the entire parsing and translation pipeline. - Native Plural Forms: Automatically requests and maps the exact number of plural forms (
nplurals) defined for the target locale. Partial plural forms are safely detected and completed. - Smart Filtering & Cost Optimization: Automatically skips non-translatable strings (numbers, URLs, pure placeholders, HTML tags) in memory without making redundant API requests.
- Atomic File Saving & Compilation: Writes PO files atomically using temporary files and filesystem locks, preserving file permissions and automatically compiling binary
.mofiles via WordPress POMO classes. - Real-Time Progress & Analytics: Monitor batch progress, elapsed time, strings translated, and token usage in real time.
- Direct & Transparent Communication: In WordPress AI Client mode, requests are routed by WordPress Core through the configured connector. In Direct mode, requests are sent from your server to the configured endpoint without any Error Web Agency-operated intermediary or proxy server. Services such as OpenRouter may route requests onward to their own model providers under their terms and privacy policies.
- 100% Free & Open Source: No paywalls, no trial limits, no feature restrictions.
- Loco Translate Disclaimer: Loco Translate is an independent project by Tim Whitlock. This plugin is an independent third-party add-on and is not affiliated with, sponsored, or endorsed by Loco Translate or its authors.
- Backup First: Always create a complete backup of your
.poand.mofiles before performing automated AI translations. - Review Translations: AI-generated translations are automated suggestions. Site owners are advised to review translated strings for context, grammar, and tone before deploying them on public or production sites.
- API Usage & Costs: If using paid third-party APIs (such as OpenRouter or commercial providers), monitor your usage and set spending limits on your provider dashboard. Developers are not responsible for third-party billing charges.
安装:
- Ensure the Loco Translate plugin is installed and activated.
- Upload the
ewa-ai-string-assistant-for-loco-translatefolder to your/wp-content/plugins/directory, or install the ZIP file via Plugins → Add New → Upload Plugin. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to Settings → EWA AI String Assistant in the WordPress admin menu.
- Choose your AI Connection Mode:
- WordPress AI Client (Recommended): Available on WordPress 7.0+. Uses credentials and connectors configured in Settings → Connectors.
- Advanced Direct Connection: Configure OpenRouter, Ollama, or a custom OpenAI-compatible endpoint directly.
- Go to Loco Translate → Plugins or Loco Translate → Themes, and open any PO translation file in the editor.
- Click the 🤖 AI Translate button in the editor toolbar, review the settings, and click Start Translation.
屏幕截图:
![Loco Translate PO file editor integration, displaying the dual language selectors ("From: [Source] ➔ To: [Target]"), the "🤖 AI Translate" toolbar action button, the active AI provider/model badge (e.g. "WordPress AI Client · deepseek/deepseek-v4.1-flash"), and the Gettext strings table.](https://cdn.jsdelivr.net/wp/ewa-ai-string-assistant-for-loco-translate/assets/screenshot-3.png)
常见问题:
Where do I find the plugin settings menu?
You can find the plugin settings by navigating to Settings → EWA AI String Assistant in the WordPress administrator sidebar menu. A direct Settings link is also available on the Plugins screen (plugins.php) right under the plugin name. When editing any .po file in Loco Translate (Loco Translate → Plugins or Loco Translate → Themes), the AI translation controls and status badges appear automatically directly above the Gettext translation table.
Does this plugin require Loco Translate?
Yes. EWA AI String Assistant for Loco Translate is an add-on that specifically extends Loco Translate. Loco Translate must be installed and active.
Is an API key required to use the plugin?
On WordPress 7.0+ with the native WordPress AI Client mode active, no plugin-level API key is required — credentials and connectors are managed centrally by WordPress Core (Settings → Connectors). In Direct Connection mode, an API key is required for OpenRouter or commercial OpenAI endpoints, but local Ollama instances require no API keys.
Does this plugin send data to third parties automatically?
No. No data is ever sent automatically or in the background. Data is sent to the configured AI provider only when an administrator explicitly initiates an action, such as testing the connection or translating strings.
Does the plugin overwrite existing translations?
No. By default, the plugin only translates untranslated strings. Existing translated strings in your PO file are preserved intact.
How does the plugin handle plural forms?
The plugin parses the PO file header for plural rules (Plural-Forms: nplurals=...) and sends both singular and plural source strings to the AI. The AI generates all required plural variations, which are validated against the target language's plural count before being written to the file.
What happens if an API request fails?
The plugin includes exponential backoff retry logic for transient errors (such as network hiccups or rate limits). If a permanent error occurs (e.g. 401 Invalid Key or 404 Model Not Found), the job halts cleanly and provides an actionable error message. Failed items are never falsely flagged as fuzzy.
How are translations saved?
Translations are written atomically to the .po file on your server using WP_Filesystem and standard locking mechanisms. The plugin then automatically compiles the binary .mo file using WordPress POMO classes, making the translations immediately available to WordPress.
Can I use this plugin for commercial websites?
Yes. The plugin is licensed under GPL v2 or later and can be used on any number of personal or commercial websites without restrictions.
Who is responsible for backups and translation accuracy?
The site administrator is solely responsible for creating and maintaining backups of translation files prior to using the plugin, and for reviewing generated translations for contextual correctness. The developers and Error Web Agency (EWA) assume no liability for machine translation errors, unintended file overwrites, data loss, or third-party API costs.
更新日志:
1.8.4
- Feature: Added bidirectional translation allowing translation from any source language (e.g. German, French, Spanish) into selected target language.
- Feature: Expanded language catalog to 180+ official WordPress locales, including all English dialects (US, UK, Canada, Australia, etc.).
- UI: Added dual language selector controls (From: [Source] -> To: [Target]) in the Loco Translate editor toolbar with automatic source language detection.
- Code Quality: Converted non-Yoda comparisons to strict Yoda conditions for complete WordPress Coding Standards (WPCS) compliance.
- Enhancement: Standardized all codebase comments, docblocks, and internal test assertions to English.
- Resolved Plugin Check nonce-analysis warnings by verifying the AJAX nonce directly in each AJAX callback before request data is processed.
- Added required translator comments for internationalized strings containing placeholders.
- Removed manual
load_plugin_textdomain()usage and rely on WordPress just-in-time translation loading. - Shortened the WordPress.org short description to stay within the 150-character limit.
- Retained the documented Advanced Direct Connection as an explicit opt-in fallback while WordPress AI Client remains the recommended/default transport on WordPress 7.0+.
- Fixed the Loco Translate Stop button contrast so its pause icon and label remain white and clearly visible against the red button in normal, hover, and disabled states.
- Fixed native WordPress AI Client execution by using the public fluent builder methods exposed through
WP_AI_Client_Prompt_Builder::__call(). - Removed silent fallback from WordPress AI Client mode to Direct Connection mode; the selected transport is now always honored.
- Corrected WordPress AI capability detection so missing compatible text providers are reported accurately without making a generation request.
- Updated Loco Translate editor labels so WordPress AI Client mode no longer displays stale Direct provider/model information.
- Clarified privacy and External Services disclosures, including local AI availability checks and retained-but-inactive Direct credentials.
- Completed additional internationalization and WordPress.org compliance hardening.
- Hardened editor notices so provider and server error messages are rendered as text instead of HTML, and normalized remaining AJAX input handling.
- Made the default OpenRouter endpoint explicit in source code to keep external-service behavior transparent to WordPress.org static and manual review.
- Integrated native WordPress AI Client (wp_ai_client_prompt) as the recommended and default AI transport for WordPress 7.0+.
- Added centralized AI Connection Mode settings (WordPress AI Client vs Advanced Direct Connection).
- Implemented modular transport architecture (WP_AI_Client_Transport and Direct_AI_Transport under AI_Transport_Interface).
- Added real-time WordPress AI status check and direct link to WordPress Connectors settings.
- Preserved complete backward compatibility for WordPress 6.x and retained existing direct configurations upon upgrade.
- Updated privacy policy declarations and external service disclosures for WordPress Core AI routing.
- WordPress.org compliance and remediation release.
- Updated plugin name to EWA AI String Assistant for Loco Translate and canonical slug to
ewa-ai-string-assistant-for-loco-translate. - Confined administrative dependency notices to relevant screens (
plugins.phpand settings screen) with dismissal capability in strict compliance with Guideline 11. - Fully namespaced and prefixed all WordPress registrations with 4+ character prefix
ewaas_(ewaas_*AJAX actions,ewaas-admin/ewaas-locoscript and style handles, nonces, and helper functions). Removed all legacyewa_runtime identifiers. - Implemented automatic one-time database migration from legacy
ewa_settingsto canonicalewaas_settingswith schema tracking (ewaas_schema_version). - Added comprehensive External Services documentation covering OpenRouter, Ollama, OpenAI API, and Custom OpenAI-compatible endpoints with direct links to official terms and privacy policies.
- Added WordPress Core Privacy Policy guide integration via
wp_add_privacy_policy_content()disclosing header usage attribution. - Evaluated WordPress 7.0 AI Client (
wp_ai_client_prompt) and retained direct provider adapter to preserve WordPress 6.0+ support, OpenRouter, local Ollama, and administrator-defined endpoint workflows. - Replaced NOWDOC with scanner-friendly array and implode structures in default prompt generation.
- Moved textdomain loading to
initaction hook.
- Implemented full
msgctxtcontext support and JSON-encoded deduplication keys across the entire pipeline. - Implemented deterministic ID-based AI request/response protocol (
entry_X) and strict JSON envelope validation. - Added
Translation_Validatorclass for strict tokenization and validation of printf formats, variable templates, HTML tags/attributes, and HTML entities. - Added plural form count validation against
npluralsand Strategy B partial plural regeneration. - Structured translation job state in
ewaas_job_{job_id}transients with idempotency request protection. - Stopped fuzzy flag misuse on API/network batch failures.
- Implemented machine-readable
WP_Errorclassification with early abort on permanent API errors (401, 403, 404). - Implemented atomic PO file saving with permission preservation and MO compilation error reporting via
WP_Filesystem. - Hardened canonical path validation against allowed WordPress language directories.
- Masked API key values in HTML DOM and added clear API key functionality.
- Added CLI automated test suite covering 32 pipeline assertions.
- Prepared the plugin for WordPress.org distribution.
- Standardized PHP requirement (7.4+) and WordPress requirement (6.0+).
- Refactored PHP codebase into namespaced architecture with global prefixing.
- Added automatic backward-compatible settings migration to
ewa_settings.
- Initial release of the AI translation add-on for Loco Translate.