Amir Helzer

<p>“ICanLocalize Translator” allows running multi-lingual WordPress websites (See the <a href="http://media.icanlocalize.com/wp_translation_demos/icanlocalize-translator.htm" rel="nofollow ugc">5 minute demo</a>).<br />
It helps maintain contents in different languages and automatically links between them.</p>
<ul>
<li>Blog in your native language. Translations will be created automatically.</li>
<li>Use different domains, <code>www.myblog.com</code>, <code>es.myblog.com</code>, <code>de.myblog.com</code> or directories within the same domain.</li>
<li>Updates are handled automatically. When the original contents update, translations follow.</li>
</ul>
<p>WordPress supports contents in a single language. To make multi-lingual WordPress sites insensitive to upgrades and to other plugins,<br />
ICanLocalize Translator doesn’t change any table structure and doesn’t alter permlinks. Instead, each language will run in its own WordPress instance.</p>
<h4>Is this machine translation?</h4>
<p>Unlike free machine translators, this plugin will send posts and pages to be translated by real people.<br />
You can select from our pool of professional translators or assign the work to your favorite translator.</p>
<p>This plugin works together with <a href="https://wordpress.org/extend/plugins/icanlocalize-comment-translator/" rel="ugc">ICanLocalize Comment Translator Plugin</a>.<br />
It needs to be installed in the original-language blog. The Comment Translator plugin will be installed in the translated-language blog(s).</p>
<h4>Running a multi-lingual site</h4>
<p>Even though visitors read and comment in their languages, and You will do all your tasks (including comment moderation and replies) in your own language.</p>
<p>Comment moderation in your language is handled by <a href="https://wordpress.org/extend/plugins/icanlocalize-comment-translator/" rel="ugc">ICanLocalize Comment Translator Plugin</a> which needs to be install on each of the translated blogs.</p>
<p>The plugin provides a function that you can include in your theme which automatically links between contents in different languages.</p>
<h4>What gets translated</h4>
<p>The plugin will automatically send all texts to be translated, including:</p>
<ul>
<li>Posts</li>
<li>Pages</li>
<li>Tags</li>
<li>Categories (names and descriptions)</li>
</ul>
<h4>Where can I see some examples?</h4>
<p><a href="http://blog-en.icanlocalize.com" rel="nofollow ugc">Our own blog</a> is being translated by our system from English to French.<br />
You’re invited to <a href="http://www.icanlocalize.com/web_dialogs/new?language_id=1&store=4" rel="nofollow ugc">contact us</a> for other examples.</p>
<h4>SitePress</h4>
<p>This plugin is part of <a href="http://sitepress.org" rel="nofollow ugc">SitePress</a> – a collection of plugins that turn WordPress into a fully featured multilingual content management system.</p>
<h3>Version History</h3>
<ul>
<li>Version 0.4
<ul>
<li>First public release</li>
</ul>
</li>
<li>Version 0.5
<ul>
<li>Improved support for page hierarchy</li>
</ul>
</li>
<li>Version 0.6
<ul>
<li>Works with WordPress MU</li>
</ul>
</li>
<li>Version 1.0
<ul>
<li>Users can cancel translation jobs</li>
</ul>
</li>
<li>Version 1.3
<ul>
<li>Includes drop down language switcher that can be added to header.php.</li>
</ul>
</li>
<li>Version 1.3.1
<ul>
<li>Dropdown language selector now support IE6</li>
</ul>
</li>
</ul>


ICanLocalize Translator

Allows running multilingual WordPress sites with zero management. Automatically creates and updates translation when you edit.

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.

ICanLocalize Translator vs Preferred Languages