[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted po-debconf 0.5.0 (all source)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue,  8 Oct 2002 22:11:28 +0200
Source: po-debconf
Binary: po-debconf
Architecture: source all
Version: 0.5.0
Distribution: unstable
Urgency: low
Maintainer: Denis Barbier <barbier@debian.org>
Changed-By: Denis Barbier <barbier@debian.org>
Description: 
 po-debconf - Manage translated Debconf templates files with gettext
Closes: 163597
Changes: 
 po-debconf (0.5.0) unstable; urgency=low
 .
   * po2debconf:
       + Replace --encoding=traditional by --encoding=popular.
       + Default output value is set to 2, which means that
         Description-de.ISO-8859-1 or Choices-ru.KOI8-R fields are printed
         instead of Description-de and Choices-ru.
       + When po or UTF-8 encoding is used, always set output value to 2.
         (Closes: Bug#163597)  Thanks Tomohiro Kubota.
       + Format may also be specified in debian/output file, e.g.
           echo '2 utf8' > po/output
   * debconf2po-update:  POTFILES.in was searched in directories
     po:debian/po:../po in that order, and now in debian/po:po:../po
   * Update intltool scripts with latest CVS
   * intltool-extract:  In PO and POT files, sentences in a multi-paragraph
     string were not displayed in input order.
Files: 
 7779a6c02825bcb206958b0341e33a5f 514 devel optional po-debconf_0.5.0.dsc
 6a5ca6750b100dd4220af6dcd72407a2 45088 devel optional po-debconf_0.5.0.tar.gz
 e68ef9c41dd1b1886bff6fca3ae76570 39424 devel optional po-debconf_0.5.0_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE9o0TS8Ri1lR4WGvsRAmSLAKDAXU1QJ0fk5u38CbOdGoCRU2K6DACbBr1P
MPieVARpcnAUUwIdrzIFZns=
=g8Eg
-----END PGP SIGNATURE-----


Accepted:
po-debconf_0.5.0.dsc
  to pool/main/p/po-debconf/po-debconf_0.5.0.dsc
po-debconf_0.5.0.tar.gz
  to pool/main/p/po-debconf/po-debconf_0.5.0.tar.gz
po-debconf_0.5.0_all.deb
  to pool/main/p/po-debconf/po-debconf_0.5.0_all.deb



Reply to: