[Bf-committers] i18 project pre-merge review
xiaoxiangquan at gmail.com
Mon Sep 19 14:48:32 CEST 2011
I'll CC this to blender-translation list.
We have translation branches at
I think we can set a limitation, e.g, one branch can be merged only if it
has completed at least 80% translations.
And the not-ready branches will not be a candidate in the release.
2011/9/19 Davis Sorenson <davis.sorenson at gmail.com>
> As a translator for sv_SE (Swedish as spoken in Sweden), I would just like
> to confirm that my understanding of the effects of the merge are correct:
> Only the translations that are declared by the translators to be finished
> will be included in the merge to trunk, and the translators will have to
> request that their translation be included in trunk later.
> Is this correct?
> Additionally, once the translations are finished for whichever release and
> in trunk, will there be some way for the translators to commit updates to
> the translation in trunk? Is there any plan for how this will be managed?
> Regards, Davis
> On Mon, Sep 19, 2011 at 1:53 PM, Sergey I. Sharybin <g.ulairi at gmail.com
> > Hi,
> > Looks like all issues Dalai and Thomas pointer recently are solved.
> > There are some things i want to happen before merge:
> > - New font have to be confirmed as not worse in charsets coverage. I
> > need native speakers to check because i can't actually say if all chars
> > are fine now (especially in chinese language). Xiao, can you help with
> > this?
> > - I want Campbelland/or Brecht review garlic branch before merge. I hope
> > there's no issues but extra review wouldn't hurt.
> > --
> > With best regards, Sergey I. Sharybin
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers