As for me, I can merge translations on my own (especially because I tend to polish files between releases and the POs from previous realeases are often slightly out of date). But if you could publish a POT from the trunk from time to time, I'd keep the localization for S2_4 fresh.
On 11 August 2011 07:42, Marko Lindqvist <[email protected]> wrote: > Now that 2.3.0 is finally out, I'm already busy planning next major > release (been for some time, but wanted to let you concentrate on > 2.3.0) > > S2_3 was branched 02-Nov-2010, and when exactly one year of feature > development is finished 02-Nov-2011, S2_4 will be branched. > > In earlier cycles I have merged translations from previous stable > branch well before branching in case translator wants to translate in > trunk already, resulting also trunk having good translation after > branching. Nobody has ever used that opportunity, so this time I'm not > going that route (unless somebody now requests it for his/her > language). I'll merge translations only just before branching. > Probably one day before, though, so that there is not so much work at > once when doing actual branching. This late merge has advantage that > more updated translation from S2_3 will be used. You don't need to > translate separately S2_3 and S2_4 so long. > If you want any special treatment for your language (no merge / merge > earlier...) just let me know. > > > - ML > > _______________________________________________ > Freeciv-i18n mailing list > [email protected] > https://mail.gna.org/listinfo/freeciv-i18n > -- Hubert
_______________________________________________ Freeciv-i18n mailing list [email protected] https://mail.gna.org/listinfo/freeciv-i18n
