OLD Manual

Link: http://manual.b2evolution.net/Updating_Language_Files

So your .PO language file has been added to the b2evolution distribution. Good. b2evolution is now localized for your language.

However, as new versions come out, new strings are added to b2evolution and you'll need to update your .PO file accordingly.

The latest up-to-date strings are always available in the .POT file that comes with the latest version (or on CVS, but you must make sure to use the right branch then, so don't use CVS unless you know exactly what you're doing).

The latest .POT file can easily be merged into your already translated .PO file, so you'll only have to translate what has changed since last time you worked on the .PO.

Note: For some languages, the latest .POT will automatically be merged into the .PO file. However, this will be discontinued in the future.

To update your .PO file with the latest .POT: open your .PO file in POedit, go to the "Catalog" menu and select "Update from POT file...", finally select the latest .POT file and voilà!

When merging, the gettext utilities/tools will try to find approximative translations for each new string based on existing translations you made in previous updates. These approximations often make no sense at all... and some languages are more sensitive to this than others.

All automatic/approximative translations are also automatically marked as fuzzy so you know you have to review them. This also means it is not recommended to use the fuzzy state for anything else than identifying automatic translations.

Finally, be assured that these automatic translations do not degrade your work in any way. Already translated strings are never modified automatically and automated translations of new strings never appear in the application until you validate them! As a matter of fact, b2evolution does not use the .PO files directly. These files need to go through a process of extraction before their content is used. We never do extract automatically updated .PO files. We only run extraction on .PO files you send back by email with everything checked.

Once again, I suggest you do not leave anything fuzzy in the files you send back. If you're unsure of something, just leave it untranslated (empty string) rather than marked fuzzy.