Title: OpenLang – Translate WordPress with AI | Multilingual Plugin Author: Vynatics Published: 2026 年 8 月 19 日 Last modified: 2026 年 8 月 29 日 --- 搜尋外掛 ![](https://ps.w.org/vynlang/assets/banner-772x250.jpg?rev=3657352) ![](https://ps.w.org/vynlang/assets/icon-256x256.png?rev=3655017) # OpenLang – Translate WordPress with AI | Multilingual Plugin 由 [Vynatics](https://profiles.wordpress.org/vynatics/) 開發 [下載](https://downloads.wordpress.org/plugin/vynlang.2.8.13.zip) [即時預覽](https://tw.wordpress.org/plugins/vynlang/?preview=1) * [詳細資料](https://tw.wordpress.org/plugins/vynlang/#description) * [使用者評論](https://tw.wordpress.org/plugins/vynlang/#reviews) * [安裝方式](https://tw.wordpress.org/plugins/vynlang/#installation) * [開發資訊](https://tw.wordpress.org/plugins/vynlang/#developers) [技術支援](https://wordpress.org/support/plugin/vynlang/) ## 外掛說明 OpenLang is a free WordPress translation plugin for creating multilingual WordPress websites with automatic AI translation and full manual translation control. Translate WordPress without manually creating a separate page for every language. OpenLang discovers visible frontend text at runtime, stores translations for reuse, and serves language-specific URLs with a frontend language switcher. Use OpenLang when you need a multilingual WordPress plugin that combines automatic translation, manual translation editing, RTL support, Elementor language switching, translation caching, per-language typography, language-specific logos, CSV import/ export, and per-language CSS and JavaScript. All features included in this WordPress.org package are free to use and do not require a license key. #### Translate WordPress with AI or Manually OpenLang supports both automatic AI translation and manual WordPress translation in one workflow. For manual translation, OpenLang discovers visible frontend strings and common translatable attributes while pages are rendered. Administrators can review detected strings and edit translations directly from WordPress admin. For automatic translation, OpenLang can translate missing strings through its hosted AI translation service and save the returned translations for reuse. Automatic AI translation is enabled by default and can be disabled at any time under OpenLang > Settings. This gives site owners the speed of automatic website translation while keeping manual control over important wording, brand language, and corrections. #### WordPress Translation & Multilingual Features * Translate visible WordPress frontend text discovered at runtime. * Manage manual translations and detected strings from WordPress admin. * Automatically translate missing strings with hosted AI translation. * Create a multilingual WordPress website with multiple enabled languages. * Configure a default website language. * Serve language-specific URLs without manually duplicating every page. * Add a frontend language switcher with local translation caching. * Support both RTL and LTR page direction. * Add an Elementor language-switcher integration. * View translation coverage, runtime activity, analytics, and system status. * Configure typography separately for each language. * Use Google Fonts, system fonts, or uploaded WOFF, WOFF2, TTF, and OTF webfonts. * Set a different website logo for individual languages. * Import and export WordPress translations with CSV. * Add Custom CSS and Custom JavaScript for each language. * Use all included plugin features without license activation. #### Multilingual WordPress without Duplicate Pages OpenLang does not require administrators to manually create a separate WordPress page for every translated language. Instead, the plugin detects frontend strings, stores their translations, and serves translated content through language-specific URLs. Visitors can switch languages from the frontend language switcher while OpenLang uses stored translations and local caching where available. This workflow is useful for site owners who want multilingual website translation without maintaining duplicate page structures for every language. #### Automatic AI Translation for WordPress Hosted AI translation is enabled by default. When an enabled language has missing strings, OpenLang can send those strings to the managed translation service, receive translated text, and store the translations for use on the website. Administrators can disable automatic AI translation under OpenLang > Settings and use OpenLang as a manual WordPress translation plugin instead. Automatic translation requests are described in detail in the Privacy and External Services section below. #### Elementor Language Switcher, RTL & Language URLs OpenLang includes a frontend language switcher and an Elementor language-switcher integration for adding language selection to Elementor layouts. Language-specific URLs are used when visitors switch languages. OpenLang also supports both RTL and LTR page direction, making it suitable for multilingual websites that need right-to-left as well as left-to-right layouts. #### Per-Language Fonts, Logos, CSS & JavaScript A multilingual website may need more than translated text. OpenLang lets administrators customize the visual presentation for individual languages. Each language can use its own typography, Google Font, system font, uploaded webfont, website logo, Custom CSS, and Custom JavaScript. Generated language-specific assets are stored under `wp-content/uploads/vynlang/ assets/`. #### Translation Management & CSV Import/Export Detected WordPress strings can be reviewed and edited from the OpenLang translation manager. Administrators can also import and export translation data with CSV, making it easier to review translations externally, move translation data, or maintain larger translation dictionaries. #### Why Choose OpenLang? OpenLang is designed for WordPress site owners who want a flexible translation workflow without locking core plugin features behind license activation. * Free multilingual WordPress plugin with no license key required. * Automatic AI translation for speed. * Manual translation editing for accuracy and control. * No need to manually duplicate every page for each language. * Frontend language switcher and Elementor integration. * RTL and LTR language direction support. * Per-language typography and website branding controls. * CSV translation import and export. * Per-language CSS and JavaScript. * Translation coverage and activity visibility. #### Privacy and External Services OpenLang works locally for manual translation management. Hosted automatic translation is enabled by default and can be disabled under OpenLang > Settings. When enabled and missing strings need translation, OpenLang can send requests to: ``` https://vynatics.corsysltd.com/server/api/translate ``` A translation request can include source and target language codes, source strings and their MD5 dictionary hashes, the site URL and an MD5 hash of the site URL, and OpenLang and WordPress version numbers. This build has no license activation system and does not require or transmit an OpenLang license key. The public OpenLang REST dictionary endpoint is read-only. It returns locally stored translations and language assets; it does not call the hosted service and does not write translations to the database. If automatic translation is enabled and a visitor requests a language whose current page still contains untranslated strings, OpenLang uses the normal language URL so translation can occur through the server-side page-rendering workflow. If an administrator selects a Google Font, the visitor’s browser may load resources from `https://fonts.googleapis.com` and `https://fonts.gstatic.com`. Standard request information such as IP address, user agent, and requested font resource may therefore be sent to Google. Google Privacy Policy: https://policies.google.com/privacy Google Terms: https:// policies.google.com/terms Service provider: Vynatics Privacy policy: https://vynatics.corsysltd.com/openlang/ privacy-policy.html Terms: https://vynatics.corsysltd.com/openlang/terms-of-service. html Support: d.laeeq@corsysltd.com #### Security * Administrative data-changing actions require WordPress capability checks and nonces. * The public translation REST endpoint is read-only and accepts only bounded, validated MD5 hash lookups. * Managed translation requests require HTTPS and use WordPress safe HTTP requests with redirects disabled. * Custom webfont uploads are limited to administrators who can upload files. * CSV import is administrator-only, nonce-protected, limited to CSV files up to 10 MB, and does not execute uploaded content. * CSV exports neutralize leading spreadsheet-formula characters in human-entered text fields. * Custom code changes are administrator-only and nonce-protected; unfiltered JavaScript editing respects WordPress’s `unfiltered_html` capability. ## 螢幕擷圖 [⌊OpenLang multilingual WordPress dashboard showing translation coverage and status.⌉⌊ OpenLang multilingual WordPress dashboard showing translation coverage and status .⌉[ OpenLang multilingual WordPress dashboard showing translation coverage and status. [⌊Languages screen for enabling and managing website languages.⌉⌊Languages screen for enabling and managing website languages.⌉[ Languages screen for enabling and managing website languages. [⌊WordPress translation manager for reviewing and editing detected frontend strings.⌉⌊ WordPress translation manager for reviewing and editing detected frontend strings .⌉[ WordPress translation manager for reviewing and editing detected frontend strings. ## 安裝方式 1. In WordPress, go to Plugins > Add New and search for `OpenLang`, or upload the ` vynlang` plugin folder / ZIP. 2. Install and activate `OpenLang - AI Language Translator`. 3. Open OpenLang > Languages and enable the languages you want on your multilingual website. 4. Open OpenLang > Translations to review or manually edit detected WordPress strings. 5. Automatic AI translation is enabled by default; optionally review or disable it under OpenLang > Settings. 6. Configure the frontend language switcher and Elementor integration as needed. 7. Configure per-language Typography and Website Logo overrides if needed. 8. Use OpenLang > Custom CSS / JS for language-specific frontend code. ## 常見問題集 ### What is OpenLang? OpenLang is a free WordPress translation and multilingual plugin that combines manual translation management with optional automatic AI translation, language-specific URLs, RTL support, caching, a frontend language switcher, Elementor integration, and per-language design controls. ### Is OpenLang a free WordPress translation plugin? Yes. All features shipped in this WordPress.org package are available without license activation. ### How do I translate a WordPress website into multiple languages? Install OpenLang, enable your languages under OpenLang > Languages, then use OpenLang > Translations to review or edit detected strings. When automatic AI translation is enabled, OpenLang can translate missing strings and store the translations for reuse. ### Can OpenLang translate WordPress automatically with AI? Yes. Hosted AI translation is enabled by default so missing strings can be translated automatically. Administrators can disable automatic translation under OpenLang > Settings. ### Can I translate WordPress manually? Yes. OpenLang discovers visible frontend strings and lets administrators review and edit translations manually from WordPress admin. ### Can I create a multilingual WordPress site without duplicating every page? Yes. OpenLang serves language-specific URLs and stored translations without requiring administrators to manually create a separate WordPress page for every language. ### Does OpenLang include a language switcher? Yes. OpenLang includes frontend language switching with local translation caching where available. ### Does OpenLang work with Elementor? OpenLang includes an Elementor language-switcher integration for adding language selection to Elementor layouts. ### Does OpenLang support RTL languages? Yes. OpenLang supports both RTL and LTR direction handling. ### Does OpenLang use language-specific URLs? Yes. OpenLang serves translated website views through language-specific URLs when users switch languages. ### Can each language use different fonts or logos? Yes. OpenLang supports per-language typography, Google Fonts, system fonts, uploaded webfonts, and website-logo overrides. ### Can I add different CSS or JavaScript for each language? Yes. OpenLang includes per-language Custom CSS and Custom JavaScript controls and generates language-specific asset files. ### Can I import and export WordPress translations with CSV? Yes. Administrators can import and export translation data using CSV files. ### Is automatic AI translation required? No. Automatic AI translation can be disabled under OpenLang > Settings. You can continue using the plugin for manual translation management. ### Does OpenLang require a license key? No. This WordPress.org build has no license activation system, and all features included in the package are available without a license key. ## 使用者評論 ![](https://secure.gravatar.com/avatar/447a7fa300810410081eeda41b8cb82dee6e7a548e9a16c68a70095edd9d3a99? s=60&d=retro&r=g) ### 󠀁[Excellent Translation Plugin](https://wordpress.org/support/topic/excellent-translation-plugin-9/)󠁿 [Kamran A.](https://profiles.wordpress.org/kamiraj/) 2026 年 8 月 31 日 OpenLang makes creating a multilingual WordPress website simple and easy. The translation management is clean, fast, and easy to use. Highly recommended! [ 閱讀全部 1 則使用者評論 ](https://wordpress.org/support/plugin/vynlang/reviews/) ## 參與者及開發者 以下人員參與了開源軟體〈OpenLang – Translate WordPress with AI | Multilingual Plugin〉 的開發相關工作。 參與者 * [ Vynatics ](https://profiles.wordpress.org/vynatics/) [將〈OpenLang – Translate WordPress with AI | Multilingual Plugin〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/vynlang) ### 對開發相關資訊感興趣？ 任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/vynlang/)、查看 [SVN 存放庫](https://plugins.svn.wordpress.org/vynlang/)，或透過 [RSS](https://plugins.trac.wordpress.org/log/vynlang/?limit=100&mode=stop_on_copy&format=rss) 訂閱[開發記錄](https://plugins.trac.wordpress.org/log/vynlang/)。 ## 變更記錄 #### 2.8.13 * Replaced the Languages dashboard switch-position HTML select with the same visual card selector used by the setup wizard. * Added a prebuilt language quick-add selector to the Languages dashboard. * Prebuilt languages automatically populate code, language name, native name, RTL direction, and enabled state while custom language entry remains available. * Added duplicate-language detection that highlights and re-enables an existing language instead of adding a duplicate row. #### 2.8.12 * Converted setup wizard Save & Continue, Skip this step, and Back navigation to AJAX so steps change without reloading the WordPress admin page. * Added AJAX-rendered step refreshes so languages saved in step 1 are immediately available to Typography and Website Logo steps. * Added browser Back/Forward history synchronization for setup steps. * Reinitialize Google Font and Media Library controls after dynamic wizard step changes. * Retained the existing admin-post flow as a no-JavaScript fallback. #### 2.8.11 * Refined setup wizard layout to a single-column app grid, 950px content width, and reset active-step margin. #### 2.8.10 * Removed the OpenLang dashboard header from the setup wizard so onboarding starts directly with the wizard content. * Kept Save & Continue / Finish Setup button text and Dashicons white across normal, hover, focus, and active states. #### 2.8.9 * Fixed setup wizard access by registering onboarding as a hidden WordPress admin page without removing its access mapping. #### 2.8.8 * Added a guided setup wizard that opens after plugin activation. * Added four onboarding steps for languages, floating switcher position, per-language typography, and per-language website logos. * Languages configured in the first step are automatically available in the Typography and Website Logo steps. * Added per-step skip controls and a full “Skip setup wizard” action. * Reused the existing OpenLang language, typography, logo, cache, and Media Library settings so wizard changes remain editable from the normal dashboard pages. #### 2.8.7 * Changed Custom CSS and Custom JavaScript from site-wide code to per-language assets. * Added per-language CSS/JS storage, language switching in the editor, DOM-ready and document-head JavaScript options, AJAX load/save/reset, and unsaved-change protection. * Generate cache-busted files under `wp-content/uploads/vynlang/assets/css/{language}. css` and `wp-content/uploads/vynlang/assets/js/{language}.js`. * Enqueue generated files only for the active server-rendered language and dynamically replace them during client-side language switching. * Preserve 2.8.6 site-wide custom code by migrating it into the default language on upgrade. * Kept custom-code changes nonce/capability protected and retained WordPress `unfiltered_html` enforcement for JavaScript editing. ## 中繼資料 * 版本 **2.8.13** * 最後更新 **3 天前** * 啟用安裝數 **少於 10 次** * WordPress 版本需求 ** 6.3 或更新版本 ** * 已測試相容的 WordPress 版本 **7.1** * PHP 版本需求 ** 7.4 或更新版本 ** * 語言 * [English (US)](https://wordpress.org/plugins/vynlang/) * 標籤: * [ai translation](https://tw.wordpress.org/plugins/tags/ai-translation/)[automatic translation](https://tw.wordpress.org/plugins/tags/automatic-translation/) [language switcher](https://tw.wordpress.org/plugins/tags/language-switcher/) [multilingual](https://tw.wordpress.org/plugins/tags/multilingual/)[translation](https://tw.wordpress.org/plugins/tags/translation/) * [進階檢視](https://tw.wordpress.org/plugins/vynlang/advanced/) ## 評分 5 星，滿分為 5 星 * [ 1 個 5 星使用者評論 ](https://wordpress.org/support/plugin/vynlang/reviews/?filter=5) * [ 0 個 4 星使用者評論 ](https://wordpress.org/support/plugin/vynlang/reviews/?filter=4) * [ 0 個 3 星使用者評論 ](https://wordpress.org/support/plugin/vynlang/reviews/?filter=3) * [ 0 個 2 星使用者評論 ](https://wordpress.org/support/plugin/vynlang/reviews/?filter=2) * [ 0 個 1 星使用者評論 ](https://wordpress.org/support/plugin/vynlang/reviews/?filter=1) [撰寫評分](https://wordpress.org/support/plugin/vynlang/reviews/#new-post) [查看全部使用者評論](https://wordpress.org/support/plugin/vynlang/reviews/) ## 參與者 * [ Vynatics ](https://profiles.wordpress.org/vynatics/) ## 技術支援 使用者可在技術支援論壇提出意見反應或使用問題。 [檢視技術支援論壇](https://wordpress.org/support/plugin/vynlang/)