-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody! I just splitted the new 1.8 stable line off into its own branch (branches/1.8) and updated gettext.wesnoth.org to automatically show the stats for 1.8. I don't know exactly how the wescamp stuff will work out, we have to handle this separately.
The basic rules for 1.8.x will be rather identical with the stuff for 1.2, 1.4 and 1.6 when it comes to translations: * At least one week between string changes and a new release. I will announce the pot-update that introduces the changed strings on the wesnoth-i18n ml. * All translations, no matter how incomplete, will be in. If a translation needs an extra font that is not included, they should send a mail to the wesnoth-i18n mailling list and say the font-name, a link to the homepage/license. We will include that font if that translation does at least have these textdomains complete: wesnoth, wesnoth-lib, wesnoth-tutorial, wesnoth-multiplayer, wesnoth-units, one campaign. This is *only* needed to have the font included if it is not already included. All translations itself will be in anyway. String changes and how it goes on: Several strings were already updated in 1.8 (in trunk as well). This lead to several textdomains being incomplete. These are the numbers of new/fuzzy strings if your files were complete before: wesnoth: 21 fuzzy, 34 untranslated (mainly the /help stuff in the mp lobby) wesnoth-did: 1 fuzzy wensoth-httt: 1 juzzy wesnoth-lib: 2 untranslated wesnoth-nr: 1 fuzzy wesnoth-sotbe: 1 fuzzy wesnoth-units: 2 fuzzy (whitespace(indention changes only!) wesnoth-utbs: 1 fuzzy wesnoth-manpages: 3 untranslated You can either get yourself a checkout of branches/1.8 and work on this, get the files via the webinterface at gna.org or fetch them from the links from gettext.wesnoth.org. You should *not* start working on trunk right away since there will be really heavy changes. Beside this I will not run a pot-update on trunk for the next ~4 weeks. 1.8 on the other hand will be updated regularly and I will inform you about changes. Once you eventually have a commit that should *only* go to trunk, please explicitly mention that the commit is only for trunk in the mail when sending in the po files. If there is no note "this update is only for trunk" or "this update is only for 1.8" I will apply the update to both branches. The next big changes in trunk include the addition of the new campaign "Dead Water" as well as some "prose polishing" for some unit description (planned by esr). Again: you should from now on, until I tell you to do differently, concentrate on branches/1.8 instead of trunk. The 1.8.1 release is still not planned yet. But most likely there will be more than one week between the announcement of 1.8 and the release of 1.8.1. So you got at least two weeks to fix the open strings. Cheers, Nils Kneuper aka Ivanovic -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkus1bAACgkQfFda9thizwWabQCfbPpAYrkibCthp8LSzJvFynMz u18AoJ8pU6hLNX22WeGdftAxqqboAheR =ivP7 -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-i18n mailing list Wesnoth-i18n@gna.org https://mail.gna.org/listinfo/wesnoth-i18n
