Notice

This page show a previous version of the article

Checking in Extracted UI Strings and Their Translations

These instructions describe how to extract UI strings so that they can be translated. The original source of these instructions, stored on Assembla, is here: 1

Markup for internationalized strings in the code

In the code, whenever developers write strings that will have to be translated, they use a special function whose name consists of a double underscore. A script (CakePHP's "i18n extract" script) can later be run to scan the code and extract the strings that are passed to this function.

Examples, with the equivalent actions:

  • __(‘some text’) => echo ‘some text’;
  • __(‘some text’, true) => return ‘some text’;

The language used in the code will be English.

Running cake i18n

  • Open a console on a Linux machine or Linux virtual machine.
  • Type : /var/http/tatoeba/cake/console/cake i18n
  • Choose : E (Extract POT file from source)
  • When asked if you want to merge all translations into a single file, say yes
  • Type in the path to app: /home/tatoeba/tatoeba-www/app
  • Type in the path to locale: /home/tatoeba/tatoeba-www/app/locale
  • Choose a name for the file that will be generated (in this example, default.pot): default.pot
  • Choose: Q (quit)

Modifying the header

Before you upload the POT file, you may need to open it and change the header into this:

msgid ""

msgstr ""

"Project-Id-Version: \n"

"POT-Creation-Date: \n"

"PO-Revision-Date: \n"

"Last-Translator: \n"

"Language-Team: \n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=utf-8\n"

"Content-Transfer-Encoding: 8bit\n"

Otherwise, Launchpad may reject the file.

Uploading default.pot to Launchpad

Go to this URL:

https://translations.launchpad.net/tatoeba/trunk/+translations-upload

Set the following: * file type: template * path: default.pot * template: default

You can leave name and translation domain empty.

Upload the file.

You may need to wait a day or so for the translation files to be updated.

Editing .po files

You may need to edit the .po files manually at this stage if you want to restore translations for UI strings that have changed. Skip this step if you don't know what is entailed.

Check .po files

Use this command on each .po file to ensure that it has the correct syntax:

msgfmt -c filename.po

The Launchpad site executes this step after the .po files are uploaded and approved, but checking the files first will save you more work in the long run.

Upload .po files

Put all the .po files that have changed into a "tarball", which is a file with the extension .tar.gz or .tar.bz2 . You can use a zipfile utility such as 7Zip command on Windows or tar on Linux to produce the tarball. Then upload them at the same URL that you used to upload the default.pot file.

Run update-translations.sh

Go to your Tatoeba virtual machine and run this script:

tatoeba-www/docs/update-translations.sh

It will do the following: * check out the files from the Launchpad repository (using Bazaar) * place them in a temporary directory * check them into the final Tatoeba2 repository

Note that the script currently commits to the old Assembla SVN repository rather than the new GitHub Git repository. This needs to be changed (see issue #96).

Actions