{"id":516215,"date":"2014-12-01T07:38:24","date_gmt":"2014-12-01T07:38:24","guid":{"rendered":"http:\/\/wpml.org\/?p=516215"},"modified":"2014-12-01T12:04:02","modified_gmt":"2014-12-01T12:04:02","slug":"wpml-3-2-first-alpha","status":"publish","type":"post","link":"https:\/\/wpml.org\/de\/changelog\/2014\/12\/wpml-3-2-first-alpha\/","title":{"rendered":"WPML 3.2 First Alpha"},"content":{"rendered":"

We are ready with a first development version of WPML 3.2. This release packs big improvements for everyone running multilingual WordPress sites and is expected to be production-ready in about 4 weeks.<\/strong><\/p>\n

String Translation – From Any Language to Any Language<\/h2>\n

So far, WPML’s String Translation supported only one source language and that language was set to English. This is because our String Translation mechanism worked much like GetText – everything is translated from one language to all others.<\/p>\n

As we discovered, this causes a convoluted workflow when the site’s default language is other than English.<\/p>\n

\"Selection<\/a>
Selection for source language of string contexts<\/figcaption><\/figure>\n

In WPML 3.2, you will be able to select the source language for different contexts. So, the ‚WordPress core‘ context will be hard-wired to English, scanned themes and plugins will default to English (but you can change it) and the site’s admin strings will default to the site’s default language. Sorry if this sentence takes 5 times to read.<\/p>\n

\"Strings<\/a>
Strings have an explicit source language<\/figcaption><\/figure>\n

Bottom line, you will be able to translate from the original language of the strings to all the site’s languages in a much more natural way.<\/p>\n

Translation Basket<\/h2>\n

Many times, it’s convenient to collect items for translation and send them all at once. WPML 3.2 introduces the concept of ‚Translation Basket‘. It will be similar to the ‚cart‘ in e-commerce sites. You can go through your site’s content (posts and strings) and throw items to the translation basket. They would still not go to translation. Then, review the content of the basket, see that you’re happy and send everything at once. Your translators will receive one package of everything in this round of updates, instead of a trickle of content and strings.<\/p>\n

\"Translation<\/a>
Translation Basket in WPML 3.2<\/figcaption><\/figure>\n

More Professional Translation Services<\/h2>\n

Yes, we are also responsible for ICanLocalize<\/a> and we like our translation service very much, but people need choices. WPML 3.2 will include more options for professional translation, fully integrated into WPML. We are working with leading translation services, adding them to WPML. If you are working with a translation service today, we want you to be able to keep using it when you buy WPML. If you already have a relationship with a translation service, you will only see it in the translation offering. If you buy WPML and are looking for a translation service, you will see a list of all available ones.<\/p>\n

String Translation Packages<\/h2>\n

WPML 3.2 will make it much easier to translate ‚complex‘ site elements. We see a lot of this in page builders, event managers and form plugins. The ‚String Translation Packages‘ allows WPML to translate such elements with just tiny code in their side (two filters, added in strategic locations). We are currently looking integration with ACF, Visual Composer, Headway and Pagelines DMS. Integration with our own Layouts<\/a> plugin is already complete and fully working.<\/p>\n

With String Translation Packages, you can translate virtually anything. WPML will ’see‘ the items for translation as objects with strings. You will see them in the Translation Dashboard and select these items like you select any other WordPress content. Then, send to translation using any method that you prefer.<\/p>\n

If you are working with a plugin that is difficult to translate with WPML, talk with us. We’d like to start a conversation with the author and get this integration rolling. The great thing is, that this integration takes very little development effort. The author of the other plugin (or theme) only needs to add a few lines of PHP, with these two filters. WPML takes care of the rest. There is no performance impact and translation is very convenient for you.<\/p>\n

Known Issues<\/h2>\n

This is a first development snapshot. A lot works and we want to get your feedback on it. Some is broken. All these things (and possibly more) are not working right now. Of course, we will only release WPML 3.2 when everything here, and everything else we or you find gets fixed.<\/p>\n