0

WPML 1.1 allows translating not just posts, pages, tags and categories but also all the little persistent texts that didn’t get translated so far. These include the blog’s title, tagline, widget titles, widget contents and other ‘floating’ texts.

New in features WPML 1.1

  1. Translation for ‘general settings’ strings: we already talked a bit about translating texts by other plugins, and now it’s officially released.
  2. Translation by ICanLocalize for texts in custom fields (I’ll talk more about this in a minute).
  3. A new overview page that gives a quick snapshot of WPML’s features.

Example usage for translation of custom fields

This is only relevant for folks who use our translation service via WPML. As you know, the ICanLocalize translation service allows running a multilingual WordPress sites without spending any time doing translations yourself.

  1. Until now, WPML would send the post/page title and body for translation. WPML 1.1 allows including any custom fields that belong to pages. You must be asking yourself what something like that is good for. Well, here are a few examples:
  2. If you’re using an SEO plugin, it will add custom fields for titles, descriptions and keywords.
  3. If you’re using WPML’s section names for navigation, those get included.
  4. If you’re using custom fields for your proprietary needs, you can have them translated too. Folks who use plugins such as More fields will see the immediate benefit.

Fixes and improvements

We didn’t have too many bugs to fix from WPML 1.0.4, so we could concentrate mainly on building new features and improving new ones.

The most notable addition is auto-loading the theme’s text domain for localized themes.

When you go to WPML->Languages->Theme localization, you’ll see a new field for entering your theme’s text domain. The text domain is the second argument in all the __() and _e() calls.

WPML will automatically load your theme’s .mo file according to the locale’s name and the text domain you enter there. This should help get multilingual themes much easier that it’s done now.

What’s next

We’re working on localizing themes with WPML too. It’s almost ready but didn’t make it into version 1.1. The way it’s going to work is:

  1. Create a .po file for your theme (you’re welcome to use our online .po generator).
  2. Upload that file to WPML.
  3. Translate in WPML in the strings translation table.

That’s it. You don’t need to create any .mo file or do anything else.

What do you think?

Do you like these new features? Anything you’d do different? Let us know.