Re: Arabic L10n - 2.8

Je 2011-Jul-09 je 13:07, Chris Leonard skribis:
> On Sat, Jul 9, 2011 at 12:21 PM, Keith BOWES <zooplah@gmail.com> wrote:
> > Je 2011-Jul-09 je 00:07, Chris Leonard skribis:
> >> Dear AbiWord devs,
> >>
> >> Attached please find the completed Arabic PO files for 2.8 courtesy of
> >> the Arabic team at Sugar Labs / OLPC / eToys Translation team.
> >>
> >
> > Is there any way to submit the updated PO files via Pootle?
> >
>
> Keith,
>
> Short answer: No, but there could be.

Whoa. One thing I liked about when I translated Midnight Commander was
that I just translated it and submitted the PO file to Transifex and
then all the languages were merged to the Midnight Commander git
repository in the next version. It seemed to be pretty much without
hassle for the translators, developers, and repository managers.

>
> Long answer:
> Pootle does have a feature that allows for setting up direct commits
> from Pootle to a repo. We have not established this direct commit
> connection for AbiWord yet. but we may discuss it with the Sugar Labs
> and AbiWord infrastructure teams to coordinate it in future. There is
> an extra step in AbiWord L10n (converting PO to .strings) that would
> have to be scripted for complete automation.
>
> Just FYI, here is an explanation of how it would work (and currently
> works for Sugar and other projects on our Pootle instance).
>
> 1) A repo user named "pootle" is created and given commit priv to the
> project repo, it typically only makes commits to the directory where
> the POT and PO files are stored. Sugar Labs has such a git:pootle
> user and it has an SSH key that could be used (if needed). Pootle
> needs to exercise some control over the PO directory because it tracks
> versioning, etc. We've had some problems with automated template
> updates (from repo to Poolte), but we are working through them.
> Manual fiddling with the files in that directory can create error
> messages and be a general pain, so typically there needs to be a
> decision to turn PO commits over to Pootle for the most part.
>
> 2) Configuration / set up is done on the back end of Pootle that
> points the specific Pootle project to the specific repo for the PO
> file. This serves for Pootle-to-repo and repo-to-Pootle information
> transfer.
>
> 3) Pootle users granted "language administrator" status (lang admins)
> are presented with a "Commit to VCS" option for the PO files in their
> language in the Poolte web UI. They are expected to review and QA
> files before committing them to the repo. Non lang admins may
> request commits by posting to the L10n list.
>
> About our lang admin granting process:
> We have a small group of known and trusted native speakers for most
> languages, in some cases we do not have a lang admin (for some less
> active lang projects). I try to recruit users that show a history of
> contributing to langs to act as admins. We try to keep lang admin
> requests and grants on the L10n list (to make them public and open to
> comment). For new langs, the lang admin is often the person
> requesting it be set up. For some langs, we defer to the selection
> advised by an OLPC deployment partner (e.g. Dari/Pashto for OLPC
> Afghanistan, Nepali for OLE Nepal) as they have to live with the
> strings and they are responsible for the use of these strings by
> children in their country.
>
> 4) When the lang admin does a "Commit to VCS" what happens is that
> Pootle (via the repo pootle user) "lends" them the repo commit priv
> (limited to their language) by acting as a proxy for them in
> committing it, also recording and publishing the Pootle username of
> the admin making the commit via Pootle in the commit message. This
> essential a "chain-of-trust" type situation with the management
> happening via the lang admin granting process on Pootle, which is
> managed by Pootle admins (usually me, but also a few other Sugar Labs
> sysadmin-priv level types).
>
> Things are a bit hectic at the moment. OLPC is coming up on a major
> release (11.2.0), so any attempt to set up direct commits will have to
> wait a little while. For now, Poolte serves as a useful collaboration
> and QA workflow platform supplementing the existing AbiWord commit
> process via this list and I will work with AbiWord devs to keep things
> synched up manually.
>
> cjl

-- 
Keith Bowes <http://zooplah.farvista.net/>