Photricity Web Design

Evertongue helps WordPress sites carry one message across many languages without the overhead of a heavyweight multilingual system.
It was built for teams who need more than a handful of translations. Many popular multilingual plugins work well for a few languages, then become hard to manage as the language list grows. Evertongue keeps the workflow intentionally simple: real WordPress pages and posts, predictable language URLs, focused string translation, and switchers that remain usable when your audience spans dozens of languages.
Inspired by Revelation 5:9, “every tribe and tongue and people and nation,” Evertongue is for mission-driven teams working to make their message accessible to a global audience.
<h4>What Evertongue does</h4>
<ul>
<li>Translate pages and posts as whole posts using the standard Gutenberg/classic editor</li>
<li>Translate theme/site strings</li>
<li>Default language at the site root, others under <code>/{code}/</code></li>
<li>Identical slugs across every language for a given page or post</li>
<li>Auto-swapping menu items with fallback to the default language</li>
<li>Floating language switcher, or manual template tag</li>
<li>hreflang alternate links and og:locale metadata on translated pages and posts</li>
<li>WPML and Polylang importers for migrating languages, content, and strings</li>
<li>PO file export/import for round-tripping strings</li>
</ul>
<h4>What Evertongue does not try to be</h4>
Evertongue is not an all-in-one localization suite. It does not try to handle every edge case, automatic translation workflow, or site-specific integration inside the core plugin. The goal is a clean foundation for multilingual content that stays understandable, maintainable, and fast as your language count grows.
<h3>Usage</h3>
Add languages under Evertongue → Languages. Configure your default. Translate pages and posts from the editor sidebar (Gutenberg) or side meta box (Classic).
Render the language switcher in your theme:
<pre><code><?php if ( function_exists( 'evertongue_switcher' ) ) evertongue_switcher(); ?>
</code></pre>
Use <code>style => 'combobox'</code> for a searchable dropdown.
For users who prefer not to edit theme code, enable the floating button or footer list under Evertongue → Settings → Automatic switchers.

Evertongue

Carry your message across every language. Lightweight, scalable WordPress translation for reaching a truly global audience.

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.

Evertongue vs Preferred Languages