l10n: Pull, update and push

Prerequisites

• We're using Gettext v0.19.7 or greater, this fixes some reflow issues and is needed for some extraction types. Anything older and we get massive noise from reflow.

Get translations from PLO

• make get-translations
• git add pootle/locale/*/*.po
• git commit
• git push

Create new POT files

• make pot
• git add pootle/locale/templates/*.pot
• git commit
• git push

Update translations in PLO against new templates

We commit these to VCS because we want template updates in one batch and want to be able to see user translations clearly from template updates.

• Get into dev virtualenv
• make pot
• ./pootle/tools/updatepootlepo
• git add pootle/locale/*/*.po
• git commit
• git push
• make put-translations
• git reset --hard HEAD

Testing localisations

If you want to see that your localisations are actually working then you want to hack a locale with an xxx build. This will place x's around localisable strings. Thus Open becomes xxxOpenxxx and thus you can easily see if a string is translatable. Anything without xxx around it cannot be localised.

• ./pootle/tools/test_localisation.sh --pot af
• make assets
• Restart server
• Check localisations

This will use the af locale as your test locale (use whichever language you find easiest to set on your browser. You need to rerun make assets to ensure that assets are compiled.