Pootle

Olpcboxes Contact: Alfonsodg —Rafael Ortiz, Xavi

Here's a report of trying to document the ups & downs of installing Pootle.

Proving Grounds

We are currently testing in an ad-hoc trial site

• configuration
• olpc project statistics

  (PO files were uploaded from fedora—except spanish, which came from the PO versiona in the wiki)

Language	Translated		Fuzzy		Untranslated		Total	Diff.Spanish
arabic	198	78%	7	2%	48	18%	253	1425
portuguese BR	174	84%	12	5%	19	9%	205	1473
french	144	67%	15	7%	53	25%	212	1466
portuguese	12	42%	0	0%	16	57%	28	1650
spanish	1336	79%	342	20%	0	0%	1678

Observations

• Casual translators may only 'suggest' translation
• You can download the PO, so there's no forcing of the on-line UI.
• In the translation interface, fuzzy entries are grayed out and there's a gray vertical line separating the terms

To Do

Usage

• Define goals
• Explore the 'suggest' function & review process
• File maintenance: rename, delete files? How is it done? (ie: uploaded a file with a name that has no POT should not be valid—but I've done it—so if it was a mistake, how do you undo it?)
• Is 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)

Config

• Interface with GIT — both on importing POTs & POs from it & exporting POs back to it.
  • Version Control doc (scant doc on configuration)
• Verify the registration via email

Glitches

• Something related to encodings was wrong during the setup

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

• Haven't found the way to read / load the .POT files using git
• User permits seem a bit awkward (per user, no groups except for 'nobody' & 'default')

See also

• http://wiki.creativecommons.org/Translating_with_Pootle