Template talk:OBX pot

Rationale or intent

The basic idea is to add an {{OBX pot}} in each Activity page (may or not be a full blown Olpcboxes) filling in the most info available (iow, links to actual l10n files POT & POs).

The explicit language codes are those codes that belong to green countries, but without country specific postfixes (ie: no pt_BR, just pt; no es_UY, just es; etc.) This allows for categorizations based on target languages. If no PO is specified for ar that activity page will end in a Category:PO wanted lang-ar; if there's one, in Category:PO present lang-ar (or something along those lines).

Theoretically, in order to have xyzzy.rw.po, a xyzzy.rw.pot should exist - if not declared, the page will end in Category:Missing POT. This will allow us to either contact the developers, search the GIT, or just file a missing i18n ticket for said activity, which hopefully will push the developers to i18n-ize it.

In order to have the developers doing the i18n, we should give them the template hello-world on how to fully prepare their source code and directory structure. Python i18n has some info on that, but I'm not quite sure if it's what translate.fedoraproject.org actually uses (as I've seen references to some other files that guide the automation).

Comments? Ideas? --⬜⬜Xavi 17:58, 13 September 2007 (EDT)