[Wesnoth-dev] Translations and the release cycle time

2008-03-02 Thread Eric S. Raymond
ott [EMAIL PROTECTED]: So if short release cycles mean lots of campaign churn, expect reduced translation activity. I don't think these two things are coupled. For one thing, I think most of the campaign churn we're going to see in the foreseeable future has already

Re: [Wesnoth-dev] Translations and the release cycle time

2008-03-02 Thread David Philippi
Am Sonntag 02 März 2008 schrieb Nils Kneuper: And one requirement before anything gets lifted from now on is 2 complete months with the *revised* texts in wescamp. I do not want to see such Just to make sure... 1. WesCamp-i18n is currently not supported well by g.w.o ... 2. Developing

Re: [Wesnoth-dev] Translations and the release cycle time

2008-03-02 Thread Eric S. Raymond
Nils Kneuper [EMAIL PROTECTED]: And one requirement before anything gets lifted from now on is 2 complete months with the *revised* texts in wescamp. I do not want to see such excessive stringchanges to happen again when the content is already in mainline. Fair enough. -- a

Re: [Wesnoth-dev] Translations and the release cycle time

2008-03-02 Thread jeremy rosen
This is a basic idea tought on the fly. 1) Any mainline content is a no-go zone for translators for the first half of the development cycle. That is you can translate things, but they might get changed and reverted at any moment due to various reasons. 2) At the half point campaign