Translate Toolkit & Pootle

Tools to help you make your software local

User Tools

Pootle TODO

This is a wikified version of the Pootle TODO that lives in CVS at Pootle/TODO

It will require maintenance from time to time as a result…

Current Tasks

  • upload submissions as po file / zip
  • assigning stuff to people (package + email too)
  • upload completed work (by maintainer)
  • what has been returned, what hasn't
  • ability to send work to people
  • let maintainer add people manually
  • create / review goals
  • localize pootle
  • create po files
  • set language on login
  • priorities (directory/file order)
  • migration to Django toolkit


  • process (administrators/translators/reviewers)
  • locking
  • allow search to display only items related to search (no context)
  • add ability to email bug report

Requirements for [[Translatathon]]

  • assigning stuff to people (with permissions)
  • both translation and review
  • attribution (based on login)
  • last translator
  • comment with everyone at top of po file
  • comment in suggestion
  • translation review cycle
  • comment to explain rejection
  • highlight spaces in original so you can see what is a space

Other Tasks

  • handle plurals properly (currently ignored)
  • add ability to mark/unmark things as fuzzy
  • move the sidebar to be like distributed proofreaders (at the top, small)
  • test with apache multiprocess
  • store a history file
  • maybe have a separate file to track who translated each string
  • display results of checks for each string on submission
  • handle language subtypes (regions)
  • handle project versions
  • have clickable characters to add for a language (mostly useful for diacritics)
  • allow user to copy original to translation
  • a reviewer can mark as string as fuzzy but not provide a translation (inorder to browse and fixup things like af KDE).
  • integrate with KBabel/POEdit
  • allow XLIFF version of files to be downloaded/uploaded
  • show KDE and other PO comments in some uncluttered but accesible way
  • create Gettext .mo/.gmo (compiled .po) files that can be downloaded and run. Similarly
  • allow creation of .qm (compiled Qt .ts files).
  • See pygettext for .mo files and lrelease which is GPL'd for Qt .qm files
  • create XPI files automatically when updates are made
  • Add X-Poedit style tags in the header when you download so that people usingthis PO editor don't have to configure everything


  • percentage change. So you can see if a language/project is active or not.
  • if there is only one .PO firl for a project then merge the header bar and the PO file bar to make it less clutered and more logical.
  • goto a specific message. Maybe a better thing to have a bar graph showing what bits aren't translated and jump straight to that.