On 12 April 2013 08:44, Jürgen Schmidt <[email protected]> wrote:
> On 4/11/13 6:21 PM, janI wrote: > > On Apr 11, 2013 11:23 AM, "Andrea Pescetti" <[email protected]> wrote: > >> > >> Rob Weir wrote: > >>> > >>> Another option is to put off the push for more languages. So with 4.0 > we > >>> just work to update the languages we already have, but bring in > > additional > >>> languages later. This might be done as a "second edition" of 4.0, as > we > >>> did with the additional 3.4.1 languages. > >> > >> > >> If we can have the new Pootle available (with no need to rush it of > > course) we could consider to make the call for translators as soon as > > Pootle is ready and the 4.0 files are uploaded. > > > > Honestly as being one of those who have actually tried 2.5, dont expect > too > > much, with our current setup there are very few differences. The > > differences will be aperant (is that the right word?) when we have > genLang > > and svn automatic comit in place. > > I think the completely automated svn commit have to be discussed. > > Do we really want it? Or is it better to have a process where we > reintegrate translation on demand or on a regular basis once per month > or so. > I totally agree, that it have to be discussed, when we are ready for it. I see a simple chain at the moment: 1) get translate-vm2 online with pottle 2.5rc1 and our 4.0 strings 2) get genLang integrated and tested for helpcontent2 3) get genLang integrated and tested for all modules 4) discuss svn-pottle-poedit workflow 5) make the scripts so it will take some time before we need that discussion :-) rgds Jan I. > > Juergen > > > > > >> > >> The consolidation of PO files does not impact very much on the > > translators' workflow and I agree it can wait until after 4.0. > > Well not the workflow, but very well the motivation, it is quite > different > > if you look at checking/editing about 240 files or just 40. > > > > But since I cannot make the deadline, sorry for that,. > > > > rgd > > Jan I > >> > >> > >> Regards, > >> Andrea. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
