Pewit AI Multilingual Translator

外掛說明

Plugin homepage, documentation and paid plans: https://pewitlabs.com/product-ai-multilingual-translator.html

Pewit AI Multilingual Translator lets you translate your multilingual content with WordPress 7.0+ AI connectors or your own AI provider key (BYOK) instead of paid WPML or Polylang machine-translation credits.

Fully functional and free

Every feature is free and fully functional — there is no language limit, feature cap or license gating. Connect via WordPress 7.0+ AI connectors (Settings Connectors) or bring your own API key (OpenAI, Anthropic Claude or Google Gemini) and:

  • WPML: list pending Translation Memory jobs, export/translate/import XLIFF, optional auto-import, string packages.
  • Polylang: translate posts directly — no Polylang Pro machine-translation credits required.
  • Translate only what is missing: gap detection for Polylang posts and XLIFF segments.
  • Bulk translation and background jobs for whole languages.
  • Review queue to approve translations before they are applied.
  • Cost estimate before you translate, glossary and site context for consistent terminology.
  • Email notification when a background job finishes.

Providers

  • WordPress 7.0+ AI Client (Settings Connectors) when configured, with BYOK fallback.
  • OpenAI, Anthropic (Claude) and Google Gemini — use your own API key.
  • You pay your provider directly for API usage.
  • Configurable model (default gpt-4o-mini) and API key test button.

You always use your own provider credentials (core connectors or BYOK). Requests go directly from your site to the provider you choose under that provider’s terms.

External services

This plugin connects to third-party AI providers to translate your content. Please review this before use.

You choose the AI provider in the plugin settings and use your own API key (BYOK), or on WordPress 7.0+ use the site-wide AI connectors (Settings Connectors) via the core AI Client. No data is sent to any provider until you trigger a translation or test the connection. Requests go directly from your site to the selected provider under your own credentials and that provider’s terms. Nothing is sent to the plugin author.

WordPress AI Client (WordPress 7.0+, when connectors are configured):
* What and when: translation uses wp_ai_client_prompt() so credentials stay in core (Settings Connectors). Source text, optional site context/glossary and translation instructions are sent to whichever provider the site administrator configured.

OpenAI API (https://openai.com):
* What and when: when you test the API connection or translate content (XLIFF segments or Polylang post fields) with OpenAI selected as the provider (BYOK fallback), the source text to translate, your optional site context/glossary and the selected model name are sent to OpenAI to produce the translation. Endpoints: https://api.openai.com/v1/responses and https://api.openai.com/v1/chat/completions.
* Data sent: the source text, optional context/glossary you configure, and the selected model name.
* Terms: https://openai.com/policies/terms-of-use — Privacy: https://openai.com/policies/privacy-policy

Anthropic (Claude) API (https://www.anthropic.com):
* What and when: only if you select Claude as the provider (BYOK fallback) — when you test the connection or translate content, the source text, optional context/glossary and the selected model name are sent to Anthropic to produce the translation. Endpoint: https://api.anthropic.com/v1/messages.
* Data sent: the source text, optional context/glossary you configure, and the selected model name.
* Terms: https://www.anthropic.com/legal/consumer-terms — Privacy: https://www.anthropic.com/legal/privacy

Google Gemini API (https://ai.google.dev):
* What and when: only if you select Gemini as the provider (BYOK fallback) — when you test the connection or translate content, the source text, optional context/glossary and the selected model name are sent to Google’s Generative Language API to produce the translation. Endpoint: https://generativelanguage.googleapis.com/v1beta/models/.
* Data sent: the source text, optional context/glossary you configure, and the selected model name.
* Terms: https://ai.google.dev/gemini-api/terms — Privacy: https://policies.google.com/privacy

Freemius (licensing & updates — https://freemius.com):
* What and when: used for plugin updates and optional anonymous usage diagnostics. Opt-in is optional.
* Terms: https://freemius.com/terms/ — Privacy: https://freemius.com/privacy/

Source code

All JavaScript and CSS shipped in this plugin (in assets/js and assets/css) is the original, hand-written, human-readable source. Nothing is minified, compiled, transpiled or generated by a build tool, so no separate source files are required — what you read in the plugin is the source. The only bundled third-party library is the Freemius SDK (vendor/freemius), whose source is available at https://github.com/Freemius/wordpress-sdk

安裝方式

  1. Upload the plugin ZIP through Plugins -> Add New -> Upload Plugin, or extract it to wp-content/plugins/pewit-ai-multilingual-translator/.
  2. Activate the plugin.
  3. Connect AI under Settings — WordPress 7.0+ Connectors (Settings Connectors) or your own API key (BYOK — OpenAI, Claude or Gemini).
  4. Pick WPML or Polylang and start translating.

The plugin folder must always be pewit-ai-multilingual-translator/ and the main file pewit-ai-multilingual-translator.php.

常見問題集

Do I need an API key?

On WordPress 7.0+ you can use Settings Connectors (core AI Client). Otherwise bring your own key for OpenAI, Anthropic Claude or Google Gemini. You pay your provider directly for API usage.

Do I need WPML or Polylang Pro?

No. You can translate WPML XLIFF jobs and Polylang posts with WordPress Connectors or your own AI key, without paid WPML or Polylang machine-translation credits.

Will my translations be reviewed before they go live?

You can enable the Review queue so translations are queued for approval before they are applied or downloaded.

1.0.11

  • Fixed: Plugin Check / review — resolve WPML TM loader via constants and active plugin paths (no hardcoded WP_PLUGIN_DIR folder names).
  • Fixed: sanitize download nonce with sanitize_text_field( wp_unslash() ) before wp_verify_nonce().
  • Changed: shared PEWIT Labs AI hub is no longer bundled here (optional when another suite plugin provides it); avoids non-slug text domain and foreign prefixes.

1.0.10

  • Added: shared PEWIT Labs AI settings hub when 2+ suite plugins are active (provider, API key, model, global context).

使用者評論

這個外掛目前沒有任何使用者評論。

參與者及開發者

以下人員參與了開源軟體〈Pewit AI Multilingual Translator〉的開發相關工作。

參與者

〈Pewit AI Multilingual Translator〉外掛目前已有 1 個本地化語言版本。 感謝全部譯者為這個外掛做出的貢獻。

將〈Pewit AI Multilingual Translator〉外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄

變更記錄

1.0.9

  • Fixed: readme “Tested up to” set to WordPress 7.0 for directory automated checks.

1.0.8

  • Added: WordPress 7.0+ AI Client integration — uses wp_ai_client_prompt() when site connectors are configured (Settings Connectors), with BYOK direct API fallback.
  • Fixed: removed bundled .po/.mo translation files from the wordpress.org package (translations via translate.wordpress.org); empty languages/ retained for Domain Path.
  • Fixed: Plugin Check — AI Client called via function_exists/call_user_func for WP 6.x compatibility; absint() in printf integer placeholders.

1.0.7

  • Changed: the wordpress.org build now ships with no license or plan gating code at all — every feature is unconditionally free. Plan checks live only in the separate premium build.
  • Added: “Source code” documentation noting all JS/CSS is human-readable source and linking the bundled Freemius SDK repository.

1.0.6

  • Changed: renamed to “Pewit AI Multilingual Translator” (new slug pewit-ai-multilingual-translator) for a distinctive directory name.
  • Changed: every feature is now free and fully functional — no plan gating (bulk jobs, auto-import and Claude/Gemini providers are available to everyone).
  • Added: External services documentation for OpenAI, Anthropic (Claude), Google Gemini and Freemius, including terms/privacy links.
  • Fixed: removed Google Fonts (no external font requests); admin uses a system font stack.

1.0.5

  • Fixed: Plugin Check advisory warnings — annotated direct DB queries (DirectQuery/NoCaching), WPML integration hooks, and validated XLIFF upload input.

1.0.4

  • Fixed: WordPress Plugin Check — i18n translators comments, filesystem helpers, prefixed LLM client class, removed manual textdomain loading.

1.0.3

  • Fixed: WordPress.org Plugin Check i18n compliance for shared LLM client.

1.0.2

  • Changed: Shared provider select with Pro gating for Claude/Gemini; inherits AIMT provider when borrowing API key.

1.0.1

  • Added: Gap detection for Polylang and XLIFF — translate only missing fields or segments.

1.0.0

  • WPML TM sync, string packages, review queue, cost estimate, suite pairing, i18n (7 locales).

0.1.1

  • AIMT API pairing; WPML XLIFF parser improvements.

0.1.0

  • Initial release: XLIFF bridge + Polylang post translation.