Your message dated Thu, 13 Apr 2006 06:17:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326670: fixed in po4a 0.25-1
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 ---
Package: po4a
Version: 0.21-1
Severity: wishlist

Hello,

As discussed on #po4a tonight (in French, see the censured attachment),
po4a-gettextize could detect that an original string (used multiple times
in the original document) has different translations (or that different
strings in the original document are translated in the same way).

Basically, the irc log indicates that we can find the number of references
in the PO.pm gettextize funstion (files are separated by a line reference
and a blank), and if one of the file has more references than the other,
we can issue a warning, but still continue (until we fail on a type
mismatch, or until we succeed to gettextize the whole file).

Thanks in advance,
-- 
Nekral
21:49 < emptty> > msgid "optional"
21:49 < emptty> > msgstr "optioneel"
21:49 < emptty> >
21:49 < emptty> > l�, il existe une autre traduction, pour optional, � savoir 
naar keuze.
21:49 < emptty> >
21:49 < emptty> > -> �chec.
21:49 < emptty> >
21:49 < emptty> > la chaine naar keuze sera affect�e � un autre message.
21:49 < emptty> > C'est pas possible d'�viter ce comportement ?
21:50 < emptty> Y'a deux interpr�tations du "on peut pas �viter ca?", toutes 
les deux aussi chalenging
21:50 < emptty> La premiere est de permettre de traduire le meme morceau de 
deux facons diff�rentes selon le contexte
21:50 < emptty> Faut inventer une facon de pr�senter l'alternative pour que 
po4a comprenne
21:51 < emptty> une facon de faire des sequences d'�chapement, or so
21:51 < emptty> La seconde, c'est de faire en sorte que la gettextization se 
rende compte qu'un bout identique en anglais est traduit de facon diff�rente
21:52 < emptty> et se resyncronise juste derriere
21:52 < emptty> Attend
21:52 < emptty> Ca, c'est peut etre faisable
21:54 < nekral_> En tout cas ce serait super d'avoir �a
21:54 < emptty> la premiere ou la deuxieme?
21:55 < nekral_> d�j� la deuxi�me
21:55 < nekral_> la premi�re serais tr�s bien, mais c'est trop pour un PO
21:55 < nekral_> dans du XLIF (ou un truc qui ressemble � ce nom), il me semble 
qu'on peut stocker des alternatives/les derni�res traductions
21:56 < nekral_> l� on pourrait faire la premi�re "facilement"
21:56 < emptty> c'est raisonnable
21:56 < emptty> on oublie la premiere, on cherche � faire la seconde
21:57 < nekral_> Tu avais une piste ?
21:57 < emptty> oui
21:58 < emptty> Po.pm, regarde la fonction de gettextization
21:58 < emptty> Elle est assez simple
21:58 < emptty> On fait un po de l'anglais, un autre po du francais, et 
ensuite, on parcours les deux en //
21:59 < emptty> On v�rifie que les types correspondent en garde fou, mais 
sinon, c'est aussi con que         $pores->push_raw('msgid' => $orig, 'msgstr' 
=> $trans)
22:00 < emptty> Pour le cot� deux traductions diff�rentes, il suffit de 
d�tecter que msgid=$orig est d�j� dans le fichier
22:00 < nekral_> On a le compte d'occurences pour les chaîne orig et trad ?
22:00 < emptty> dans les r�f�rences, de maniere un peu masqu�e
22:01 < nekral_> C'est un tableau, ou une chaîne avec des noms de fichiers 
s�par�s par des espaces ?
22:02 < emptty> chaine, je pense
22:02 < emptty> Les tableaux, faut jouer avec les \@, c'est chiant, je me 
gourre tout le temps
22:02 < emptty> Mais un split et tu l'as ton tableau
22:02 < ptitlouis> mon dieux, j'ai encore rien pig� aux references en perl moi
22:03 < nekral_> Qu'est-ce qu'il se passe si un fichier a un espace dans son nom
22:04 < emptty> T'es niqu�, pourquoi?
22:04 < emptty> :-/
22:04 < emptty> Enfin, tu peux chercher ':[0_9]* ' comme s�parateur
22:04 < nekral_> Ah oui, y'a les num de ligne.
22:05 < emptty> Ca serait vraiment vicieux de donner un nom de fichier qui 
plante cette regex
22:06 < emptty> Bref, y'a moyen de contourner au moins le pb des traductions 
divergentes de la meme chose
22:07 < emptty> Pour les traductions convergeantes, il te faut une table 
associative inverse, msgstr->msgid
22:08 < nekral_> Bon emptty, �a doit �tre faisable en comptant le nombre de 
r�f�rences, ont fait un warning disant qu'on poursuit la recherche en ignorant 
une chaîne

--- End Message ---
--- Begin Message ---
Source: po4a
Source-Version: 0.25-1

We believe that the bug you reported is fixed in the latest version of
po4a, which is due to be installed in the Debian FTP archive:

po4a_0.25-1.diff.gz
  to pool/main/p/po4a/po4a_0.25-1.diff.gz
po4a_0.25-1.dsc
  to pool/main/p/po4a/po4a_0.25-1.dsc
po4a_0.25-1_all.deb
  to pool/main/p/po4a/po4a_0.25-1_all.deb
po4a_0.25.orig.tar.gz
  to pool/main/p/po4a/po4a_0.25.orig.tar.gz



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Quinson <[EMAIL PROTECTED]> (supplier of updated po4a 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 [EMAIL PROTECTED])


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

Format: 1.7
Date: Thu, 13 Apr 2006 11:08:43 +0200
Source: po4a
Binary: po4a
Architecture: source all
Version: 0.25-1
Distribution: unstable
Urgency: low
Maintainer: Martin Quinson <[EMAIL PROTECTED]>
Changed-By: Martin Quinson <[EMAIL PROTECTED]>
Description: 
 po4a       - tools for helping translation of documentation
Closes: 326670 359352 360141 362169
Changes: 
 po4a (0.25-1) unstable; urgency=low
 .
   New upstream release (no change in packaging):
 .
   [Nicolas François]
   (Po.pm)
   * Missing =back in the pod part.
   * consecutive escaped tabulations in the PO: only the first one was
     un-escaped. Closes: #359352
   * gettextize: do not associate the strings by their order in the POs, but by
     their order in the documents. This permits to gettextize documents
     which have the same structure, but where a string have
     multiple translations, or when different strings have the same translation.
     If multiple translations appear for a string, both strings are proposed in
     the PO. Closes: #326670
   (po4a)
   * When a master document is specified twice in a configuration file:
     - do not ignore the options specified in the first line;
     - also warn in this case since po4a may not do what the user wants.
   * Fix the documentation: po4a do not use the POT-Creation-Date field of the
     POT and PO headers. It only updates the POs with msgmerge -U.
     Closes: #360141
   (Man.pm)
   * Documentation: this module is no more beta.
   * Another fix for "when a font modifier if followed by another font
     modifier". Also add a test for this case.
   * mdoc support.
   * Do not put the header at the top of the file, but just before the .TH
     macro. This will preserve the indications on how to process the page if
     the first line contains something like: '\" t
   (Xml.pm)
   * Implement placeholders: this permits to specify that footnotes must not be
     translated inside a paragraph, but are translated separately and a
     <placeholder0> tag will be put where the footnote must be installed.
   * In tag_extract_doctype, we can't test whether the Document Type Definition
     contains an Internal Subset by searching the document for "]>" because
     this is also used for closing the CDATA Sections.  This caused
     segmentation faults.  Closes: #362169
   * get_string_until: add a option to search a regular expression.  The
     default is to search for a fixed string.  Also make sure get_string_until
     works when the serach string (or regex) contains a newline (\n).
   * When there is an Internal Subset, the Document Type Definition ends with
     "]\s*>", not necessarily "]>".
   * Add support for CDATA Sections.
   (po4aman-display-po)
   * new script to display a translated man page with a given PO.
     Thanks to Thomas Huriaux.
   (po4a.7.pod)
   * Fix a typo in the detailed example for the beginboundary field.
     Thanks to Ognyan Kulev.
Files: 
 e3f7a3e0791804ebff0f4bb3e44eef58 714 text optional po4a_0.25-1.dsc
 e868a14e5e5212d1e1d78e0905f01fe5 757672 text optional po4a_0.25.orig.tar.gz
 1207e3d6961e9257dbee870d2994d9e5 18920 text optional po4a_0.25-1.diff.gz
 ef629c61665625592dbf6b47d3ee6f68 668138 text optional po4a_0.25-1_all.deb

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

iD8DBQFEPk53IiC/MeFF8zQRAoZpAKDJDxi2g5DZtXDicRWC81jywkcvgACfc8YU
swgKquPckzt6F7jDeCYHakw=
=SSla
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to