-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody! I just splitted the new 1.6 stable line off into its own branch (branches/1.6) and updated gettext.wesnoth.org to automatically show the stats for 1.6. So far the stuff for wescamp was not implemented yet and will be done later on (at the moment there is an error message in this, just ignore it, the normal mainline stuff works as expected...).
The basic rules for 1.6.x will be rather identical with the stuff for 1.2 and 1.4 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.6 (in trunk as well). This lead to the wesnothd manpage being too incomplete for file generation in every language. Beside this some other some changes/additions happened that require your attention. In general I will for the moment commit all your work to trunk and 1.6. You can either get yourself a checkout of branches/1.6 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.6 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.6" I will apply the update to both branches. Announcement: I had to "re-tag" 1.6 due to some severe problems with the AI in the "normal version". Now there is a 1.6a. For you this *should* not mean much of an extra effort. I already fixed the links in the original and in all the translation files, so at the moment you have *no* fuzzy strings in there. I will also check right before announcing if the links in the versions that have created html files are working. Just for you as info (and to directly fix it in your po files if you have uncommitted changes) now a list of changes: wesnoth-1.6.tar.bz2 -> wesnoth-1.6a.tar.bz2 wesnoth-1.6-windows.exe -> wesnoth-1.6a-win32.exe Wesnoth_MacOSX_1.6.dmg -> Wesnoth_1.6a.dmg So much about the announcement, it is still planned for Sunday in the afternoon. This should be everything for the moment, I will keep you informed when any new things pop up. Cheers, Nils Kneuper aka Ivanovic -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknDySQACgkQfFda9thizwXKUgCeNnXIcxfYEO7i8YM1fdhgvwC1 j38Ani89aEYe7197BATdxczpUnTUKP/Y =lV/A -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-i18n mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-i18n
