comotive

Supertext

msebel

This plugin allows the user to send a WordPress post or page to Supertext for translation or proofreading.
Process for translation
Supertext can translate content, titles, excerpts, image captions, shortcode arguments and custom fields. Simply order a translation instead of creating a new page. 
You will be presented with services, prices and deadlines. Select the right one for you. 
Once completed, the translation will be automatically inserted into a new page or post in your WordPress installation. 
You’ll be notified by email once your translated content has been uploaded to your website. 
This works for every post type that is translatable by Polylang or WPML.
Process for proofreading
For proofreading your existing page or post, select the option “order proofread”. You will be presented with services, prices and deadlines. 
Select the right one for you. Once completed, the proofread text will automatically be inserted into your post or page in your WordPress installation.
Please note
Translatable custom fields must be defined in the settings. Supported plugins at the moment are:
<ul>
<li>Advanced Custom Fields</li>
<li>Yoast SEO</li>
<li>All In One SEO pack</li>
</ul>
If the field is not available in one of the lists, you can define it by adding self defined custom fields.
The plugin supports following page builders:
<ul>
<li>Visual Composer</li>
<li>Beaver Builder</li>
<li>BE page builder</li>
<li>Divi page builder</li>
<li>SiteOrigin page builder</li>
<li>Elementor</li>
</ul>
We highly recommend to test the translation process for the page builders mentioned above and for any other that you may use.

Supertext Translation and Proofreading

This plugin allows you to order human translations for your pages and posts using Supertexts professional translation services.

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.

Supertext Translation and Proofreading vs Preferred Languages