As I've commented to Christian Kirbach in private mail, when I generated the reports before a new stable release, I didn't get this kind of errors, so I'm really confused about what is happening. The only difference I see is that I used to generate them under Ubuntu 12, and now I'm using Debian... maybe it's due to Python versions? I'm installing a virtual machine to investigate it...
Anyway... simply ignoring the translator-credits line would be enough to have good reports. Media links are not used at all in the PO files, so it doesn't matter how you translate them; about placeholders, they should placed in the right place, as they often indicate the kind of license or the name of the program, so they should be, at least, the same in the translated and in the original string (but not in the same order....). Thanks to all of you for your comments (and special thanks to Ask for taking care of this :) ) Cheers! 2014-05-09 19:44 GMT+02:00 Rūdolfs Mazurs <rudolfs.maz...@gmail.com>: > Pk, 2014.05.09. 16:51 +0000, Rafael Ferreira rakstīja: > > If someone that knows python3 could patch pyg3t to fix this, I think > > it would be a great tool for this XML validation... Someone? > > specifically in "translator-credits" strings, the e-mail is often put in > angle brackets, which is not a valid XML. > > If the translator-credits string is parsed with XML, that IS a bug. > Otherwise just skip the translator-credits string in the xml check. > > -- > Rūdolfs Mazurs <rudolfs.maz...@gmail.com> > > _______________________________________________ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n >
_______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
