I've frozen the translatable strings for 3.0.0 and called for updated translations. If you're a translator on this list and haven't received the PO file, let me know. http://lists.debian.org/debian-i18n/2009/08/msg00102.html Drivel has a complicated history and has a lot of GNOME-ness embedded in various layers, especially translations where translators were given direct commit access to svn.gnome.org - this became problematic when drivel had to move to svn.sourceforge.net :-) Until 3.0.0 is released, there are still two active branches in drivel as well, with subtly different translation strings. 3.0.0 brings those together, which is why some translations for 2.0.4 have not been carried forward into 3.0.0 because an existing translation from the other branch (2.1.1) was more complete. It's quite a mess. 2.1.1 was left behind because it was still using deprecated GTK code and libgnome etc. drivel 3.0.0 is GTK+3 ready, hence the major version bump - I've made a lot of changes to get from 2.0.4 through 2.1.1 to 3.0.0. Therefore, translator details for 2.0.x may have been overwritten by translator details from 2.1.x and I'm trying to bring the whole lot back together for 3.0.0 so that there is one trunk/, one set of PO files, one set of translators and one set of language teams. I don't mind whether those teams are GNOME based or Debian based - as long as the translators and teams are responsive and don't use subscriber-only mailing lists. (vi, sv, es and nb did this; sv already has a replacement. Unless I hear from the others, they too will (forcibly) be replaced with Debian teams.) This also means that no more new functionality is going into drivel 3.0.0 - once the remaining bugs are fixed and the deadline for updating translations has passed (30th September 2009), I'll make the 3.0.0 release from SVN trunk at SF, using the SF file release system and all branches will become obsolete. The extra long deadline is for two reasons: 1. I'm not sure if the current blocker issues (LJ support) will be fixed by then. (See other mail) 2. The mess with the current translations needs time to be sorted out so that I can give a reasonable period before giving up on inactive translators and seeking updates from others. It's likely that drivel 3.0.0 will release with an incomplete libsoup transition, as long as the LJ support can be fixed. It's not ideal carrying code from libsoup2.2 and a goal of 3.1.0 will be to remove it. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpDbC7eoVvCz.pgp
Description: PGP signature