Your message dated Sun, 09 Apr 2006 10:47:09 -0700 with message-id <E1FSe0D-00075P-10@spohr.debian.org> and subject line Bug#309502: fixed in developers-reference 3.3.7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: HOWTO for translation updates
- From: Torsten Landschoff <torsten@debian.org>
- Date: Fri, 18 Mar 2005 00:34:28 +0100
- Message-id: <20050317233427.GD27423@stargate.galaxy>
Package: developers-reference Severity: wishlist Version: 3.3.5 Hi there. The following message was written by Christian Perrier to debian-devel explaining how to update debconf templates if the translation remains valid (typos etc.) I think this should be added to the DR. ----- Forwarded message from Christian Perrier <bubulle@debian.org> ----- Date: Tue, 15 Mar 2005 20:55:05 +0100 From: Christian Perrier <bubulle@debian.org> To: debian-devel@lists.debian.org Cc: debian-i18n@lists.debian.org Subject: Re: Another load of typos (what to do when correcting typos in debconf templates....and want to avoid extra work to translators) Quoting Adeodato Simó (asp16@alu.ua.es): > * Christian Perrier [Tue, 15 Mar 2005 09:24:57 +0100]: > > > Indeed, typo and spell corrections should not need translation updates > > and affected translations can certainly be unfuzzied.....WHEN ONE > > KNOWS HOW TO DO THIS CLEANLY...:-) > > I've never had to to such thing, but I've wondered from time to time. > So, if I do a spell correction in a debconf template, what should I > take care of doing/not doing? (RTFM welcome if accompanied by a point > to the relevant M :). Nothing already written comes to my mind. The following is some of the practice I recommend when discussing with maintainers about such issues. This has to be followed point by point. 0) run debconf-updatepo (to be sure that ALL PO files are up-to-date with regards to your current templates, not yet modified for typos) 1) Put all incomplete PO files out of the way You can check the completeness by using: for i in debian/po/*po ; do msgfmt -o /dev/null --statistics $i ; done move all files which report either fuzzy strings to a temporary place. Files which report no fuzzy strings (only translated and untranslated) will be kept in place 2) NOW AND NOW ONLY, modify the template for the typos AND BE SURE THIS DOES NOT AFFECT THE TRANSLATIONS (typos, spelling errors, sometimes typographical corrections should not affect translations) 3) run debconf-updatepo This will fuzzy all strings you modified in translations. You can see this by running the above again 4) Run: for i in debian/po/*po ; do msgattrib --output-file=$i --clear-fuzzy $i ; done 5) move back files you moved in 1) to debian/po 6) run debconf-updatepo again Doing so, you unfuzzy in 4 all strings fuzzied by the changes in 2+3. Moving incomplete files elsewhere prevents you to clear the fuzzy marker they could have for *legitimate* reasons. Again and again, only do this when you have carefully checked that translations have no reason to be impacted by the change(s) you plan to make. And, do this exactly as I described, in the same order. Messing up with translations is *not* recommended. Doing so with the gettext tools prevents to mess up encodings (emacs can be very good at this as well as several text editors)....but you have to be sure of what you're doing, indeed....:) There are other ways, more elaborated, to do preventive modification of PO files (for instance by using sed)....which allow the "unfuzzyfication" process to be done even on incomplete files....but this is gory enough for being left to people who *really* are sure of what they do...:-) -- To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org ----- End forwarded message -----Attachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 309502-close@bugs.debian.org
- Subject: Bug#309502: fixed in developers-reference 3.3.7
- From: Andreas Barth <aba@not.so.argh.org>
- Date: Sun, 09 Apr 2006 10:47:09 -0700
- Message-id: <E1FSe0D-00075P-10@spohr.debian.org>
Source: developers-reference Source-Version: 3.3.7 We believe that the bug you reported is fixed in the latest version of developers-reference, which is due to be installed in the Debian FTP archive: developers-reference-fr_3.3.7_all.deb to pool/main/d/developers-reference/developers-reference-fr_3.3.7_all.deb developers-reference_3.3.7.dsc to pool/main/d/developers-reference/developers-reference_3.3.7.dsc developers-reference_3.3.7.tar.gz to pool/main/d/developers-reference/developers-reference_3.3.7.tar.gz developers-reference_3.3.7_all.deb to pool/main/d/developers-reference/developers-reference_3.3.7_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 309502@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Barth <aba@not.so.argh.org> (supplier of updated developers-reference package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sun, 09 Apr 2006 11:31:52 -0600 Source: developers-reference Binary: developers-reference-fr developers-reference Architecture: source all Version: 3.3.7 Distribution: unstable Urgency: low Maintainer: Debian Documentation Project <debian-doc@lists.debian.org> Changed-By: Andreas Barth <aba@not.so.argh.org> Description: developers-reference - guidelines and information for Debian developers developers-reference-fr - guidelines and information for Debian developers, in French Closes: 295483 297069 298016 299217 302000 305947 306120 306630 308103 309502 317411 320981 326857 327682 334820 336146 338660 339826 340024 341195 341197 341568 344303 347229 348160 349493 351255 351944 352749 353447 Changes: developers-reference (3.3.7) unstable; urgency=low . * Andreas Barth: - adjust information about distributions with reality. - add note on alioth accounts. Thanks, Phillip Kern. Closes: #306630 - correct manpage section of dpkg-scanpackages. Closes: #297069 - fix RFC 2440 URL. Closes: #308103 - add $arch@buildd information. Closes: #295483 - link to keyring.d.o for key replacement. Thanks, Martin Michlmayr. Closes: #298016 - add information about Packages-arch-specific. Thanks, Frank Küster. Closes: #302000 - add hint about LWN subscription. Thanks, Martin Michlmayr. Closes: #299217 - more about debconf-style translation. Thanks, Christian Perrier. Closes: #309502 - non-us discontinued. - document nmu changes wrt version tracking. Thanks, Justin Pryzby. Closes: #341197 - fix spelling issues. Thanks to various people. Closes: #336146, #326857, #338660 - update menu policy helpers. Thanks, Florian Ernst. Closes: #340024 - send mia-mail to mia@qa. Thanks, Adam D. Barratt. Closes: #341568 - Joerg Jaspert is now freenode contact. Closes: #344303 - give a clearer description of the gpg v4-key issues. Thanks, Martin Michlmayr and Peter Palfrader. Closes: #317411 - more verbose about Homepage. Closes: #339826 - add sarge and etch. Closes: #327682 - document severity of RoM-request bugs. Closes: #305947 - update FSF address. Closes: #334820 - fix P-a-s link. Closes: #341195 - reflect binNMU changes. Closes: #349493 - new security upload queue. Closes: #352749 - fix experimental's sources.list entry. Closes: #347229 - remove deprecated "Closes:..." to ACK NMU bug fixes. Closes: #353447 - when resigning, gpg-sign your mail. Closes: #348160 - make pristine source and repackaged origtargz anchors work. Closes: #351255 - same number of RC bugs is ok. Closes: #351944 - dpkg-source doesn't keep permissions. Thanks, Enrico Zini. Closes: #306120 - also mention aspell. Closes: #320981 . * Frédéric Bothamy - French translation updated to version 3.3.7, proofread by Bernard Adrian Files: 1fa3306d313ef71c320b29fc65de5a73 687 doc optional developers-reference_3.3.7.dsc a5ebba2123818aa47c897654ac1352c0 272598 doc optional developers-reference_3.3.7.tar.gz 075ee8db80660b21d2d1b51ca29e79c4 589522 doc optional developers-reference_3.3.7_all.deb 43eeb36aeb4ed2ff90bf3d2934867239 231352 doc optional developers-reference-fr_3.3.7_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEOUZDmdOZoew2oYURAurBAKCxZGWku01W9/y4hgoovvanK/0S4ACdHkMA U767wyMyp3Imd76flAehRNs= =2Xb4 -----END PGP SIGNATURE-----
--- End Message ---