Please allow gettext 0.16.1-1 in testing

[Santiago Vila <sanvila@unex.es>]

The main reason is that it fixes #400187, which is an important bug
(well, maybe serious).

gettext (0.16.1-1) unstable; urgency=low

  * New upstream release. See the NEWS file for details.
  * Use -no-site-file instead of --no-site-file, to make xemacs happy.
    Thanks to Luis Rodrigo Gallardo for the report. Closes: #399284.
  * Fixed xgettext segfault with lisp files, which made other packages
    to FTBFS. Thanks to Martin Pitt for the report. Closes: #400187.

 -- Santiago Vila <sanvila@debian.org>  Mon, 27 Nov 2006 23:31:08 +0100

Secondary reasons, but also interesting:

* It has been 12 days in unstable and no new bugs have been reported:

     * gettext (0.15-3 to 0.16.1-1)
          + Maintainer: Santiago Vila
          + 12 days old (needed 10 days)
          + Not touching package, as requested by freeze (contact
            debian-release if update is needed)
          + Not considered

* In the author's opinion, the jump from 0.15 to 0.16.1 should be smooth,
compared with the jump from 0.14.6 to 0.15 (which caused problems because of
msgfmt being more strict).

  * Possible exception to the avobe: msgcmp, but almost nobody uses it.

  * Real exception to the above: lintian, but a version which works with
    gettext 0.16.1 is already in unstable and it's 6 days old.

* It opens the door for automake-1.10, which is 45 days old, in case
we would need to have it in testing (which I think it would be good,
since some packages already in etch use automake-1.10 internally).


Follows the NEWS file for gettext:

--------------------------------------------------------------------------

Version 0.16.1 - November 2006

* Bug fix in the gettext.m4 autoconf macros.

Version 0.16 - October 2006

* Interoperability with automake-1.10.

* msgmerge has a new option --previous that has the effect of saving the
  previous msgid of message when making them fuzzy. These previous msgids are
  stored in the resulting PO file, using a pseudo-comment syntax like this:

     #, fuzzy
     #| msgid "too many arguments"
     msgid "too few arguments"
     msgstr "trop d'arguments"

  The translator then only needs to compare the previous and the current
  msgid ("too many arguments" and "too few arguments"), and infer which
  parts of the translation she needs to change.

  msgattrib has a new option --clear-previous that removes these #| lines.

* msgmerge is faster now on CPUs with multiple execution units, if compiled
  with GCC 4.2 or newer.

* msgcmp now ignores fuzzy and untranslated messages in the PO file.
  Previously it considered fuzzy and untranslated messages the same way as
  translated messages, which was hardly useful.  The previous behaviour can
  be obtained through the options --use-fuzzy --use-untranslated.

* gettextize, when invoked without --intl option, now installs only the .m4
  files that are needed: gettext.m4, iconv.m4, lib-ld.m4, lib-link.m4,
  lib-prefix.m4, nls.m4, po.m4, progtest.m4.

* gettextize no longer creates symbolic links by default; it makes file copies
  instead.  The option --copy is removed.  You can get back the flawed
  symlinking behaviour by specifying the --symlink option.

* Autoconf macros:
  - The gettext autoconf macros now require autoconf 2.52 or newer.
  - A new autoconf macro AM_GNU_GETTEXT_INTL_SUBDIR is added. It allows to
    specify the presence of an intl/ subdirectory outside the AM_GNU_GETTEXT
    invocation.
  - A new autoconf macro AM_GNU_GETTEXT_NEED is added. It allows to specify
    the requirements relating to the GNU gettext implementation outside the
    AM_GNU_GETTEXT invocation.

* The libgettextpo library no longer exports symbols that could clash with
  symbols of the application that uses it.

* Vastly improved French translations. Thanks to Christophe Combelles.

--------------------------------------------------------------------------

Thanks.