User:Xavi/Spanish POs
This page has a more up-to-date location: Pootle
What is needed
The current (back in 2007!) workflow, described in Sugar i18n is only good for things kept both in http://dev.laptop.org AND http://translate.fedoraproject.org/module/ (listed under «OLPC :: xyzzy». The dynamics of the workflow are sub-optimal, which wouldn't be too problematic if it wasn't for the problem that there are quite a few activities hosted elsewhere...
This must change.
We need to know
- i18n
- split between activities that have done their i18n homework from those that haven't
- have access to some sort of 'master index of POTs'
- l10n - determine for each POT
- available POs
- status of each PO (how far it has been l10n-ized)
Having the list of all POTs, we should have an idea of the different workflows and how to coordinate with the development teams how to interface them. IOW, for things in dev.laptop.org we have the Sugar i18n; what about other development teams/sites?
Currently available
Currently I'm thinking about how to get the list of all things l10n-izables...
- we have an Activities index page,
- most activities have in-wiki pages (ie: Kuku, Write)
- activity pages (in general) have their {{Status box}} (that has a link to l10n things - but ad-hoc)
- we have a temptative replacement for {{Status box}} using Olpcboxes
general sources
Dealing only with OLPC core activities (and Fedora) is just part of the 'sources'. A sample:
| Site | Root | Comments |
|---|---|---|
| Translate Fedora Project | Release OLPC | The place where core or base activites keep it (ie: Write, Chat, Sugar, etc) |
| Translations Launchpad | Etoys | The POTs & POs for Etoys |
| sourceforge.net | trunk/PO | News Reader |
| dev.laptop.org | tree | Turtle Art |
| coderanger.net | tree | Reversi |
| tuquito.org.ar | trunk | Ecomundo |
Possible solution
All those things together give the following possible solution:
- each activity page will have a foo/POs page
- in said foo/POs the structure would be similar to foo/translations
- [link to arabic po|ar] | [link to spanish po|es] | ... | [link to chinese po|zh]
- an Olpcboxes (ie: {{OBX pot}}) would transclude said page in the activity page (much like {{Translations}} or {{Translation}})
For example there's {{OBX pot}} which can be used / reshaped.
Thoughts
- PROs
- the foo/POs can be transcluded into one big 'index' (ie: Translated pages) for fast evaluation of status
- specific categories could be added in the foo/POs denoting available languages (thus all activities can be monitored by language)
- for example besides stating in foo/POs links to each PO (ie: [link to chinese po|zh]) the following could be added (enclosed in <noinclude>):
- [[Category:PO lang-xx]] — denoting that there's a PO in said 'xx' language
- [[Category:PO lang-xx|status]] — status could be "new", "finished", "working", etc. or even "wanted" if the PO is not available (then the POs would be 'grouped' in the category page by status, or we could develop other (sub-)categories for different views - this would probably deserve some sort of template to guarantee a homogeneous and consistent classification scheme.
- for example besides stating in foo/POs links to each PO (ie: [link to chinese po|zh]) the following could be added (enclosed in <noinclude>):
- CONs
- more subpages :(
- the translating framework (much similar to this) has proven to be a bit messy
- the workflow is not addressed!
- although each language team could develop their own, it wouldn't make sense to have 5 translator teams each with a different workflow because then the developers would just go bananas...
- on the other hand, it wouldn't make much sense either to have 1 translator team deal with 5 different workflows on a per activity base...
via subpages
| Activity | Repository | POT | POs | ||
|---|---|---|---|---|---|
| Write | 1 | fedoraproject.org | write.master.pot | +/- | ar | es | fr | el | pt_BR |
Comments for this layout? Actually the {{/PO-write.master}} could actually be {{:Write/POs}}, iow, a sub-page of the activity page (which would make it easy to create a template for each row).
manual in-line links
dropping wiki-tables
Incompatible with the use of '|' as PO delimeter...