Inpsyde GmbH

Guido Scialfa

Patrick Ullrich

locale

With the WordPress plugin from Locale you can send your pages and posts to your LSP. The plugin requires MultilingualPress 2 or 3.
<h3>Setup</h3>
<ol>
<li>In your WordPress project, go to Locale > Settings > Credentials</li>
<li>Copy the API key</li>
<li>Paste it into the API key field in WordPress</li>
<li>Click on Save changes</li>
</ol>
You are now ready to create, and import translation jobs.
<h3>Creating Translation Jobs</h3>
<ol>
<li>Go to your posts or pages list</li>
<li>In the Bulk actions dropdown, select Bulk Translate</li>
<li>Tick the checkboxes of the posts or pages that you want to translate</li>
<li>And click on the Apply button beside Bulk Translate</li>
</ol>
This will create a translation job, that can later be imported into the languages that you have configured in MultilingualPress
<h3>Managing Translation Jobs</h3>
<ol>
<li>Go to Locale > Jobs</li>
<li>Here you can view, or delete an existing translation job</li>
</ol>
<h3>Importing Translation Jobs</h3>
<ol>
<li>Go to Locale > Jobs</li>
<li>Select the translation job that you want to import</li>
<li>On the translation job information box, click on Import</li>
</ol>
This will update the posts indicated in the translation job with the corresponding translations based on the matching language codes.
<h3>Project Statuses</h3>
Here are the following statuses that a translation job goes through before finally being imported:
<ol>
<li>In Progress – The translation is in progress.</li>
<li>Delivered – The translation has been completed, and is now ready for importing.</li>
</ol>
The Import button in a translation job’s information box will only be displayed once it is delivered. Click on Update, occasionally to check on the translation’s status.

Locale for WordPress

With Locale, connect your WordPress Multisite to your Language Service Providers, like RWS, TextMaster and Alpha.

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.

Locale for WordPress vs Preferred Languages