Pascal Birchler

<p>Thanks to language packs it’s easier than ever before to change the main language of your site.<br />
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.<br />
That’s a poor user experience for many non-English speakers.</p>
<p>This feature project aims to change that by letting users choose multiple languages for displaying WordPress in.<br />
That way you can set some sort of “fallback chain” where WordPress tries to load translations in your preferred order.</p>
<p>Please help us test this plugin and let us know if something is not working as you think it should.</p>
<p><strong>Keyboard Shortcuts</strong></p>
<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>
<p><strong>Note</strong>: the Preferred Languages UI needs to be focused in order for the keyboard shortcuts to work.</p>
<p><strong>Merging Translations</strong></p>
<p>Previously, only the first available translation for a given locale and domain will be loaded.<br />
However, when translations are incomplete, some strings might still be displayed in English.<br />
That’s a poor user experience as well.</p>
<p>To prevent this, Preferred Languages now automatically merges all incomplete translations in the list.</p>
<p>the <code>preferred_languages_merge_translations</code> filter can be used to opt out of this behavior.<br />
It provides three parameters:</p>
<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>
<p>Active development is taking place on <a href="https://github.com/swissspidy/preferred-languages" rel="nofollow ugc">GitHub</a>.</p>
<p>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>.</p>


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.

Pedro Mendonça

<h3>Use any Locale, with or without Language Packs</h3>
<p>With core Language Packs you can easily change the language of your WordPress install.</p>
<p>The Language Packs used to be provided only for 100% translated Locales.</p>
<p>To give teams with less contributors a better chance to get WordPress released into their Locale, since <a href="https://make.wordpress.org/polyglots/2021/02/22/wordpress-5-7-ready-to-be-translated/" rel="nofollow ugc">22nd February 2021</a> the required translation status for core Language Packs to be built are as follows:</p>
<ul>
<li>The <a href="https://translate.wordpress.org/projects/wp/dev/" rel="nofollow ugc">Front-end project</a> needs to be translated at least <strong>90%</strong>.</li>
<li>The <a href="https://translate.wordpress.org/projects/wp/dev/admin/" rel="nofollow ugc">Administration project</a> needs to be translated at least <strong>75%</strong>.</li>
<li>The <a href="https://translate.wordpress.org/projects/wp/dev/admin/network/" rel="nofollow ugc">Network Admin</a> and <a href="https://translate.wordpress.org/projects/wp/dev/cc/" rel="nofollow ugc">Continent & Cities</a> projects are not included in the threshold calculation.</li>
</ul>
<p>If you need a Locale that has no Language Packs yet, this tool helps you by enabling ALL Locales on the list of the available languages.</p>
<h3>Compatible with plugin <a href="https://wordpress.org/plugins/preferred-languages/" rel="ugc">Preferred Languages</a></h3>
<p>The plugin <a href="https://wordpress.org/plugins/preferred-languages/" rel="ugc">Preferred Languages</a> overrides the standard languages field for site and user languages.</p>
<p>All the features added by Translation Tools are available for Preferred Languages users.</p>
<h3>Update your WordPress, Plugins or Themes translation, on demand</h3>
<p>If you need to update your WordPress core, Plugins or Themes translations on demand without waiting for a language pack to be generated, this tool allows you to manually update all the needed files for the installed version, with one click, in a few seconds.</p>
<p>Go to “Translations” on the Updates screen and choose what you want to update.</p>
<h4>All WordPress core sub-projects</h4>
<ul>
<li>Development</li>
<li>Continents & Cities</li>
<li>Administration</li>
<li>Network Admin</li>
</ul>
<h4>All translation files</h4>
<ul>
<li>.po (editable translation files)</li>
<li>.mo (binary translation files)</li>
<li>.l10n.php (PHP performant translation files)</li>
<li>.json (JavaScript translation files)</li>
</ul>
<h3>WordPress Translations tests and info in Site Health</h3>
<p>Check your WordPress core translations in Site Health tests page.</p>
<p>The Site Health debug info shows the selected site and user languages, including multiple languages from the plugin Preferred Languages.</p>


Translation Tools

A fundamental tool for translators (and not only), works flawlessly.

Essential

The big difficulty when a plugin uses mostly JS is that the source files are minified. It is therefore very difficult to understand exactly where the string to be translated is.
This plugin allows to start the translation by validating and testing the strings locally little by little. Without waiting for 90%.

Essential plugin for translating plugins that use the block editor


This is a function that Wordpress should bring natively!


Excellent work

Translation tools for your WordPress install.

Preferred Languages vs Translation Tools