[Wesnoth-dev] Translations and the release cycle time
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 happened, so a change in cycle length has little room to affect it. On the addition side, the seven new campaigns during 1.3 is a burst of additions that I think is quite unlikely to be duplicated in the future. For 1.5 my most optimistic projection is to do two lifts, Delfador's Memoirs and Legend of Wesmere, and nobody else is planning any lifts at all AFAIK. (If we go to a 6-month cycle I'll cheerfully settle for just one of those.) On the subtraction side, I think I've eased the pressures that used to lead to campaign removals a lot by (1) writing the sanity-checkers, and (2) inventing the role of mainline campaign maintainer. We now have at least three of those -- zookeeper, Mythological, and me -- and judging by the low frequency of campaign bugs reported on the tracker I think we're doing a good job of keeping on top of the problem without overworking anyone. In truth, I think we could as much as double the number of campaigns we now carry without straining the mainline maintainers unduly. -- a href=http://www.catb.org/~esr/;Eric S. Raymond/a ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Translations and the release cycle time
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 campaigns there needs to stop or at least be moved to a side directory marking it clearly apart. Commits to the actual campaigns may only be done through the campaign server. Outside commits are restricted to po/. David ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Translations and the release cycle time
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 href=http://www.catb.org/~esr/;Eric S. Raymond/a ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Translations and the release cycle time
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 maintainers declare each scenario to be either 'ready to translation', 'expected to get fuzzy' or 'expected to undergo huge string changes' 3) This status is reevaluated two months from planned relase date. At this point no scenario should get 'huge changes status' and adding completely new scenarios should be avoided. We should probably also state which campaigns do we plan to lift to mainline at the beggining of each cycle to save translators work on a strings that will probably change drasticaly during the process. This, assuming 9 month relase cycle gives 7 months for developers to do rather drastic things if necessary and 4,5 for translators to work on mainlined content with at least two months guarantee of no huge changes. is it easy to make a campaign untranslatable or partly untraslatable in a meaningfull way, i.e not relly on conventions with translators, but relly on the strings not being in the PO if they are not ready ? that might simplify the extra work quite a bit... ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
