Language packs for version 1.9 will also work on version 1.10.

However, version 1.10 introduces some new strings that would need specific translation.

Thus, complete 1.10 language packs will improve user experience.

Now would be a good time for all translators to update translations for version 1.10 and send them to me.

If you've never done a translation before but would like to contribute, you can find startup instructions here. There is a cool tool to help you translate efficiently.

Hi there!

We have updated all our info pages about translations, locales and language packs:

• What are the available translations?
• How to create a new translation?
• How to update an existing translation?

Of course, there may still be unanswered questions. So, if after reading those pages, something is still unclear, please fire up your questions. We'll do our best to include answers!

One question that is comming back frequently is: What happened to the language files in Phoenix? Why are there only translations for French, German and Japanese?

Actually all previous translations are still there in CVS. However we haven't shipped them with the release because they haven't been updated yet, i-e they do not contain translations for many many strings in Phoenix. Using the old files would only partially localize Phoenix to the desired language.

To update 0.9.x languages files to Phoenix, you need to merge them with the new .POT file found in Phoenix as described in the online manual.

Also, we're planning to only ship a limited number of localizations by default in future releases, in order to keep the main download file small. All other languages will be provided separately in their own language packs.

The current version 0.9.0.8 "Oslo" is pretty stable. We will however release a new version codenamed "Madrid" shortly.

The main purpose will be to provide more language packs in the main distribution.

To all translators: please update your language files as much as possible for this release.

There are two language files to translate:

• The application messages.POT : latest version here
• The install help static.POT : latest version here

The translation howto is here. Anyone feel free to start a new translation or update one that has not been updated in a while.

For those of you updating directly on the CVS ( Ronh! ), please make sure that you work on the "v-0-9" stable branch and not on the main development branch. Only changes in the "v-0-9" branch will make it into the release!

Ah yes... we might also introduce some slight cosmetic changes in this release (what do you think?)

Okay everyone, version 0.9 is nearly complete and the language files are now considered stable.


Now would be a good time to start translating if you want your language to be up to date in the release.


Version 0.9 is packed with new code, and that also applies to interface strings. There are 50% more strings than in 0.8! So there's no time to waste!


If you wish to translate but don't know how to get the latest version from CVS, you can contact me directly.


Update: Please note there is now a second lang file for the install help files, see http://forums.b2evolution.net/viewtopic.php?t=1139

You have asked for it, here it is!


By popular demand, a complete localization toolkit for b2evolution has been alpha released.


French and Japanese are already available. Dutch and Sweedish have partial translations. Brazilian Portuguese is in the works...


I count on you to produce a language files galore for the next release!

Okay, with the first beta-testers testing b2evolution I am beggining to feel an urgent need to localize the software. I was running most of my pages with french text (like "laisser un commentaire") and the testers want english (that is at least english!)

Right now I just switched back everything to english but I do need to localize this. Actually, I needed this anyway for my own site. I will eventually do it as planned and links like "leave a comment" will be displayed in the current post's language.

On blogs like this one, were posts are mixed in multiple languages (yeah I know it's a little strange, but this is Europe... ) that means I must have several languages handy at all times.

So I was thinking about putting the strings into arrays... but this may not be as straightforward as I could have thought, as I need to take care of several things:

• Make it efficient
• Make it readable in the source code. Replacing 'leave a comment' with $uistring[49][$lang] won't do it!
• Make it easy for contributors to translate the whole product

Gotta think about it some more...