Inpsyde GmbH

Guido Scialfa

Patrick Ullrich

TranslationMANAGER is a WordPress plugin that allows a user with the correct roles to request a translation of one or multiple articles, pages etc. However, TranslationMANAGER cannot import the content into the correct location because it does not have any information in relation to this. A Multilingual plugin is required for this purpose.
TranslationMANAGER works on sites with MultilingualPress 3 (https://multilingualpress.org/), Inpsyde’s solution for multilingual WordPress sites.
MultilingualPress requires some setup and our documentation (https://multilingualpress.org/docs-category/multilingualpress-3-getting-started/) provides information on how to connect sites and content.
Knowledge of how to connect content is not required, because the MLP module which is included in Translation Manager will carry out this task.
Basically, when you request a translation and import it afterwards, the MLP module will perform the task in the background.
<h3>Setting up TranslationMANAGER</h3>
For TranslationMANAGER to work correctly, the API key has to be set.
Every site has its own settings and it is possible to have different API keys for each site or to use one API key for all sites. 
To add the API key, go to TranslationMANAGER > Settings > Connection from within a site.
Enter the information in the Api Key field and click on Save changes.
Now you are ready to create projects and translate content.
<h3>Creating and Managing Projects</h3>
There are two ways to create a new project.
Go to TranslationMANAGER > Translations > Projects and complete the fields under the section Create new project. The description is optional and can be omitted.
You can Delete or View the project by hovering over the project name in the table on the right.
The second way to create a project is to request a translation, which is described in the Inquiry for Translation chapter. 
Managing the Project
To manage the project, click on the View link to see the available actions below the project name.
The Project page makes it possible to change the project settings, order a translation, view the status of the translation and import the translation.
As much content as required can be collected before placing the order for translation. 
Afterward, the status button can be used to get updates on the translations and to import the translated content.
<h3>Project Statuses</h3>
A project can have different statuses.
Pending 
We have received your request for quotation.
Feedback 
You have received the price, timeline and scope of the project. The quote is ready for approval by you.
Rejected 
You have rejected the quote.
In progress 
We are working on your project.
Finished 
Your project has been completed and is ready for download.
Imported 
The translations have been successfully imported into your system.
The initial status, when you have collected the content you want to translate and before you place the order, is: Ready to order.
When you click on Place Order, the status of the project will change to In Transition, which means 
that the content you want to translate has been sent to the server.
To get updates on the current status of the translation, simply click on the Update button. 
One thing to note is the Project Number. This is the number of the project on the server 
which can be used when contacting support in case of problems.
<h3>Importing Project Content</h3>
When all the content within a project has been translated, the status of the project will change to Finished and the content can be imported.
Remember, the status can only be updated through an explicit update request by clicking on the Update button.
At this point, all that is required is a click on Import and TranslationMANAGER will do the rest.
After the content has been imported, it is always possible to re-import the content. This is useful because it makes it possible to remove a translation for any reason whatsoever and import a new one.
But this feature has a downside, as it creates new content without checking if translated content
is already present.
This is not a problem because it does not affect the existing content. However, importing the translations multiple times will create duplicate content.

TranslationMANAGER for WordPress

With TranslationMANAGER, exporting content from your WordPress Multisite is easy and straightforward.

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.

TranslationMANAGER for WordPress vs Preferred Languages