Pootle/Administration

English | 日本語

HowTo [ID# 211330]  +/-

Contact: Xavier Alvarez —Sayamindu Dasgupta, Rafael Ortiz, Alfonsodg IRC #olpc-pootle, #olpc-content

Please note that the old Pootle address of http://dev.laptop.org/translate does not work anymore. Please use http://translate.sugarlabs.org instead. All data and user accounts should work in the new Pootle installation.

Administrators

There are two kinds of administrators: site & project+language. There's no concept of project administrator per se, nor a language administrator either; tasks & responsibilities that basically go to the site administrator(s).

Project + Language admin

Users with this right have several responsibilities and obligations. Foremost of all is to ensure that the POTs get translated to the target language. In order to do that, they can grant some rights to other users (within said project+language).

Pootle includes several built-in tests that try to ensure some quality levels (or typical errors) in the translations. They can be found by following the Show editing functions in each project+language page. Normally the project+language page displays the progress level of each file (translated/fuzzy/pending) bar. This link changes the way each file is displayed; from the progress bar view into a line of links with something similar to:

Translate My Strings | Quick Translate My Strings | Review Suggestions | Quick Translate | Translate All | PO file | XLIFF file | Qt .ts file | CSV file | Update | Commit

Note

Each one a link (that may or not be enabled). Links above in italic can be ignored.

Unless you know what you are doing, update & commit should NOT be used.

Besides this change on the per-file display, new links appear in the project+language 'gray zone':

Show Statistics | Show Checks | Show Goals | Show Assigns | Translate My Strings | Quick Translate My Strings | Review Suggestions | Quick Translate | Translate All | ZIP of folder

The checks can be found in Show Checks above, producing a detailed list of the errors found in each file, with links that allow editing the offending messages.

Defining goals

see Pootle::Goals

Goals are required in order to be able to assign translations, thus enabling the organizing and prioritizing of work within a given language-project (iow, no global goals). Also worth noting, goals seem to be nothing more than a 'bundle name', with no other data like deadlines, comments or anything else.

In order to define a goal you must enable the Show Goals in the project page, and on the right, there's an entry field to add new.

1. Define a goal in the project page (ie: spanish-olpc) toggle the Show Goals
   • by default a null-goal (ie: Not in a goal) exists as a catch all.
   • on the right, a box with an entry field allows you to give a name and Add Goal.
2. Assign files to a goal
   • as we are trying to include files into a goal, click on the Not in a goal
   • make sure that the Show Editing Funcions is enabled by clicking on it if necessary
   • once in the language-project-goals view (showing the 'Not in a goal' files), each file has a pull-down list to pick and set the goal.

After setting the goals you can view the files bundled in a goal, and later assign work.

Assigning translations

see Pootle::Assigning

This is a nice administrative functionality that will actually (or probably) make the translator's life simpler. As an administrator you can assign certain users to goals and also to specific files (either to translate everything, unassigned, and a couple other variants).

By assigning users and goals/files, those user will then be able to use special links (ie: Translate My Strings or Quick Translate My Strings) that will feed them with their workload, and thus allow focus where is needed for the project. Still, the interface and handling is not quite describable at this moment as many aspects come together and some things need to be better understood in order to get the most out of it (while trying not to complicate things too much).

how do you remove an user from a given goal?

Terminology project

see Pootle::Terminology, Pootle::Matching, Sourceforge.net::Creating glossaries, Toolkit::POGlossary

This is an extremely helpful and relatively inexpensive feature, particularly if we want to open the translation process to non-professional and #Opportunistic translators because it aids them in preserving the terminology that has been decided upon by the more involved segments of the community (ie: will the olpc.es translate "Home" as "Hogar" or "Casa"?)

The basic structure of the terminology file is a standard .PO file (ie: msgid / msgstr). There are some rules about the name (and location) of these files. Documentation is a bit blurry on which alternatives apply, but there are basically two levels (the first as a local mechanism to override the global glossary):

Specific to a project+language

override the global glossary by adding a pootle-terminology.po

note: in projects with the GNU layout where all .po files are kept in one directory—iow, d.l.o—you can not use this approach

Global to the site (as a project)

several POT glossary files can be added to the Terminology project (ie: colors.pot, hig.pot, etc. each dealing with a specific domain for example)

each language would have its corresponding PO file — that will be the one used to provide #suggestions (and edited if given the #User permissions)

Note: It would seem that a <project>-terminology.pot in the Terminology project will automatically match said project (as a source), but it may or may not affect the lookup of other terms in other files in the Terminology project. The precedence rules (if any) are unknown. The lookup is dynamic so there is no need to restart the server.

---

Administrator

1. Enable the languages for which you want to have global terminology:
   • in the projects page head into the terminology project
   • verify that the language is listed (if not add it) (ie: spanish terminology)
2. Create the glossary POT files
   • You can either create them manually from scratch, or
   • use Toolkit::POGlossary] to build the initial file from existing translations. Don't forget to clean it up.
3. If you are going to allow editing the terminology through the web-GUI
   • verify that #user permissions are granted accordingly
   • as an user, in your #User options join the Terminology project
   • enter the project (ie: spanish terminology

As any other project, if you have the #User permissions you can upload updates or totally new files to each language (but not to the templates) or edit the existing ones (ie: xavitest.po)

Taking advantage of translation memory

see Pootle::TM

Very much like terminology but instead of working at a word level, the matching is performed at the whole string proposing full already used translations, saving some time but more importantly providing some level of consistency between translations. On the other hand, instead of being a dynamic feature, this is more of a batch or static process. Starting from a base translation memory file, one may generate suggestions for a specific file or a whole set of them.

pre-test notes

This are some ideas, doubts and why-not stuff related to the reading of the documentation.

File per file is probably not desirable (ie: use one PO to generate a memory for another PO), so some sort of 'olpc' translation memory file (per language) should be made.

How do you generate the initial all-encompassing tm file?

Every time a new language or PO is added, the associated memories for them (as targets) should be (automatically?) created...

Updating a POT (iow, a new version) should trigger the update of all languages.

The updating (which is not done in real-time) would still need to be done in a reasonable time period.

User permissions

see Pootle::Permissions

Permissions are granted or revoked within a specific language-project pair, and optionally, within that scope, to specific users. This means that the nobody & default users have local, instead of global, behaviors.

The following is the list of the available permissions handled by Pootle. The actual description is a result of observation and deduction (haven't found a specific documentation on them), so they are to be considered with #, fuzzy tag...

NOTE: The system administrator flag is not reachable through the GUI, as it resides as a flag (rights.siteadmin) in the user.prefs file. This permission allows the users possesing it to administrate all the projects, languages and functionality (you should always have one user with it).

Permission	Description	Default users	Comments
View	Allows the browsing of the PO files and their translation	nobody, default
Suggest	Allows to suggest a translation	default	this should be enabled for nobody if we want to make things simpler for the #Opportunistic translator.
Translate	Allows to submit a translation.	none	By default there are no users allowed to translate forcing the administrator to grant this right—bureaucratic and restrictive.
Overwrite	When uploading a PO file, it allows the user to overwrite any existing file (iow, no merge of changes)	none	Handle with care.
Review	Allows to approve/reject suggestions made by users capable of suggesting translations.	none	see #Reviewer
Archive	Would allow the user to download the a set of PO files in zip format. Probably those of a language/project.	none
Compile PO files	Allows an user to generate / compile the PO into MO files.	none	It is unknown where the MO files will reside, or how they will be transfered or made available. need to explore
Assign	Allows an user to assign files (or chunks of files) amongst users that have been granted the translate permission.	none	need to explore
Administrate	It's granularity is not well defined (or understood): administrate everything (seems like it), or just a project? or just a language? or just a language-in-a-project?	none	need to explore
Commit	The holy grail or point of all this: make a translation available.	none	Again, the granularity is not well defined or understood. need to explore

Site admin

As an administrator, in your home page you have access to the Admin page which offers: Users, Languages & Projects.

Users

is a simple interface allowing the manual addition of users, edition of their names & (invisible) passwords (ie: resetting them) and where you can activate, de-activate and remove an user.

Languages

allows the maintenance of the list of available languages (based on the ISO 639 codes, a descriptive text, special characters (used in the translating UI), defining the number of plurals and its equation. Note: removing a language here would seem to affect only the ability to associate them to projects, with no apparent impact on the previously defined associations.

Projects

this is the initial page where things start to come together. Besides being able to add a project by defining the values for the Project Code, Full Name, Project Description, Checker Style, File Type and Create MO Files fields, you can also Remove Project. The most mysterious parameter is Checker Style which offers Standard, creativecommons, kde, openoffice, mozilla and gnome as options.

The above covers the broad, high-level configuration, which must be followed by the project and language configuration:

Project languages

A project needs to be informed of which languages it will have. This is accomplished by following the link of a specific project resulting in a page where you can add them. The only apparent way to remove a language is to delete its directory from outside of Pootle.

Project language permissions

Each language mentioned above is a link that allows you to configure the #user permissions in said project-language combination. You can grant/remove specific rights to a particular user, that will only apply in said project+language context.

NOTES

Several languages were removed from the initial (default) list with the intention to limit or focus on the core green languages: am, ar, en, es, fr, ha, hi, ig, ne, pt, ro, ru, rw, th, ur, & yo.

Still pending: Obtain and verify the plural formulas for all.

Primary administration

This administration level refers to the process of ensuring a functional and operative interface between the development environment and the translating environment. In other words, it must cover the largest probable set of situations and describe the appropiate steps to cope with it. Some things that need to be defined before starting are:

Number of Pootle-projects — options are:

1. single 'mega-olpc' project where all d.l.o. projects are kept
2. one-to-one mapping between a d.l.o & pootle project
3. ad-hoc granularity in the mapping (ie: core, bundled, extras, prototypes, etc.)

Some of this granularity may be handled by the concept of goal in Pootle (but they only work within a project+language context). On the other hand, although less likely, is that in a 'mega-olpc' we may be faced with name conflicts (ie: two or more projects using the same filename). This could be solved by adopting a standard naming convention within Pootle(ie: prefixing all Pootle files with d.l.o's path to the project).

Number of Pootle-languages — options are:

1. strict minimal number for the 'green' countries (ie: Amharic, Arabic, English, Spanish, French, Hausa, Hindi, Igbo, Nepali, Portuguese, Romanian, Russian, Kinyarwanda, Thai, Urdu, & Yoruba)
2. the above plus certain 'typical' languages (ie: german, japanese, etc.) plus some 'red' or 'orange' languages
3. totally free as long as a language administrator can be identified and named for each language

Notification channels and/or mechanisms:

• developer's changes to the POTs (creation, changes and elimination) must reach the translating environment.
• translator's work and generation of POs (and possibly MOs) must reach the development environment.

How? This could be performed through the filing of tickets, sending mails, scripts monitoring both sides, etc. And in the future it may be modified to include or consider the back-end integration to git. A clear primary channel must be determined. The periodicity and/or milestones for re-injecting the POs back into the development environment for their testing must also be determined.

d.l.o project	POT	PO	Actions
New	none	none	open a d.l.o ticket requesting missing POT file
		> 0	PAD & developer should decide if a PO may be used as the basis to generate the POT. If appropriate, PAD creates the POT. : switch to 'new, POT > 0 and PO > 0' case below. If not, open a d.l.o ticket requesting missing POT file. Developer eliminates offending PO(s).
	> 0	none	PAD saves POT in po/project/templates. Performs a update from templates (in order to generate the required PO for each language Notifies the LADs who can then decide to include into their goals, assign it, etc.
		> 0	PAD processes the POT as above. : switch to 'old, POT none and PO > 0' below.
Old	updated	none	PAD saves POT in po/project/templates. Performs a update from templates (in order to update existing POs). PAD notifies LADs of changes as it may change the workload of goals and assignments.
		> 0	PAD saves POT in po/project/templates. Performs a update from templates (in order to update existing POs). PAD notifies LADs of changes as it may change the workload of goals and assignments. : switch to 'old, POT none and PO > 0' case
	none	none	ignored — nothing to do
		> 0	LAD verifies that PO matches existing POT. If valid, uploads the PO through the web-GUI (either merging or overwriting the exising file)

Notes

The columns POT & PO refer to the external or incomming files generated outside of Pootle.

If a POT exists in Pootle, the corresponding POs must exist for each language.

Terminology & roles used

POT & PO

name given to the files depending on the purpose: Portable Object Template, for 'master copies'; Portable Object for their localized versiones (one per language). naming convention would probably be "xx.po"

project administrator (PAD)

person in charge of overseeing that a project has the correct (latest) set of POT files and coordinates with the language administrator in order to ensure that the PO files reflect the POTs. Has also the responsibility to decide which languages to use.

to be determined if there's a single PAD for all d.l.o projects or more. Every d.l.o project should have one PAD.

language administrator (LAD)

person in charge of ensuring that PO files are available to be translated while taking the appropriate measures to guarantee that the PO reflect the latest POT, merging, reviewing, etc. the translating community effort. Can also assign tasks to specific registered translator

There should be at least one LAD for each of the 'green' languages.

registered translator

person actually performing the translation of a PO file within a specific project and language.

developer

person that is (ultimately) responsible of providing POT files

Setting up version control systems

see Pootle::Version control

These are some notes of the trials, not actual documentation.

Things have been messier than expected. First of all, GIT is not supported in the stable version, and the newer (unstable) version is reorganizing several aspects of Pootle making it too risky to jump onto the bleeding edge... Thus the decision to backport the git support.

On top of this, although volunteer gnrfan joined the fray (doing the backport), our experience with git is way below average and we are totally in the dark about how does Pootle actually obtain and store the POT files. We seem to have found a way (using symlinks in the Pootle subdirectories pointing to the repository files) but this solution although it may work, is a bit obscure and not even hinted by the documentation of Pootle:

To have any sort of integration with version control from within Pootle, it is necessary to check out the translation files into their correct places in their Pootle projects. The CVS or SVN meta files (CVS/ or .svn/) need to be there. This has to be done outside of Pootle.

Our efforts to contact or elucidate some sort of answers from the Pootle community have not been very effective for the moment... but hope is not lost! :)

Pootle workflow as per #pootle channel

Pootle has some very nice features, but integration to the repositories is not really one of them. Particularly the initial bootstrapping of a project. As extracted from a chat with friedel in IRC#pootle, the usual / standard workflow with no repositories is as follows:

1. The POT file is manually injected into /po/project_name/templates
2. Doing the Update from templates for a specific language in a project basically re-syncs the existing PO (doing a merge, and in the case of conflicts demotes them as suggestionsneed to test) or makes available the particular PO for said language (in the /po/project_name/lang_code).
3. In its origins, Pootle was finished, and the re-injection of the PO & MO files into the original project was left for the language or project coordinator to do.

With the inclusion of repositories, apparently the only part really integrated is the commit phase which would somehow trigger a push of the PO files. Unfortunately the 'pulling' from the repositories is not so automatic. Therefore, the probable (and suggested in IRC) workflow we'll implement requires manual intervention and/or the development of some scripts, and would probably look like this:

1. Have a local git repository that syncs with d.l.o (as any other repository)
2. Manually create the project
3. Manually inject the POT file (most likely a symlink to the POT in the local repository)
4. Update from templates would be performed for all languages

   This step would actually create (or sync) the PO files for all languages in the project together with some associated internal files to Pootle. The actual PO file should then be symlinked and added to the appropriate place in the (local) repository.

   Another possibility would be to create the project directory as a symlink into the repository (and probably use the .gitignore to filter out the Pootle files). This alternative (which could be simpler) seems to clash with the idea that all POT and PO files are stored in the /po directory in d.l.o because Pootle handles each language as a subdirectory (under the assumption that each project has several POT files, something that even Etoys has reverted and now has just one big POT).

5. Translate at will & perform commits at will / as necessary, staying alert for:
   • If the POT changes along the way, this should be somehow noted and an Update from templates should be carried out.
   • If a new POT file (not an update) is generated, it must be manually injected together with the corresponding PO files per language.
   • If a POT is deprecated (eliminated) the appropriate local removal should ensue.

The manual nature of Pootle's repository integration is currently the weakest point as it adds administrative overhead and coordination issues. Some of it could be eased by either developing some scripts or modifying Pootle itself (ie: the creation of a new PO file could be tweaked to automatically generate the symlink instead of the local file and the issuing of the appropriate command to add it to the repository; or, just settle for a simple symlink of the project's directory and all files would reside in the local repository). verify any possible conflict in naming conventions of the target PO—particularly with t.fp.o

Twilight Zone

Testing setup

Is based on a two-layered clone of d.l.o projects. The first clone acts as the pseudo-d.l.o, and the second clone (a clone of the first) is where Pootle files will be symlinked. Currently the first clone (a.k.a. the d.l.o-clone) is in Rafael's home dir, and the second clone (a.k.a. pootle-clone) in Xavi's home dir. Each d.l.o-project is cloned individually, as you can't actually clone d.l.o as a whole. The way each project is cloned into the pootle-clone git is by first cloning from d.l.o:

#
# For every project in d.l.o with L10n support
#
cd __d.l.o-clone__                                            # path to the d.l.o-clone (for testing purposes: /home/rafael)
git-clone git://dev.laptop.org/git/__project_name__           # see git-clone doc
#
cd __Pootle-git__                                             # for testing purposes /home/xavi/clone2
git-clone __d.l.o-clone__/__project_name__ __project_name__   # could be manual or by scripts.(clone.sh) 

Hooking Pootle into the pootle-clone

This is a manual step involving the symlinking of the appropriate POT file(s) and possible PO previously done.

cd /var/log/pootle                  # home podirectory specified in /etc/pootle/pootle.prefs
cd __pootle_project__/templates     # a test directory for OLPC -- for testing purposes /olpctest
# symlink the POT file and associate an unique name withing Pootle by prefixing it with __project-name__
ln -s __Pootle-git__/__project_name__/__project.pot__ __project-name__.__project__.pot
#
# Enter the GUI and in the project languages perform an update from templates
# this will create the appropriate PO files for each language in 
#  /var/log/pootle/__project_name__/xx
# (where the xx is the ISO 639 language code)
#
#
# For each PO that didn't exist in a language in the pootle-project (for testing purposes: olpctest):
#
cd /var/log/pootle/__pootle_project__/xx
mv __unique__.po __Pootle-git__/__project_name__/po/xx.po
ln -s __unique__.po __Pootle-git__/__project_name__/po/xx.po
#
# If a given language PO existed in the project:
# (and you want to keep it)
#
cd /var/log/pootle/__pootle_project__/xx
rm unique.po
ln -s unique.po __Pootle-git__/__project_name__/po/xx.po

The reason that we are symlinking files instead of directories is that the structures differs:

Pootle directories	OLPC git directories
/var/lib/pootle/__pootle_project__ /templates /__project_name_1__.pot /__project_name_2__.pot /es /__project_name_1__.po /__project_name_2__.po /pt /__project_name_1__.po /__project_name_2__.po	/__Pootle-git__ /__project_name_1__ /po /__project_name_1__.pot /es.po /pt.po /__project_name_2__ /po /__project_name_2__.pot /es.po /pt.po
git integration
/var/lib/pootle/__pootle_project__ /templates /symlink __project_name_1__.pot -> __Pootle-git__/__project_name_1__/po/__project_name_1__.pot /symlink __project_name_2__.pot -> __Pootle-git__/__project_name_2__/po/__project_name_2__.pot /es /symlink __project_name_1__.po -> __Pootle-git__/__project_name_1__/po/es.po /symlink __project_name_2__.po -> __Pootle-git__/__project_name_2__/po/es.po /pt /symlink __project_name_1__.po -> __Pootle-git__/__project_name_1__/po/pt.po /symlink __project_name_2__.po -> __Pootle-git__/__project_name_2__/po/pt.po

The initial failure of Pootle to identify a symlinked file as being within the domain of a version control system was fixed with a small patch.

Apparently, the layout of the OLPC's git follows what the Pootle documentation refers to as a GNU layout (in the /etc/pootle/pootle.prefs file):

 # pootle.podirectory
 #
 # All projects are stored in this directory in this layout:
 #   $podirectory/$project/$language
 # Projects can also be stored according to the GNU convention with one PO file
 # per language, and all files in one directory.
 podirectory = "/var/lib/pootle/"

Pootle handles GNU layout automatically (just symlink the /po directory in the d.l.o project and add the pootle-project). Although this reduces the hassle of setting up the version control, there are some practical disadvantages:

• No pootle-project specific glossaries.

  This is not a great loss as the global glossary is still active.

• Multiplicity & size of POT files per project

  Given the nature of our activities, POT files are on the smallish end of the spectrum (even minimal, like Kuku) and each activity, has just one POT file. ** This means that the statistics are rather shallow and not useful to keep tabs on the advances of the localization effort.

  • Some of the intended tools (like goals & assignments) loose their appeal,
  • Adds other administrative tasks (associating languages, permissions and users), and
  • Users will now have to register in each of the projects+languages.

Overall, we could say that the usability (both in administration & user interaction) would suffer, while the only gain is obtained on the initial setup and some follow-up maintenance.

setup

These are the steps being taken in order to properly setup the server:

1. Execute Sayamindu's populatepootle.py script that given the pootle_project, git-url & destination_directory, does the following:
   1. creates a clone of the d.l.o-git (GNU layout /po/xx.po)
   2. creates a symlink in pootle_project/templates to the POT file, and
   3. for each xx.po file it adds a symlink from pootle_project/xx/ to it.
2. In order to trim, or ensure that the POs match their POTs, we recreate them by executing:

   pot2po --input=_/templates_dir/_ --template=_/old_po_dir/_ --output=_/new_po_dir/_

   The resulting new PO files should be copied over the old PO

Advanced site administration

Lowering latency through web servers

see Pootle::Apache

see Pootle::NginX

Translator statistics

see Pootle::LogStats

Configurable logos

see Pootle::Changes

Removing / Renaming files

According to user friedel in IRC#pootle, you can 'safely' delete a file (and associates—ie: xyzzy.es.po.pending) without much to worry about. This has to be done outside of Pootle.

File structure

F/D+Type	File/dir	Comments
D-base	/var/lib/pootle/ (using __pootle-dir__ below)	root directory of the Pootle data directories and files (POT & PO)
D-base	/var/lib/pootle/terminology/	directory representing the pootle-project dealing with the terminology that will be used throughout the site. Also known as the glossary
D-base	/var/lib/pootle/terminology/templates/	directory where terminology POT files are stored. Also known as glossary files
D-auto	/var/lib/pootle/terminology/xx/	directory where each language keeps their terminology or glossary files
D-gui	/var/lib/pootle/_project_/	directory of a prticular pootle-project (note that there's no 1:1 correspondence with d.l.o) Note: the removal of a pootle-project has no effect on the directories and files (which must be eliminated manually)
D-manual	/var/lib/pootle/_project_/templates/	directory where the POTs associated with the pootle-project go (not accessible through the web-GUI)
D-gui	/var/lib/pootle/_project_/xx/	directory where the PO files in an associated language (using ISO 639 coding) for a given pootle-project are kept. Created when a language is added to the project.
F-auto	/var/lib/pootle/_project_/xx/pootle-_project_-xx.prefs	file that overrides the global .prefs in the context of a specific [language+project], holding the rights on a per user basis (for nobody, default & specific users). Also keeps track of the goals (name and list of files),
F-auto	/var/lib/pootle/_project_/xx/pootle-_project_-xx.stats	file holding for each PO file in the project six numbers (pressumably translated words, translated strings, non-translated words, non-translated string, total words, and total strings)
F-gui/rcs	somefile.po	the actual PO file.
F-auto	somefile.po.pending	if suggestions have been made, they are stored here in a pseudo-PO format that modifies the msgid (appends a "_: suggested by username\n" line). See #Bug dealing with Suggestions.
F-auto	somefile.po.stats	statistics about the internals of the file, apparently only about the checks and their results.
F-manual	somefile.po.tm	the results of applying a translation memory to that file, pressumably the suggested string translations.

To Do

Usage

• Merge of uploaded PO
• Check if there any kind of verification when a PO file is uploaded to ensure the up-to-dateness of the original POT on which it is based? (ie: a PO is loaded but the POT on which it is based is a an older version)
• Update from templates (this needs the git interface on one side, but also if a POT is updated by whichever means, the PO should be merged/solved)
• Define a workflow! — the #Basic Scenarios above just cover the translator part. After the git interface is tested, the handling of the developer input, and the Pootle output must be defined.

Config

• Interface with GIT — both on importing POTs & POs from it & exporting POs back to it.
  • Version Control doc (scant doc on configuration)
  • Alfonso has patched the server with the git support and installed git in the server. So we should be almost in condition to start testing against dev.laptop.org.
• For completion's sake, language plurals & associated formulas must be defined (a bit pointless if developers don't actually do i18n right though, but...)

setting up

Please note that we are grouping the projects found in d.l.o into two base projects for localization: core & bundled. Other projects that are not found in the builds, will have a case-by-case decision on where to included them (either in an independent pootle-project, or grouped with other 'extras'). Given this grouping, we must ensure that no files will conflict in their naming, so the first approach is to prefix their POT filenames with their project name, ie: the Chat.pot of the chat-activity will be chat-activity.Chat.pot in Pootle. This in turn means that all the .PO files will be named chat-activity.Chat.po (but in different per-language subdirectories).

1. First obtain a local clone in the Pootle server machine of the project(s) that needs to be included (see Pootle/Files for some notes).
   • Create the appropriate pootle-project for the git-project
   • Copy the .POT file from the git clone into the /templates directory of the pootle-project

     (may need to create this directory as a subdirectory of the pootle-project directory)

   • Associate the initial languages (am, ar, en, es, fr, ha, hi, ig, ne, pt, ro, ru, rw, th, ur, & yo)
   • Select the languages and perform an Update from templates in order to generate the initial (empty) PO files for each language
2. If the project includes pre-existing PO files, they need to be merged and included:
   1. merge previous work by executing
      msgcat --use-first -o /__git_path__/xx_YY.po /var/lib/pootle/__project__/xx_YY/__project__.__foo__.po /__git_path__/xx_YY.po

      this takes the initial clean Pootle generated PO file and populates it with the msgstr from the git PO file; while it also ensures that Pootle's basic and standard header is preserved (more specifically the timestamp of the source POT file)

   2. copy the file back into Pootle with:
      cp /__git_path__/xx_YY.po /var/lib/pootle/__project__/xx_YY/__project__.__foo__.po
   3. delete (the now obsolete) Pootle statistics (that will be re-generated on-demand):
      rm /var/lib/pootle/__project__/xx_YY/__project__.__foo__.po.stats

Done

• user creation (both through the admin & registration interface that uses confirmation codes via mail)
• add / remove languages (basically reduced the set to green countries languages in order to focus attention)
• add project (only one for 'olpc' — deleting is performed through the GUI.
• associate languages & projects
• define permissions for nobody, default and specific user
• upload PO file (note: it doesn't verify against the templates, so you may end up uploading anything anywhere... handle with care)
• translate on line — may be a bit slow although it could be the browser, connection or server (see #Advanced site administration)
• used the suggest funcionality, hit bug with review (see #Bug dealing with Suggestions)
• Define goals
• Assign translations
• Delete files (this is done outside of Pootle directly on them... some things will protest, but is the 'accepted procedure')

Glitches

• Something related to encodings was wrong during the setup

  Alfonso commented several language specs that apparently were iso8859 instead of UTF ??

Bug dealing with Suggestions

There seems to be something awry with the suggestions... somehow there seems to be a mismatch between the msgid for which the suggestion was made, and the msgid displayed in the review process. IOW, you suggest foo as a translation of bar, but in the review process it will show it as a suggestion for xyzzy!! review problem!

Talking in IRC#pootle, the following emerged: the mechanism used to associate a given suggestion is based on the #: comments (usually documenting the source code line where the string is located). This mechanism fails when there are more than one strings extracted from the same source line.

Possible solutions & workarounds

the problem is relatively serious as it inhibits the #Opportunistic translator (or any other translator) from making suggestions (as they may get lost).

• modify the source code to avoid having more than one gettext string per line.
• modify the POT to avoid duplicate comments (iow, a manual process)
• disable the suggestions
  • explore the possibility of having the offending POT in another project where suggestions are not allowed (thus avoid reviewers get bitten by it).
• patch Pootle (or file a bug)