However, handling the translation for these strings is a bit of a pain in the b**t. The code is easier to read and much easier to manage. You just wrap texts in gettext calls, like _(‘foo’) and _e(‘foo’), and you’re done. When writing PHP code that includes localized strings, it’s easier organizing translations by string contents without using any tokens. Pros and cons for using tokens to organize translations Several strings that have the same value can have different translations – each on matching the context of the string. Now, the translation is arranged according to the context of the string and where it’s being used and not according to the contents. It appears like a minor change, but it’s very important. In the theme, this string will be displayed like: In this case, the translation table would be: Token Translations are organized according to the tokens and not the string values. Each string gets a token, that describes what the string is used for. Resource files in applications normally use a different approach. Otherwise, the original text is displayed. If there is translation for the string, it will be output. When you use the multilingual string, you would normally enter something like: The translation table (to Spanish) looks like: String For example, if you translate the word ‘Save’, it can be used in a form for saving the current values or in the context of “ Save the Earth”. It doesn’t matter where the string is used but only what it contains. mo files handle strings according to their contents. Do we translate according to string contents or token names? mo files to localize itself, just managed automaitcally (without the need to search for new strings and add them to the. It’s very similar to the way WordPress uses. Otherwise, the original value of the string is shown.

If there’s a translation for a certain language, that translation will be shown. Each string will have entries in all the site’s languages, which will be user editable.

When new texts are created (by the widgets save or blog configuration save), they will be automatically added to the list of strings in the website.

What we’re thinking about is adding a generic string translation facilty which will allow localizing anything that’s text. We’ve been asked how to translate texts that appear in the site but are not a part of posts or pages.

Poedit adding entry