michelanjos

Easy I18n is a lightweight inline translation plugin that lets you add multilingual content directly in your HTML, templates, or Elementor blocks — without duplicating pages or dealing with complex UI.
It focuses on a simple and modern workflow: 
– Use HTML normally 
– Mark text with <code>data-i18n</code> 
– Add translations in a clean admin interface 
– Show a minimal frontend language switcher 
– Done.
This makes it ideal for: 
– Landing pages 
– SaaS sites 
– Marketing funnels 
– Elementor layouts 
– Static content 
– Headless-style frontends 
– Low-maintenance multilingual sites
No page duplication. 
No heavy UI. 
No lock-in.
Just fast, simple multilingual content.
<h3>Features</h3>
<ul>
<li>Inline translations with <code>data-i18n</code></li>
<li>No page duplication</li>
<li>Works with Elementor and static HTML</li>
<li>Lightweight language switcher (via shortcode)</li>
<li>Designer-friendly admin UI</li>
<li>Supports HTML inside translations</li>
<li>Automatic language fallback</li>
<li>Multi-language support in admin UI</li>
</ul>
Admin available in: 
– Arabic 
– Chinese (Simplified) 
– Dutch 
– English 
– French 
– German 
– Italian 
– Japanese 
– Korean 
– Polish 
– Portuguese (Brazil) 
– Spanish
<h3>Usage</h3>
<ol>
<li>
Add language switcher using the shortcode: 
 [easyi18n_switcher]
</li>
<li>
Mark text:
</li>
</ol>
Fallback text
<ol>
<li>
Add translations in the admin UI
</li>
<li>
Save and refresh page
</li>
</ol>
The plugin loads translations automatically based on current language.
<h3>Support</h3>
This is a community project, but development is supported by donations.
If this plugin helps your work, please consider supporting its maintenance and development on Ko-fi: https://ko-fi.com/micheldosanjos
Support may be limited or delayed.
<h3>Contributing</h3>
Pull requests and translations are welcome.
<h3>License</h3>
GPLv2 or later 
https://www.gnu.org/licenses/gpl-2.0.html

Easy I18n

Lightweight inline translation plugin for static content and Elementor. No page duplication.

Pascal Birchler

Thanks to language packs it’s easier than ever before to change the main language of your site. 
However, in some cases a single locale is not enough. When WordPress can’t find a translation for the active locale, it falls back to the original English strings. 
That’s a poor user experience for many non-English speakers.
This feature project aims to change that by letting users choose multiple languages for displaying WordPress in. 
That way you can set some sort of “fallback chain” where WordPress tries to load translations in your preferred order.
Please help us test this plugin and let us know if something is not working as you think it should.
Keyboard Shortcuts
<ul>
<li><code>Arrow Up</code>: Move selected locale one position up.</li>
<li><code>Arrow Down</code>: Move selected locale one position down.</li>
<li><code>Home</code>: Select first locale in the list.</li>
<li><code>End</code>: Select last locale in the list.</li>
<li><code>Backspace</code>/<code>Delete</code>: remove the selected locale from the list.</li>
<li><code>Alt+A</code>: Add the current locale from the dropdown to the list.</li>
</ul>
Note: the Preferred Languages UI needs to be focused in order for the keyboard shortcuts to work.
Merging Translations
Previously, only the first available translation for a given locale and domain will be loaded. 
However, when translations are incomplete, some strings might still be displayed in English. 
That’s a poor user experience as well.
To prevent this, Preferred Languages now automatically merges all incomplete translations in the list.
the <code>preferred_languages_merge_translations</code> filter can be used to opt out of this behavior. 
It provides three parameters:
<ol>
<li><code>$merge</code> – Whether translations should be merged. Defaults to <code>true</code>.</li>
<li><code>$domain</code> – The text domain</li>
<li><code>$current_locale</code> – The current locale.</li>
</ol>
<h4>Get Involved</h4>
Active development is taking place on <a href="https://github.com/swissspidy/preferred-languages" rel="nofollow ugc">GitHub</a>.
If you want to get involved, check out <a href="https://github.com/swissspidy/preferred-languages/issues" rel="nofollow ugc">open issues</a> and join the <a href="https://wordpress.slack.com/messages/core-i18n" rel="nofollow ugc">#core-i18n</a> channel on <a href="https://wordpress.slack.com/" rel="nofollow ugc">Slack</a>. If you don’t have a Slack account yet, you can sign up at <a href="https://make.wordpress.org/chat/" rel="nofollow ugc">make.wordpress.org/chat/</a>.

Preferred Languages

Esto es imprescindible para cualquier usuario no angloparlante. El estado de las traducciones es irregular y sería perfecto tener un segundo e incluso un tercer idioma local para cargar si algo falta en tu idioma local, y así que no salga media web en español - por ejemplo - y el resto en inglés.

Esto ya estaría en WordPress si los principales equipos de desarrollo no fuesen angloparlantes, y claro, para ellos no es una prioridad ni de lejos.

Imprescindible - Debería estar ya en WordPress

Thanks for Pascal to solve the problem of fallback languages. It is time to add it to the core and would show that WordPress is thinking globally.

In core, please

I think this should be in Core for websites with several possible languages. I like it very much! Specially I appreciate that each user can also choose languages from the selected languages. 
(I am developing a translation plugin for my own needs to use Google Translate to translate posts/pages and complement it.)

Very necessary in core


I honestly think that this should be a core feature of WP. 



The only thing wrong I notice is that when you are looking at the front end... The language of the admin bar changes into the site language but that's the only issue I have with this plugin at the time of writing. For the rest, it's a dream plugin.


Make this a core feature

Should be in the core!

Choose languages for displaying WordPress in, in order of preference.

Easy I18n vs Preferred Languages