Sébastien SERRE

Grégory Viguier

Chouby

Emmanuel Hesry

Hugo

Marianne

Sylvain Schellenberger

<p>With Polylang fully integrated to WordPress and using only its built-in core features (taxonomies), keep steady performances on your site and create a multilingual site featuring from just one extra language to 10 or more depending on your needs. There is no limit in the number of languages added and WordPress’ language packs are automatically downloaded when ready.</p>
<h4>Features</h4>
<p>Depending on the type of site you have built or are planning to build, a combination of plugins from the list below might be of interest.<br />
All plugins include a wizard allowing to setup them in just a few clicks.</p>
<h3>Polylang</h3>
<p>Polylang and <a href="https://polylang.pro" rel="nofollow ugc">Polylang Pro</a> share the same core providing features such as:</p>
<ul>
<li>Translating posts, pages, media, categories, post tags, custom post types and taxonomies, RSS feeds; RTL scripts are supported.</li>
<li>The language is either set by the language code in URL, or you can use a different sub-domain or domain per language.</li>
<li>Automatic copy of categories, post tags and other metas when creating a new post or page translation.</li>
<li>Translating classic menus and classic widgets. Also accessible with <a href="https://wordpress.org/plugins/fse-classic/" rel="ugc">Site Editor Classic Features</a> in block themes.</li>
<li>Customizable language switchers available as blocks, classic widget or classic navigation menu item.</li>
<li>Compatibility with Yoast SEO.</li>
</ul>
<h3>Polylang Pro</h3>
<p>Helps optimizing the time spent translating your site with some very useful extra features such as:</p>
<ul>
<li>Better integration in the new Block Editor.</li>
<li>Language options available in the widget block editor.</li>
<li>Template parts translatable in the site editor (FSE).</li>
<li>Duplicate and/or synchronize content across post translations.</li>
<li>Improved compatibility with other plugins such as <a href="https://polylang.pro/doc/working-with-acf-pro/" rel="nofollow ugc">ACF Pro</a>.</li>
<li>Share the same URL slug for posts or terms across languages.</li>
<li><a href="https://polylang.pro/doc/translating-urls-slugs/" rel="nofollow ugc">Translate URL slugs</a> for categories, author bases, custom post types and more…</li>
<li>Machine translation with DeepL.</li>
<li>Export and import of content in XLIFF format for outsourced professional translation.</li>
<li><strong>Access to a Premium Support for personalized assistance.</strong></li>
</ul>
<h3>Polylang for WooCommerce</h3>
<p><a href="https://polylang.pro/downloads/polylang-for-woocommerce/" rel="nofollow ugc">Add-on</a> for the compatibility with WooCommerce which provides features such as:</p>
<ul>
<li>Translating WooCommerce pages (shop, check-out, cart, my account), product categories and global attribute terms directly in the WooCommerce interface.</li>
<li>Translating WooCommerce e-mails and sending them to customers in their language.</li>
<li>Products metadata synchronization.</li>
<li>Compatibility with the native WooCommerce CSV import & export tool.</li>
<li>Compatibility with popular plugins such as WooCommerce Subscriptions, Product Bundles, WooCommerce Bookings, Shipment Tracking and more.</li>
<li>Ability to use the WooCommerce REST API (available with Polylang Pro).</li>
<li><strong>Access to a Premium Support for personalized assistance.</strong></li>
</ul>
<h4>Switching from WPML?</h4>
<ul>
<li><a href="https://wordpress.org/plugins/wpml-to-polylang/" rel="ugc">WPML to Polylang</a> allows migrating from WPML to Polylang in a few clicks.</li>
</ul>
<h4>Credits</h4>
<p>Thanks a lot to all translators who <a href="https://translate.wordpress.org/projects/wp-plugins/polylang" rel="nofollow ugc">help translating Polylang</a>.<br />
Thanks a lot to <a href="http://www.alexlopez.rocks/" rel="nofollow ugc">Alex Lopez</a> for the design of the logo.<br />
Most of the flags included with Polylang are coming from <a href="http://famfamfam.com/" rel="nofollow ugc">famfamfam</a> and are public domain.<br />
Wherever third party code has been used, credit has been given in the code’s comments.</p>


Polylang

Works great for the translations of a WordPress website

Great plugin for i18n


If i need multilingual solution, only polylang


Good plugin


Faster and lighter than WPML, easy to configure and manage.


Fast, easy to use, reliable

works fine!


A few quirks here and there, but handles this complicated task very, very well, and with a good interface. 🫶


Simply marvelous


If you are using FSE then you cant translate templates and this makes the polylang useless


Not working with basic tool - native wordpress editor


The only issue is you cannot pair existing translations - or if there this feature already exists, I haven't found it. Otherwise it works well.


I am very happy with free version


Thanks to developers of this excellent work.Many filter hooks and functions to use for developers.Using built-in core tables on database is smart.


Great Work


It works very well, even with block themes, as long as it's used together with Site Editor Classic Features.



Thank you!


Works great, thank you!


Plugin cumpri com tudo que promete, simples de ser instalado e tudo que tiver duvida o forum resolve os problemas.



Vale muito a pena a versão free dele da para desenvolver muito projeto com ele.


Excelente


It does what it needs to do and is free!


Works great

Nice and easy!


This plugin works great for creating multilingual websites. I have been using it on a couple of my websites and it does its work perfectly.


Works like a charm!


Indispensable if you want to create a multilingual website. It integrates well with other plugins, eliminating unnecessary stress.


A true standard

Great plugin

Go multilingual in a simple and efficient way. Keep writing posts and taxonomy terms as usual while defining their languages all at once.

Doug Wollison

<p>The nLingual system allows for flexible multilingual support and translation management for WordPress. The system handles translations on a per-post basis, and can be set to be synchronized so changes to certain details on one are copied to the others. It offers you control over what can be translated and how, with a number of utilities available for 3rd party themes and plugins to utilize.</p>
<p><strong>nLingual 2 offers more robust control of translation management, better extensibility, and fixes to numerous core issues with the previous incarnation.</strong></p>
<h4>Translation for Almost Anything</h4>
<p>When setting up, you have control over what content supports translation. Any UI-enabled post types or taxonomies will be available for enabling, along with any navigation menus or sidebar locations registered. In addition, nLingual includes a LocalizeThis API that can be enabled on nearly any text field found in the admin, allowing just about any option or meta field to support separate values in each language.</p>
<h4>Simple Translation Creation and Management</h4>
<p>Assigning a language and translations to a post can be done on either the post editor screen or the posts management screen via Quick Edit (language can also be set for multiple post via Bulk Edit). You can also easily create new translations for existing posts on the fly; select “New [language] [post type]”, provide a translated title if you wish, and a new draft post will be created that is an exact copy of the original, ready for translation.</p>
<p>Translations are stored as independent posts, associated with their counterparts via a custom table. This allows you to translate the custom fields and other metadata associated with a post, and can assign them their own separate terms if desired. However, since there are plenty of occasions where you want the same information used between posts, nLingual offers <em>post synchronization</em>.</p>
<h4>Post Synchronization</h4>
<p>Each post type has it’s own rules for what data is synchronized between translations. When changes are saved to a post, it’s translations will be updated with to have the same data in the approved fields. This covers post data (e.g. date, status, and menu order), terms of specified taxonomies, and any meta fields you specify (e.g. the thumbnail image used, or a custom field value).</p>
<p><strong>Note: Currently, there is no per-post basis override for the synchronization rules</strong></p>
<h4>Free-form Language Management</h4>
<p>Admittedly, this is a feature few will need, but it’s a godsend to those that do. When setting up the languages nLingual will use, you can define you own languages from scratch or based on numerous presets. Each language has a number of fields:</p>
<ul>
<li>System Name: the name to use when referring to the language within the admin.</li>
<li>Native Name: the name of the language as it appears to native speakers on the site.</li>
<li>Short Name: a shorthand version of the native name, if applicable.</li>
<li>Locale: the language/country code to represent this language, as well identify the .mo file to load for text domains.</li>
<li>ISO Code: the official ISO 639-1 code for the language (2 letters)</li>
<li>Slug: the value to use when localizing a URL for the language (typically the same as the ISO code).</li>
<li>Text Direction: the text direction the language should be rendered in (Left-to-right or right-to-left). Will override the one specified in the text domain files.</li>
<li>Active State: whether or not to allow public access to content in the language.</li>
</ul>
<h4>Flexible Language Detection/Switching</h4>
<p>When the public-facing side of the site is loaded, nLingual will attempt to detect what language to serve the page in, using the following process:</p>
<ol>
<li>Use the language code in the <code>$_REQUEST</code> array for the specified key, if present.</li>
<li>Use the language code in either the subdomain or directory path, depending on method specified.</li>
<li>Use the browser’s preferred language setting and find the closest match, falling back to the default language.</li>
</ol>
<p>Once the language is set, it can be overridden by the language belonging to the requested post. This override is an configurable option.</p>
<p>In addition, the language can temporarily be switched to another by 3rd party theme or plugin code, similar to switching blogs in a multisite installation. When the language is switched, all text domain files will be reloaded in the desired language (the originals cached for when it’s restored), so any gettext translations will reflect the current language.</p>
<h4>Extensibility and 3rd Party Development</h4>
<p>In addition to numerous hooks to modify the functionality of nLingual, this plugin also includes some useful gettext utilities: <code>_f</code>, <code>_ef</code>, <code>_fx</code>, <code>_efx</code>, <code>_a</code>, and <code>_xa</code>, all of which are documented in <code>includes/functions-gettext.php</code>.</p>
<h4>Backwards Compatibility</h4>
<p>Although nLingual 2 has be rewritten from scratch, most if not all of the functions and filters are still available via the backwards compatibility feature, which is automatically enabled upon upgrading. However, any code that directly queries the database using the old nLingual language and translation tables will need to be updated to reflect the new structure.</p>


nLingual

This is plugin that I chose as a developer because of it's simplicity and minimal impact on page speed. I tested it along with several other much more famous plugins, and this gave me the best speed results. If some small issues with plugin would be resolved, I would give it a 5 star. I see a potential in it.

The plugin I like

A simple but flexible multilingual system. Features custom language management, post data synchronization and theme/plugin development utilities.

Polylang vs nLingual