[MeeGo-il10n] IRC meeting Thursday 1400 UTC
michal at sawicz.net
Mon Sep 13 14:32:56 PDT 2010
Dnia 2010-09-13, pon o godzinie 23:07 +0200, Marcin Sołtysiak pisze:
> Dnia 2010-09-13, pon o godzinie 13:58 -0700, Auke Kok pisze:
> > On 09/13/10 13:50, Marcin Sołtysiak wrote:
> > > 1. Each lang team appoints one delegate (a team lead) to request write
> > > access to repos. A delegate would have Margie's approval if required.
Yes, a coordinator is required, although IMO we don't need write access,
that's where gitorious helps, just have a branch and submit it as a
OTOH I am probably biased that this is an OK solution due to the fact
I'm a translator slash developer and do work with git every day, so...
> > > 2. Every team member clones a repo and creates a translation
I'd add a "and adds him/herself to the wiki page, 'locking' the
> > > 3. Translation is sent out to the il10n list with subject prefix like
> > > "[pl] TS file for component-name"
> > > 4. Lang team is reviewing the translation. Once completed, team lead
> > > commits a translation file and makes appropriate changes to .pro file if
> > > needed.
Fine with me. Although I do fear that most of the 'teams' are too small
to actually do any reviews. I think this can be optional, we didn't do
mandatory reviews on Tx either.
> > > The manual translation is done on lang team members computers, then
> > > reviewed and approved by the team with final word in hands of team lead.
> > > This way all effort is well coordinated by lang team and we omit the
> > > problem of overwriting one's effort.
> > I'm really not fond of taking back 3 steps again, we had this all
> > working without developer interaction and it seems we're back to the
> > stone ages...
AFAIK It's either that or no l10n for 1.1. I prefer to do it the hard
way as opposed to not doing it at all, just this time.
> > - autodetected languages based on presence of .ts files, build code
> > does all the work without the need for hardcoded language lists.
There's one issue - there's no concept of a template in TS translations.
That means we either need to add a new language to the .pro file and run
lupdate to generate the translations for us or get a .ts file for
another language, change the translation language and replace the
strings used. I'd rather have a clean, lupdate-generated file to avoid
breakage. But if we can't get that, everything will do.
Michał (Saviq) Sawicz <michal at sawicz.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the MeeGo-il10n