Translation Team/Pootle Administration

From Sugar Labs
< Translation Team
Revision as of 16:28, 11 January 2011 by Godiard (talk | contribs) (Created page with "=== Work in progress .... === Pootle in Sugar is actually unmaintained. We (godiard / martin_xsa / erikos) are trying to resolve the pending issues because we need working tran...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Work in progress ....

Pootle in Sugar is actually unmaintained.

We (godiard / martin_xsa / erikos) are trying to resolve the pending issues because we need working translations but need a real maintainer.

The last maintainer was Sayamindu Dasgupta and we asked he our doubts, i am putting here this information.

Basic info:

The pootle directory is /var/lib/pootle The translations live in /var/lib/pootle/translations

Creating branches:

  • Each branch (eg: glucose-0.90) is a directory in the translations directory
Each project is a subdirectory inside this directory (eg: glucose-0.90/sugar)
These are actually symlinks to directories /var/lib/pootle/checkouts
  • There's a script called pootlepopulator.py[1] It is invoked as
pootlepopulator.py category GIT_URL checkout_directory [branch]
So, assuming the directory /var/lib/pootle/translations/sucrose-0.90 exists,
you can issue a command:
pootlepopulator.py sucrose-0.90 git://dev.laptop.org/git/sugar sugar

sucrose-0.90

The script can be found in maintainance/helpers directory in /var/lib/pootle
  • Once this is done, you need to create project in Pootle admin - go

to admin->projects and createa project called Sucrose 0.90 with the code sucrose-0.90 (same as the directory name)

  • Restart Pootle and Apache if the new project does not show up after this...
  • Add the new projects to maintenance/helpers/potupdater/project_list.ini

-sdg-

[1] http://git.sugarlabs.org/pootle-helpers/mainline/blobs/master/admin/pootlepopulator.py

Working in git in the pootle server

The git operations must be done by the pootle user:

sudo -u pootle git log

sudo -u pootle git push origin sucrose-0.82

Resolving conflicts

If the maintainer did a commit with a file in the po directory we will have a conflict, and Pootle can not do a pull.

Pootle build the pot file from the sources, if we compare and the translations are updated in pootle we can do a pull preserving the info in pootle:

sudo -u pootle git pull -s ours


Pootle scripts:

http://git.sugarlabs.org/pootle-helpers/mainline/trees/master/potupdater