Re: GTXML report: errors in documentation
Hi again, Here is an up-to-date report, with still some affected languages: ca cs de el fr gl id ja pt_BR ru if you could please review it before the release it would be great! Thanks in advance for your work El sáb., 29 feb. 2020 a las 22:40, Jordi Mas () escribió: > Thanks for generating this. It's really useful. I tried to fix most of it. > > Jordi, > > On Tue, Feb 18, 2020 at 12:13 PM Daniel Mustieles García via gnome-i18n < > gnome-i18n@gnome.org> wrote: > >> Hi all, >> >> As usual, I've created a report (attatched) with the languages >> containing typos or errors in tags in documentation files. Here is the list >> of the affected languages: >> >> ca >> cs >> da >> de >> el >> fr >> gl >> id >> ja >> pl >> pt_BR >> ru >> >> Please fix them before the new release, to avoid errors when compiling >> the affected modules. If you need help fixing it, just let me know and I'll >> help you. >> >> Regards >> >> ___ >> gnome-i18n mailing list >> gnome-i18n@gnome.org >> https://mail.gnome.org/mailman/listinfo/gnome-i18n >> > gtxml-doc-reports.tar.gz Description: application/gzip ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GTXML report: errors in documentation
Thanks for generating this. It's really useful. I tried to fix most of it. Jordi, On Tue, Feb 18, 2020 at 12:13 PM Daniel Mustieles García via gnome-i18n < gnome-i18n@gnome.org> wrote: > Hi all, > > As usual, I've created a report (attatched) with the languages containing > typos or errors in tags in documentation files. Here is the list of the > affected languages: > > ca > cs > da > de > el > fr > gl > id > ja > pl > pt_BR > ru > > Please fix them before the new release, to avoid errors when compiling the > affected modules. If you need help fixing it, just let me know and I'll > help you. > > Regards > > ___ > 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
Re: GTXML report: errors in documentation
Hi Daniel, thanks for your report. I´ll fix all the errors in gl translations ASAP. Regards, Fran On Tue, 18 Feb 2020 at 12:13, Daniel Mustieles García via gnome-i18n < gnome-i18n@gnome.org> wrote: > Hi all, > > As usual, I've created a report (attatched) with the languages containing > typos or errors in tags in documentation files. Here is the list of the > affected languages: > > ca > cs > da > de > el > fr > gl > id > ja > pl > pt_BR > ru > > Please fix them before the new release, to avoid errors when compiling the > affected modules. If you need help fixing it, just let me know and I'll > help you. > > Regards > > ___ > 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
GTXML report: errors in documentation
Hi all, As usual, I've created a report (attatched) with the languages containing typos or errors in tags in documentation files. Here is the list of the affected languages: ca cs da de el fr gl id ja pl pt_BR ru Please fix them before the new release, to avoid errors when compiling the affected modules. If you need help fixing it, just let me know and I'll help you. Regards gtxml-doc-reports.tar.gz Description: application/gzip ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GTXML report: errors in documentation
Hi Ask, Yes, but since I download all the PO files from DL in a folder an then check them I have no way to guess which module they belong to. Only the PO file might give us a clue but as you've said it's not always clear. A possible solution could be extract each set in separate folders (core, gimp-help, etc), create a single report for them and merge reports in a big one, with separate sections. I cant take a look into it ;-) Thanks! El mié., 4 sept. 2019 a las 0:06, Ask Hjorth Larsen () escribió: > Thanks Daniel. > > For future reference, it might be helpful to include also the project > directory. This is because gimp-help-2 has files like "glossary.po" > which are not sufficient to tell where the file comes from. > > Best regards > Ask > > Am Di., 3. Sept. 2019 um 12:12 Uhr schrieb Daniel Mustieles García via > gnome-i18n : > > > > Hi all, > > > > As usual, I've created a report (attatched) with the languages > containing typos or errors in tags in documentation files. Here is the list > of the affected languages: > > > > ca > > cs > > da > > es > > fr > > ja > > pt_BR > > ro > > ru > > > > Please fix them before the new release, to avoid errors when compiling > the affected modules. If you need help fixing it, just let me know and I'll > help you. > > > > Regards > > ___ > > 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
Re: GTXML report: errors in documentation
Thanks Daniel. For future reference, it might be helpful to include also the project directory. This is because gimp-help-2 has files like "glossary.po" which are not sufficient to tell where the file comes from. Best regards Ask Am Di., 3. Sept. 2019 um 12:12 Uhr schrieb Daniel Mustieles García via gnome-i18n : > > Hi all, > > As usual, I've created a report (attatched) with the languages containing > typos or errors in tags in documentation files. Here is the list of the > affected languages: > > ca > cs > da > es > fr > ja > pt_BR > ro > ru > > Please fix them before the new release, to avoid errors when compiling the > affected modules. If you need help fixing it, just let me know and I'll help > you. > > Regards > ___ > 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
Re: GTXML report: errors in documentation
Thanks for the report,I just fixed the issues with Romanian. Regards,Daniel În data de Ma, 03-09-2019 la 12:12 +0200, Daniel Mustieles García via gnome-i18n a scris: > Hi all, > > As usual, > I've created a report (attatched) with the languages containing > typos > or errors in tags in documentation files. Here is the list of the > affected languages: > > ca > cs > da > es > fr > ja > pt_BR > ro > ru > > Please > fix them before the new release, to avoid errors when compiling the > affected modules. If you need help fixing it, just let me know and > I'll > help you. > > Regards > > ___gnome-i18n mailing > listgnome-i...@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Daniel Șerbănescu, Technical aficionado GPG Key: 06C7 620D signature.asc Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
GTXML report: errors in documentation
Hi all, As usual, I've created a report (attatched) with the languages containing typos or errors in tags in documentation files. Here is the list of the affected languages: ca cs da es fr ja pt_BR ro ru Please fix them before the new release, to avoid errors when compiling the affected modules. If you need help fixing it, just let me know and I'll help you. Regards gtxml-doc-reports.tar.gz Description: application/gzip ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation
Hungarian is fixed, thanks Daniel! -- Balázs ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Errors in documentation
Hi all, I've made a report with some typos or errors in XML tags in documentation. I've attatched a file with the typos found, sorted by language. Here is the list of the affected languages: ca cs de el es fi fr hu it ja pt_BR sv zh_CN Please consider to fix them before the new release, to avoid problems when compiling the affected modules. Thanks for your attention and happy translating :) gtxml-doc-reports.tar.gz Description: application/gzip ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GTXML report: errors in documentation
Should we disable the check for undefined entity? Some errors would go undetected, but people might pay more attention since they will all be real errors. If such errors don't break the compile process, it's ok for me to remove that check until we have completely clear how to detect them without false positives. Best regards Ask 2014-09-20 19:26 GMT+02:00 Daniel Mustieles García daniel.mustie...@gmail.com: And now with the report attatched Sorry... 2014-09-20 19:21 GMT+02:00 Daniel Mustieles García daniel.mustie...@gmail.com: Here is the las report, and these are the affected languages: de el fr ja pt_BR ro sl Note that this report also contains errors in non-core modules, which are not under the release cycle, so no need to fix them ASAP (but highly recommended). Cheers! 2014-09-18 23:24 GMT+02:00 Christian Kirbach christian.kirb...@gmail.com: Am Mittwoch, den 10.09.2014, 12:51 +0200 schrieb Daniel Mustieles García: Hi all, As usual, I've created a report (attatched) with the languages containing typos or errors in tags in documentation files. Here is the list of the affected languages: cs de de should be fixed. Thank you for your efforts. I'd say it would make sense if you run the report again, if possible for you, so people can fix some more issues on the weekend for the 3.14 release next week. -- Christian Kirbach christian.kirb...@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
Re: GTXML report: errors in documentation
Here is the las report, and these are the affected languages: de el fr ja pt_BR ro sl Note that this report also contains errors in non-core modules, which are not under the release cycle, so no need to fix them ASAP (but highly recommended). Cheers! 2014-09-18 23:24 GMT+02:00 Christian Kirbach christian.kirb...@gmail.com: Am Mittwoch, den 10.09.2014, 12:51 +0200 schrieb Daniel Mustieles García: Hi all, As usual, I've created a report (attatched) with the languages containing typos or errors in tags in documentation files. Here is the list of the affected languages: cs de de should be fixed. Thank you for your efforts. I'd say it would make sense if you run the report again, if possible for you, so people can fix some more issues on the weekend for the 3.14 release next week. -- Christian Kirbach christian.kirb...@gmail.com ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GTXML report: errors in documentation
And now with the report attatched Sorry... 2014-09-20 19:21 GMT+02:00 Daniel Mustieles García daniel.mustie...@gmail.com: Here is the las report, and these are the affected languages: de el fr ja pt_BR ro sl Note that this report also contains errors in non-core modules, which are not under the release cycle, so no need to fix them ASAP (but highly recommended). Cheers! 2014-09-18 23:24 GMT+02:00 Christian Kirbach christian.kirb...@gmail.com : Am Mittwoch, den 10.09.2014, 12:51 +0200 schrieb Daniel Mustieles García: Hi all, As usual, I've created a report (attatched) with the languages containing typos or errors in tags in documentation files. Here is the list of the affected languages: cs de de should be fixed. Thank you for your efforts. I'd say it would make sense if you run the report again, if possible for you, so people can fix some more issues on the weekend for the 3.14 release next week. -- Christian Kirbach christian.kirb...@gmail.com gtxml-doc-reports.tar.gz Description: GNU Zip compressed data ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GTXML report: errors in documentation
Hello The mismatched tag and not well-formed are generally real errors. I still don't have a way of telling which constructs are legal in the case of undefined entity which may therefore (and frequently does) give false positives e.g. in Japanese and Brazilian-Portuguese. If we had a way to know which constructs (mdash;, amp; and all that) are legal, then this would be easier. Should we disable the check for undefined entity? Some errors would go undetected, but people might pay more attention since they will all be real errors. Best regards Ask 2014-09-20 19:26 GMT+02:00 Daniel Mustieles García daniel.mustie...@gmail.com: And now with the report attatched Sorry... 2014-09-20 19:21 GMT+02:00 Daniel Mustieles García daniel.mustie...@gmail.com: Here is the las report, and these are the affected languages: de el fr ja pt_BR ro sl Note that this report also contains errors in non-core modules, which are not under the release cycle, so no need to fix them ASAP (but highly recommended). Cheers! 2014-09-18 23:24 GMT+02:00 Christian Kirbach christian.kirb...@gmail.com: Am Mittwoch, den 10.09.2014, 12:51 +0200 schrieb Daniel Mustieles García: Hi all, As usual, I've created a report (attatched) with the languages containing typos or errors in tags in documentation files. Here is the list of the affected languages: cs de de should be fixed. Thank you for your efforts. I'd say it would make sense if you run the report again, if possible for you, so people can fix some more issues on the weekend for the 3.14 release next week. -- Christian Kirbach christian.kirb...@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
Re: GTXML report: errors in documentation
Am Mittwoch, den 10.09.2014, 12:51 +0200 schrieb Daniel Mustieles García: Hi all, As usual, I've created a report (attatched) with the languages containing typos or errors in tags in documentation files. Here is the list of the affected languages: cs de de should be fixed. Thank you for your efforts. I'd say it would make sense if you run the report again, if possible for you, so people can fix some more issues on the weekend for the 3.14 release next week. -- Christian Kirbach christian.kirb...@gmail.com ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
GTXML report: errors in documentation
Hi all, As usual, I've created a report (attatched) with the languages containing typos or errors in tags in documentation files. Here is the list of the affected languages: cs de el es fi fr hu id it ja pt_BR ro sl sv Please fix them before the new release, to avoid errors when compiling the offending modules. If you need help fixing it, just let me know and I'll help you. Thanks for your attention gtxml-doc-reports.tar.gz Description: GNU Zip compressed data ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation
Hello Thanks Daniel, ¡muchas gracias como siempre! And thanks, Piotr. (Although I swear we were going to do this :)) Best regards Ask 2014-03-10 15:41 GMT+01:00 Piotr Drąg piotrd...@gmail.com: 2014-03-07 16:32 GMT+01:00 Daniel Mustieles García daniel.mustie...@gmail.com: As usual, I've made a report with some typos or errors in XML tags in documentation. I've attatched a file with the typos found, sorted by language. Here is the list of the affected languages: Thanks for the report! I've fixed tags that weren't fixed yet by others. I think your clone of balsa is out of date, so in fact Slovenian has no errors. :) Best regards, -- Piotr Drąg http://raven.fedorapeople.org/ ___ 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
Re: Errors in documentation
Many thanks to you Ask for your support with the gtxml script! I'll generate a new report this week to fix any error that might be in docs, before final release. Cheers! 2014-03-17 18:43 GMT+01:00 Ask Hjorth Larsen asklar...@gmail.com: Hello Thanks Daniel, ¡muchas gracias como siempre! And thanks, Piotr. (Although I swear we were going to do this :)) Best regards Ask 2014-03-10 15:41 GMT+01:00 Piotr Drąg piotrd...@gmail.com: 2014-03-07 16:32 GMT+01:00 Daniel Mustieles García daniel.mustie...@gmail.com: As usual, I've made a report with some typos or errors in XML tags in documentation. I've attatched a file with the typos found, sorted by language. Here is the list of the affected languages: Thanks for the report! I've fixed tags that weren't fixed yet by others. I think your clone of balsa is out of date, so in fact Slovenian has no errors. :) Best regards, -- Piotr Drąg http://raven.fedorapeople.org/ ___ 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
Re: Errors in documentation
2014-03-07 16:32 GMT+01:00 Daniel Mustieles García daniel.mustie...@gmail.com: As usual, I've made a report with some typos or errors in XML tags in documentation. I've attatched a file with the typos found, sorted by language. Here is the list of the affected languages: Thanks for the report! I've fixed tags that weren't fixed yet by others. I think your clone of balsa is out of date, so in fact Slovenian has no errors. :) Best regards, -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation
Thanks Piotr for fixing them. I'll generate a new report in a few day, to ensure there are no errors produced by new commits. PO files are taken directly from DL, but note that the report may not be 100% accurate, as it can show false positives ;) Cheers! 2014-03-10 15:41 GMT+01:00 Piotr Drąg piotrd...@gmail.com: 2014-03-07 16:32 GMT+01:00 Daniel Mustieles García daniel.mustie...@gmail.com: As usual, I've made a report with some typos or errors in XML tags in documentation. I've attatched a file with the typos found, sorted by language. Here is the list of the affected languages: Thanks for the report! I've fixed tags that weren't fixed yet by others. I think your clone of balsa is out of date, so in fact Slovenian has no errors. :) Best regards, -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation
On Sun, 2014-03-09 at 10:16 +0800, Wylmer Wang wrote: By the way, the language-switching of www.gnome.org is broken. I have contacted the gnome-www maintainers and the language-switch function writer (and the wppo plugin author), but seems they are busy and there's no progress. Could anyone help check this? Works for me as expected (Firefox 27). Did you file a bug report in bugzilla.gnome.org with exact steps to reproduce and system info (browser etc).? What's its number? andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation
Czech was fixed. Regards Marek Černocký Daniel Mustieles García píše v Pá 07. 03. 2014 v 16:32 +0100: Hi all, As usual, I've made a report with some typos or errors in XML tags in documentation. I've attatched a file with the typos found, sorted by language. Here is the list of the affected languages: cs da de el es fr gl id ja lv pt_BR ru sl zh_CN Please consider to fix them before 3.12, to avoid problems when compiling the affected modules. Thanks for your attention and happy translating :) ___ 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
Re: Errors in documentation
zh_CN fixed. By the way, the language-switching of www.gnome.org is broken. I have contacted the gnome-www maintainers and the language-switch function writer (and the wppo plugin author), but seems they are busy and there's no progress. Could anyone help check this? Please contact me and the related maintainers if you are willing to help. Thank you! ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation
07.03.2014, 19:33, Daniel Mustieles García daniel.mustie...@gmail.com: Hi all, As usual, I've made a report with some typos or errors in XML tags in documentation. I've attatched a file with the typos found, sorted by language. Here is the list of the affected languages: ru (Russian) has been fixed. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Hi everyone Yes, the latest released version has a known character set bug. Unfortunately we are long overdue with a new release, due to some new features that were giving us problems, but hopefully we should get around to doing a new release soon. In the meantime, it is not that difficult to simply run it from a source code checkout. It just requires adding the relevant paths to $PATH and $PYTHONPATH in the .bashrc. Let me know if it gives you any trouble. Regards Kenneth 2013/9/21 Rafael Ferreira rafael.f...@gmail.com Christian, Try the trunk version in Pyg3t's bzr repository. The latest released version has a known issue with some utf8 chars. [1] [1] http://stackoverflow.com/questions/6178929/spanish-text-in-py-files Cheers, Rafael Ferreira 2013/9/21 Christian Kirbach christian.kirb...@gmail.com Hi Daniel thanks for running the report. The de locale should be all set up now. Can you enlighten us on how you check? gtxml does not work for me :( nazgul@rivendell:/git/gnome/gimp-help-2/po/de$ gtxml menus.po Traceback (most recent call last): File /usr/bin/gtxml, line 5, in module ... xml = u''.join([u'xml', string.replace(u'\\', u''), u'/xml']) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7: ordinal not in range(128) Am Montag, den 16.09.2013, 11:05 +0200 schrieb Daniel Mustieles García: Thanks Piotr (and all of you) for fixing the errors. Here is a new report, generated with a previous version of Pyg3t, so most of the invalid token errors are now away. There are still some erros in tags, so it would be interesting to take a look into it. This is the list of the affected languages: de fi fr ja sl zh_CN Like other times, just fixing mismatching tags in translated string should be enough, so you can ignore the rest of the error messages. Again, thanks to all of you for taking care of this. Best regards 2013/9/16 Piotr Drąg piotrd...@gmail.com 2013/9/15 Daniel Mustieles García daniel.mustie...@gmail.com: Here is an up-to-date report. Note that most of the languages in the report are flagged with a not well-formed (invalid token) message, but it doesnt mean that the string is neccesary wrong. Just considering the mismatched or invalid tags should be enough. Thank you! I think all known errors are fixed now. Thanks to everyone for fixing their translations! -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Christian Kirbach christian.kirb...@gmail.com Keine Lust auf NSA und den Lauschangriff? Mein PGP-Schlüssel 1FE120E3 (seit 2005) - http://www.elektronikinfo.de/pc/pgp.htm ___ 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Also you can download latest version from the repo and it works properly for me ;-) 2013/9/22 Kenneth Nielsen k.nielse...@gmail.com Hi everyone Yes, the latest released version has a known character set bug. Unfortunately we are long overdue with a new release, due to some new features that were giving us problems, but hopefully we should get around to doing a new release soon. In the meantime, it is not that difficult to simply run it from a source code checkout. It just requires adding the relevant paths to $PATH and $PYTHONPATH in the .bashrc. Let me know if it gives you any trouble. Regards Kenneth 2013/9/21 Rafael Ferreira rafael.f...@gmail.com Christian, Try the trunk version in Pyg3t's bzr repository. The latest released version has a known issue with some utf8 chars. [1] [1] http://stackoverflow.com/questions/6178929/spanish-text-in-py-files Cheers, Rafael Ferreira 2013/9/21 Christian Kirbach christian.kirb...@gmail.com Hi Daniel thanks for running the report. The de locale should be all set up now. Can you enlighten us on how you check? gtxml does not work for me :( nazgul@rivendell:/git/gnome/gimp-help-2/po/de$ gtxml menus.po Traceback (most recent call last): File /usr/bin/gtxml, line 5, in module ... xml = u''.join([u'xml', string.replace(u'\\', u''), u'/xml']) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7: ordinal not in range(128) Am Montag, den 16.09.2013, 11:05 +0200 schrieb Daniel Mustieles García: Thanks Piotr (and all of you) for fixing the errors. Here is a new report, generated with a previous version of Pyg3t, so most of the invalid token errors are now away. There are still some erros in tags, so it would be interesting to take a look into it. This is the list of the affected languages: de fi fr ja sl zh_CN Like other times, just fixing mismatching tags in translated string should be enough, so you can ignore the rest of the error messages. Again, thanks to all of you for taking care of this. Best regards 2013/9/16 Piotr Drąg piotrd...@gmail.com 2013/9/15 Daniel Mustieles García daniel.mustie...@gmail.com: Here is an up-to-date report. Note that most of the languages in the report are flagged with a not well-formed (invalid token) message, but it doesnt mean that the string is neccesary wrong. Just considering the mismatched or invalid tags should be enough. Thank you! I think all known errors are fixed now. Thanks to everyone for fixing their translations! -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Christian Kirbach christian.kirb...@gmail.com Keine Lust auf NSA und den Lauschangriff? Mein PGP-Schlüssel 1FE120E3 (seit 2005) - http://www.elektronikinfo.de/pc/pgp.htm ___ 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 ___ 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
Re: XML errors in documentation PO file
Hi Daniel thanks for running the report. The de locale should be all set up now. Can you enlighten us on how you check? gtxml does not work for me :( nazgul@rivendell:/git/gnome/gimp-help-2/po/de$ gtxml menus.po Traceback (most recent call last): File /usr/bin/gtxml, line 5, in module ... xml = u''.join([u'xml', string.replace(u'\\', u''), u'/xml']) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7: ordinal not in range(128) Am Montag, den 16.09.2013, 11:05 +0200 schrieb Daniel Mustieles García: Thanks Piotr (and all of you) for fixing the errors. Here is a new report, generated with a previous version of Pyg3t, so most of the invalid token errors are now away. There are still some erros in tags, so it would be interesting to take a look into it. This is the list of the affected languages: de fi fr ja sl zh_CN Like other times, just fixing mismatching tags in translated string should be enough, so you can ignore the rest of the error messages. Again, thanks to all of you for taking care of this. Best regards 2013/9/16 Piotr Drąg piotrd...@gmail.com 2013/9/15 Daniel Mustieles García daniel.mustie...@gmail.com: Here is an up-to-date report. Note that most of the languages in the report are flagged with a not well-formed (invalid token) message, but it doesnt mean that the string is neccesary wrong. Just considering the mismatched or invalid tags should be enough. Thank you! I think all known errors are fixed now. Thanks to everyone for fixing their translations! -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Christian Kirbach christian.kirb...@gmail.com Keine Lust auf NSA und den Lauschangriff? Mein PGP-Schlüssel 1FE120E3 (seit 2005) - http://www.elektronikinfo.de/pc/pgp.htm signature.asc Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Christian, Try the trunk version in Pyg3t's bzr repository. The latest released version has a known issue with some utf8 chars. [1] [1] http://stackoverflow.com/questions/6178929/spanish-text-in-py-files Cheers, Rafael Ferreira 2013/9/21 Christian Kirbach christian.kirb...@gmail.com Hi Daniel thanks for running the report. The de locale should be all set up now. Can you enlighten us on how you check? gtxml does not work for me :( nazgul@rivendell:/git/gnome/gimp-help-2/po/de$ gtxml menus.po Traceback (most recent call last): File /usr/bin/gtxml, line 5, in module ... xml = u''.join([u'xml', string.replace(u'\\', u''), u'/xml']) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7: ordinal not in range(128) Am Montag, den 16.09.2013, 11:05 +0200 schrieb Daniel Mustieles García: Thanks Piotr (and all of you) for fixing the errors. Here is a new report, generated with a previous version of Pyg3t, so most of the invalid token errors are now away. There are still some erros in tags, so it would be interesting to take a look into it. This is the list of the affected languages: de fi fr ja sl zh_CN Like other times, just fixing mismatching tags in translated string should be enough, so you can ignore the rest of the error messages. Again, thanks to all of you for taking care of this. Best regards 2013/9/16 Piotr Drąg piotrd...@gmail.com 2013/9/15 Daniel Mustieles García daniel.mustie...@gmail.com: Here is an up-to-date report. Note that most of the languages in the report are flagged with a not well-formed (invalid token) message, but it doesnt mean that the string is neccesary wrong. Just considering the mismatched or invalid tags should be enough. Thank you! I think all known errors are fixed now. Thanks to everyone for fixing their translations! -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Christian Kirbach christian.kirb...@gmail.com Keine Lust auf NSA und den Lauschangriff? Mein PGP-Schlüssel 1FE120E3 (seit 2005) - http://www.elektronikinfo.de/pc/pgp.htm ___ 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
Re: XML errors in documentation PO file
Hello Daniel! I veryfied the pt_BR file, it shows not well-formed (invalid token) in translator-credits but I believe that it is everything ok. Best Regards. Enrico ___ Em 15/09/2013 06:41, Daniel Mustieles García escreveu: Hi! Here is an up-to-date report. Note that most of the languages in the report are flagged with a not well-formed (invalid token) message, but it doesnt mean that the string is neccesary wrong. Just considering the mismatched or invalid tags should be enough. I'm going to talk with PyG3t maintainers to see if there is a way to avoid the invalid token message, to simplify reports and do not generate noise. Best regards ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
2013/9/15 Daniel Mustieles García daniel.mustie...@gmail.com: Here is an up-to-date report. Note that most of the languages in the report are flagged with a not well-formed (invalid token) message, but it doesnt mean that the string is neccesary wrong. Just considering the mismatched or invalid tags should be enough. Thank you! I think all known errors are fixed now. Thanks to everyone for fixing their translations! -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
2013/9/10 Daniel Mustieles García daniel.mustie...@gmail.com: I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards Hi, It seems that most of the errors have been fixed. Do you mind generating the report again so we can be sure? Thanks for taking care of this, -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Sure I can. Tomorroy I'll generate a new report and will post there the results Thanks to all of you for your fixes. 2013/9/13 Piotr Drąg piotrd...@gmail.com 2013/9/10 Daniel Mustieles García daniel.mustie...@gmail.com: I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards Hi, It seems that most of the errors have been fixed. Do you mind generating the report again so we can be sure? Thanks for taking care of this, -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
11.09.13 03:28, Piotr Drąg написав(ла): 2013/9/10 Daniel Mustieles García daniel.mustie...@gmail.com: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: el eu ko sr sr@latin sv th uk I've fixed errors in above languages. Thanks! ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Thanks to you Fran. It seems there is a remaining mismatching tag in GDM (missin /filename in the translated string) gl/gdm-help.master.gl.po, line 1308: mismatched tag --- #. (itstool) path: sect2/para #: C/index.docbook:815 msgid to filenamelt;etcgt;/hosts.deny/filename. You may also need to add msgstr a filenamelt;etcgt;/hosts.deny. Tamén precisa engadir Cheers! 2013/9/10 Fran Dieguez fran.dieg...@mabishu.com On mar 10 sep 2013 20:51:53 CEST, Marek Černocký wrote: Czech language fixed. Marek Černocký Daniel Mustieles García píše v Út 10. 09. 2013 v 16:45 +0200: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: cs de el eu fr gl id it ja ko pt_BR ru sl sr sr@latin sv th uk zh_CN These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards __**_ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/**mailman/listinfo/gnome-i18nhttps://mail.gnome.org/mailman/listinfo/gnome-i18n __**_ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/**mailman/listinfo/gnome-i18nhttps://mail.gnome.org/mailman/listinfo/gnome-i18n Hi Dani, Thanks a lot for taking your time and report those errors. All fixed from the Galician group side. Regards. __**_ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/**mailman/listinfo/gnome-i18nhttps://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Everything seems to be ok in your language Enrico. Thanks for your quick fix :) 2013/9/11 Enrico Nicoletto live...@gmail.com Thank you, Daniel, for informing us about that errors. For the Brazilian Portuguese team, it is now fixed and commited. Please let us know if you still found something that needs our attention. Kindly Regards, Enrico Nicoletto. __ Em 10/09/2013 11:45, Daniel Mustieles García escreveu: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: cs de el eu fr gl id it ja ko pt_BR ru sl sr sr@latin sv th uk zh_CN These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards ___ gnome-i18n mailing listgnome-i18n@gnome.orghttps://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
On 11/09/13 11:13, Daniel Mustieles García wrote: Thanks to you Fran. It seems there is a remaining mismatching tag in GDM (missin /filename in the translated string) gl/gdm-help.master.gl.po, line 1308: mismatched tag --- #. (itstool) path: sect2/para #: C/index.docbook:815 msgid to filenamelt;etcgt;/hosts.deny/filename. You may also need to add msgstr a filenamelt;etcgt;/hosts.deny. Tamén precisa engadir Cheers! Ok, done ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
It is really a good thing to read! Thank you, Daniel. Enrico. Em 11/09/2013 06:14, Daniel Mustieles García escreveu: Everything seems to be ok in your language Enrico. Thanks for your quick fix :) 2013/9/11 Enrico Nicoletto live...@gmail.com mailto:live...@gmail.com Thank you, Daniel, for informing us about that errors. For the Brazilian Portuguese team, it is now fixed and commited. Please let us know if you still found something that needs our attention. Kindly Regards, Enrico Nicoletto. __ Em 10/09/2013 11:45, Daniel Mustieles García escreveu: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: cs de el eu fr gl id it ja ko pt_BR ru sl sr sr@latin sv th uk zh_CN These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards ___ gnome-i18n mailing list gnome-i18n@gnome.org mailto: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
Re: XML errors in documentation PO file
Hi Daniel, Thank you for the report. As for Japanese, all gtxml detected are undefined entity. They are no problem, as RyōTa SimaMoto, a Japanese translator and a maintainer of the document, said before. [1] Thanks, [1] https://mail.gnome.org/archives/gnome-i18n/2013-March/msg00219.html -- Jiro Matsuzawa E-mail: jmatsuz...@gnome.org matsuzawa...@gmail.com GPG Key ID: 0xECC442E9 GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Thanks for the info Jiro. I've generated the reports with gtxml, but if you see a false positive in the report (or a non broker typo) you can just ignore it. Cheers! 2013/9/10 Jiro Matsuzawa jmatsuz...@gnome.org Hi Daniel, Thank you for the report. As for Japanese, all gtxml detected are undefined entity. They are no problem, as RyōTa SimaMoto, a Japanese translator and a maintainer of the document, said before. [1] Thanks, [1] https://mail.gnome.org/archives/gnome-i18n/2013-March/msg00219.html -- Jiro Matsuzawa E-mail: jmatsuz...@gnome.org matsuzawa...@gmail.com GPG Key ID: 0xECC442E9 GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9 ___ 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
Re: XML errors in documentation PO file
10.09.2013, 18:45, Daniel Mustieles García daniel.mustie...@gmail.com: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: ru Russian translations fixed. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Czech language fixed. Marek Černocký Daniel Mustieles García píše v Út 10. 09. 2013 v 16:45 +0200: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: cs de el eu fr gl id it ja ko pt_BR ru sl sr sr@latin sv th uk zh_CN These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards ___ 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
Re: XML errors in documentation PO file
On Tue, Sep 10, 2013 at 9:45 PM, Daniel Mustieles García daniel.mustie...@gmail.com wrote: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: id Thank you. Indonesian translation cleaned up. These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
On mar 10 sep 2013 20:51:53 CEST, Marek Černocký wrote: Czech language fixed. Marek Černocký Daniel Mustieles García píše v Út 10. 09. 2013 v 16:45 +0200: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: cs de el eu fr gl id it ja ko pt_BR ru sl sr sr@latin sv th uk zh_CN These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards ___ 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 Hi Dani, Thanks a lot for taking your time and report those errors. All fixed from the Galician group side. Regards. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: XML errors in documentation PO file
Thank you, Daniel, for informing us about that errors. For the Brazilian Portuguese team, it is now fixed and commited. Please let us know if you still found something that needs our attention. Kindly Regards, Enrico Nicoletto. __ Em 10/09/2013 11:45, Daniel Mustieles García escreveu: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: cs de el eu fr gl id it ja ko pt_BR ru sl sr sr@latin sv th uk zh_CN These reports are generated by an automated script using gtxml. If you want a copy of the script, feel free to ask me about it. Thanks in advance and best regards ___ 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
Re: XML errors in documentation PO file
2013/9/10 Daniel Mustieles García daniel.mustie...@gmail.com: Hi all, I've generated a report with some bugs and typos in documentation PO files. As you know, these kind of errors may break the modules's compilation process, so it would be great if each afected language coordinator could fix them. This is the list of the affected languages: el eu ko sr sr@latin sv th uk I've fixed errors in above languages. -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: More on xml errors in documentation
So, we could use the strict check as the default one, just keeping in mind it can shows some (rare) false positives, right? The other question about this is, is it possible to do this check in DL to show this typos (like the errors generating POT file are shown, for example)? It would be realy useful to have this check, so translators and coordinators would be aware of them. Cheers 2013/4/8 Shaun McCance sha...@gnome.org On Mon, 2013-04-08 at 11:30 +0200, Daniel Mustieles García wrote: 2013/4/6 Gabor Kelemen kelem...@gnome.hu I think these kinds of warnings are useful, until it is not compulsory to fix all of them :). Why not? I'm not sure about it. If Documentation team adds some tags to the original strings, translators should keep those strings. Also, having freedom to add our own tags to translated string may break the building process so fixing those errors should be fixed. I don't know how Mallard documents work, and how translators have to deal with tags (I mean: should we add or remove tags when translating strings? Shouldn't it be done by the Documentation team?) I think translators shouldn't change the format adding or removing tags (althouhg it doesn't break the compilation), but having some comments from docs team would be really useful. I think there are cases where it's worthwhile for translators to add tags, but they're probably the exception. Thinking out loud: * East Asian languages might want to add Ruby markup. And this will actually work correctly in 3.10. * Some languages might want to use an English word for a technical term when there isn't yet an established local word. They might want to mark this with em. * The instructions for certain actions on different keyboard layouts might involve more or fewer key elements than for en-US. If we really end up getting a lot of false positives, or if we want to turn these checks into hard pre-commit checks, we could add some sort of markup to allow translators to say I know what I'm doing in this case. But that can be a hassle, so it's only worthwhile if we have a real problem with false positives. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: More on xml errors in documentation
2013/4/6 Gabor Kelemen kelem...@gnome.hu I think these kinds of warnings are useful, until it is not compulsory to fix all of them :). Why not? I'm not sure about it. If Documentation team adds some tags to the original strings, translators should keep those strings. Also, having freedom to add our own tags to translated string may break the building process so fixing those errors should be fixed. I don't know how Mallard documents work, and how translators have to deal with tags (I mean: should we add or remove tags when translating strings? Shouldn't it be done by the Documentation team?) I think translators shouldn't change the format adding or removing tags (althouhg it doesn't break the compilation), but having some comments from docs team would be really useful. Cheers! Regards and thanks for the feature Gabor Kelemen ___ 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
Re: More on xml errors in documentation
On Mon, 2013-04-08 at 11:30 +0200, Daniel Mustieles García wrote: 2013/4/6 Gabor Kelemen kelem...@gnome.hu I think these kinds of warnings are useful, until it is not compulsory to fix all of them :). Why not? I'm not sure about it. If Documentation team adds some tags to the original strings, translators should keep those strings. Also, having freedom to add our own tags to translated string may break the building process so fixing those errors should be fixed. I don't know how Mallard documents work, and how translators have to deal with tags (I mean: should we add or remove tags when translating strings? Shouldn't it be done by the Documentation team?) I think translators shouldn't change the format adding or removing tags (althouhg it doesn't break the compilation), but having some comments from docs team would be really useful. I think there are cases where it's worthwhile for translators to add tags, but they're probably the exception. Thinking out loud: * East Asian languages might want to add Ruby markup. And this will actually work correctly in 3.10. * Some languages might want to use an English word for a technical term when there isn't yet an established local word. They might want to mark this with em. * The instructions for certain actions on different keyboard layouts might involve more or fewer key elements than for en-US. If we really end up getting a lot of false positives, or if we want to turn these checks into hard pre-commit checks, we could add some sort of markup to allow translators to say I know what I'm doing in this case. But that can be a hassle, so it's only worthwhile if we have a real problem with false positives. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: More on xml errors in documentation
2013-04-04 16:31 keltezéssel, Ask Hjorth Larsen írta: I would like to know how useful this kind of report is. It complains, aside from the usual syntax errors, about tags it cannot find in the corresponding msgid. This will lead to false positives in cases where the translator chooses to add, say, app.../app to a programme name when the msgid didn't. I will appreciate any feedback (this is ridiculous, everything was totally okay or otherwise). For me, it is useful - these indeed show some real bugs, like using gui tag instead of app. However, there are some really harmless false positives reported like adding extra tags where there was none in the original - we should have this much freedom. I think these kinds of warnings are useful, until it is not compulsory to fix all of them :). Regards and thanks for the feature Gabor Kelemen signature.asc Description: OpenPGP digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: More on xml errors in documentation
This question has is being discused here: https://bugs.launchpad.net/pyg3t/+bug/1052399 The main question we have is if all the tags are mandatory or not. If it's mandatory to have the same tags in the msgstr and the msgid, we should do a strict check to avoid missing tags in translations; if they aren't mandatory, there is no need to do this kind of check, but then there are other problems: unreviewd tags may become deprecated, so documentaion might not been shown properly, these tags might neve be included in translated strings, just bothering translators... Both Ask and me have no much idea about Mallard, so any comment or explanation about how it works will be welcome. Thanks in advance! 2013/4/4 Ask Hjorth Larsen asklar...@gmail.com Hello Below are some error reports for GNOME docs which are considerably more strict than usual. I would like to know how useful this kind of report is. It complains, aside from the usual syntax errors, about tags it cannot find in the corresponding msgid. This will lead to false positives in cases where the translator chooses to add, say, app.../app to a programme name when the msgid didn't. I will appreciate any feedback (this is ridiculous, everything was totally okay or otherwise). Here are the reports. Only some languages with many doc translations have been included. http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt Best regards Ask ___ 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
Re: More on xml errors in documentation
HI, thanks, personally I find those very useful, as mistakes may happen very easily in translations. Thanks for your work. I just started fixing the de locale. Actually I thought about implementing XML syntax check in gtranslator, a PO file editor. Am Donnerstag, den 04.04.2013, 16:31 +0200 schrieb Ask Hjorth Larsen: Hello Below are some error reports for GNOME docs which are considerably more strict than usual. I would like to know how useful this kind of report is. It complains, aside from the usual syntax errors, about tags it cannot find in the corresponding msgid. This will lead to false positives in cases where the translator chooses to add, say, app.../app to a programme name when the msgid didn't. I will appreciate any feedback (this is ridiculous, everything was totally okay or otherwise). Here are the reports. Only some languages with many doc translations have been included. http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt Best regards Ask ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Christian Kirbach christian.kirb...@gmail.com signature.asc Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: More on xml errors in documentation
Hi Christian, If you are planning to implement gtxml in Gtranslator, you might find useful this bug: https://bugzilla.gnome.org/show_bug.cgi?id=672080 Ignacio was working on it, and there is a patch attatched, but it isn't finished. Havind this kind of checks in GTR would be wonderful! Thanks for taking care of this 2013/4/5 Christian Kirbach christian.kirb...@gmail.com HI, thanks, personally I find those very useful, as mistakes may happen very easily in translations. Thanks for your work. I just started fixing the de locale. Actually I thought about implementing XML syntax check in gtranslator, a PO file editor. Am Donnerstag, den 04.04.2013, 16:31 +0200 schrieb Ask Hjorth Larsen: Hello Below are some error reports for GNOME docs which are considerably more strict than usual. I would like to know how useful this kind of report is. It complains, aside from the usual syntax errors, about tags it cannot find in the corresponding msgid. This will lead to false positives in cases where the translator chooses to add, say, app.../app to a programme name when the msgid didn't. I will appreciate any feedback (this is ridiculous, everything was totally okay or otherwise). Here are the reports. Only some languages with many doc translations have been included. http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt Best regards Ask ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Christian Kirbach christian.kirb...@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
More on xml errors in documentation
Hello Below are some error reports for GNOME docs which are considerably more strict than usual. I would like to know how useful this kind of report is. It complains, aside from the usual syntax errors, about tags it cannot find in the corresponding msgid. This will lead to false positives in cases where the translator chooses to add, say, app.../app to a programme name when the msgid didn't. I will appreciate any feedback (this is ridiculous, everything was totally okay or otherwise). Here are the reports. Only some languages with many doc translations have been included. http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt Best regards Ask ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
2012/9/15 Alexandre Franke alexandre.fra...@gmail.com: Can you try amp; as a replacement of the ampersand and see if it fixes the error? If it doesn't work, try with %26. Please note that a file has been uploaded to Vertimus for this translation (so fixing it in master may not be the right choice as the fix may be lost when commiting the new file). I don't have access to the script, so I can't check if it would help. -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
Hi 2012/9/16 Piotr Drąg piotrd...@gmail.com: 2012/9/15 Alexandre Franke alexandre.fra...@gmail.com: Can you try amp; as a replacement of the ampersand and see if it fixes the error? If it doesn't work, try with %26. Please note that a file has been uploaded to Vertimus for this translation (so fixing it in master may not be the right choice as the fix may be lost when commiting the new file). I don't have access to the script, so I can't check if it would help. If you just need to run it on one file, use 'gtxml filename.po'. gtxml is part of pyg3t and can be found here: https://launchpad.net/pyg3t Note that gtxml only verifies that the xml isn't broken. (One can still write valid xml using tags which are not recognized in the GNOME docs, and thus wrong) Best regards Ask ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
On Fri, Sep 14, 2012 at 6:52 PM, Piotr Drąg piotrd...@gmail.com wrote: 2012/9/14 Daniel Mustieles García daniel.mustie...@gmail.com: I managed to fix all of the remaining errors with an exception of French and Tamil. In the first case I'm not sure what to do - should ampersands in URLs be escaped in some way? Can you try amp; as a replacement of the ampersand and see if it fixes the error? If it doesn't work, try with %26. Please note that a file has been uploaded to Vertimus for this translation (so fixing it in master may not be the right choice as the fix may be lost when commiting the new file). -- Alexandre Franke French team coordinator ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
Many thanks Piotr for fixing them. Here are the updated report. Still there are some errors in tags, but much less than before. Cheers! 2012/9/13 Piotr Drąg piotrd...@gmail.com 2012/9/13 Daniel Mustieles García daniel.mustie...@gmail.com: I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module Hi, I've fixed most errors listed by your script, of course except those languages that were fixed by their maintainers. Would you mind re-running it and posting new results? -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n gtxml-doc-reports.tar.gz Description: GNU Zip compressed data ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
2012/9/14 Daniel Mustieles García daniel.mustie...@gmail.com: Many thanks Piotr for fixing them. Here are the updated report. Still there are some errors in tags, but much less than before. I managed to fix all of the remaining errors with an exception of French and Tamil. In the first case I'm not sure what to do - should ampersands in URLs be escaped in some way? And I couldn't find in which files the Tamil errors occur. There is no information in ta-report.txt about it. Any ideas? -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
On 14 September 2012 19:52, Piotr Drąg piotrd...@gmail.com wrote: 2012/9/14 Daniel Mustieles García daniel.mustie...@gmail.com: Many thanks Piotr for fixing them. Here are the updated report. Still there are some errors in tags, but much less than before. I managed to fix all of the remaining errors with an exception of French and Tamil. In the first case I'm not sure what to do - should ampersands in URLs be escaped in some way? And I couldn't find in which files the Tamil errors occur. There is no information in ta-report.txt about it. Any ideas? -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n Hi Piotr, It's the translation of gtk-doc. http://l10n.gnome.org/vertimus/gtk-doc/master/help/ta Tom Tryfonidis ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
2012/9/14 Tom Tryfonidis tomt...@gmail.com: It's the translation of gtk-doc. http://l10n.gnome.org/vertimus/gtk-doc/master/help/ta Thanks a lot, fixed! -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Errors in documentation tags
Hi all, I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Best regards gtxml-doc-reports.tar.gz Description: GNU Zip compressed data ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
Thanks Daniel, I will fix all the Galician errors in doc ASAP. Fran Dieguez On Xov 13 Set 2012 12:03:47 CEST, Daniel Mustieles García wrote: Hi all, I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Best regards ___ 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
Re: Errors in documentation tags
Hi 2012/9/13 Daniel Mustieles García daniel.mustie...@gmail.com: Hi all, I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Best regards ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n Thanks for doing this, Daniel. A tip to everyone: Open the txt files with less -R. Then it will colour the locations of the xml errors. Regards Ask ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
Here is the bug: /guiseqguiUpravit/guiguiPřidat soubory/ gui/guiseq. Note that the first tag (opening guiseq) has a slash. You can find the PO file here: http://l10n.gnome.org/POT/brasero.master/docs/brasero-help.master.cs.po Cheers 2012/9/13 Marek Černocký ma...@manet.cz Where I can find this PO files? I checked the Czech translation and I don't see this errors in Brasero's git master branch. Marek Černocký Daniel Mustieles García píše v Čt 13. 09. 2012 v 12:03 +0200: Hi all, I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Best regards ___ 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
Re: Errors in documentation tags
Where I can find this PO files? I checked the Czech translation and I don't see this errors in Brasero's git master branch. Marek Černocký Daniel Mustieles García píše v Čt 13. 09. 2012 v 12:03 +0200: Hi all, I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Best regards ___ 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
Re: Errors in documentation tags
On 13 September 2012 13:03, Daniel Mustieles García daniel.mustie...@gmail.com wrote: Hi all, I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Best regards ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n Thank you Daniel, I fixed the Greek errors. Tom Tryfonidis ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
Yeah, fixed. Reported file for Czech displays some garbage characters and I think this is that problem. Daniel Mustieles García píše v Čt 13. 09. 2012 v 13:09 +0200: Here is the bug: /guiseqguiUpravit/guiguiPřidat soubory/ gui/guiseq. Note that the first tag (opening «guiseq») has a slash. You can find the PO file here: http://l10n.gnome.org/POT/brasero.master/docs/brasero-help.master.cs.po Cheers 2012/9/13 Marek Černocký ma...@manet.cz Where I can find this PO files? I checked the Czech translation and I don't see this errors in Brasero's git master branch. Marek Černocký Daniel Mustieles García píše v Čt 13. 09. 2012 v 12:03 +0200: Hi all, I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Best regards ___ 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
Re: Errors in documentation tags
To view te report properly, just do cat file in the terminal. gtxml can colorize the errors, but opening the files with vim or gedit shows the color special characters, not the color itself ;-) 2012/9/13 Marek Černocký ma...@manet.cz Yeah, fixed. Reported file for Czech displays some garbage characters and I think this is that problem. Daniel Mustieles García píše v Čt 13. 09. 2012 v 13:09 +0200: Here is the bug: /guiseqguiUpravit/guiguiPřidat soubory/ gui/guiseq. Note that the first tag (opening «guiseq») has a slash. You can find the PO file here: http://l10n.gnome.org/POT/brasero.master/docs/brasero-help.master.cs.po Cheers 2012/9/13 Marek Černocký ma...@manet.cz Where I can find this PO files? I checked the Czech translation and I don't see this errors in Brasero's git master branch. Marek Černocký Daniel Mustieles García píše v Čt 13. 09. 2012 v 12:03 +0200: Hi all, I've generated several reports, one for each language, about errors in tags in the documentation PO files. In the attatched file, you will find several language-report.txt files, with the corresponding errors to your language. You can cat the file and the errors will be highlighted in red. If you don't see your language listed in the file, it means it has no errors :) Please fix and update your translations, since this kind of errors in PO files can generate several errors when compiling the module This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Best regards ___ 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
Re: Errors in documentation tags
2012-09-13 12:03 keltezéssel, Daniel Mustieles García írta: This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Of course we are interested, we always are :). Please put it up to some public version control system. Thanks for your work, and thanks in advance for publishing it. Gabor Kelemen ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
2012/9/13 Gabor Kelemen kelem...@gnome.hu: 2012-09-13 12:03 keltezéssel, Daniel Mustieles García írta: This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Hey Daniel! I know that you have some pretty utilities like this shell script and you're happy to share them. But, what do you think about put all these utilities into a github/bitbucket/gnome/whatever git repository? People will be able to improve and/or add more utilities in a more easy way than sharing them by mail. Cheers, Javi ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
Yes, I've considered it several times, but the main script I've developed (GTTK) has several bugs, and i'd like to fix them before sharing it with a big README file ;-) I hope I'll have some time these days to work on it and, when I fix it, sure I'll share it on github. BTW, as soon as I have time to create a repo and upload the scripts, I'll share them in this mail list. Many thanks for your interest! 2012/9/13 Javier Hernández Antúnez jhernan...@emergya.com 2012/9/13 Gabor Kelemen kelem...@gnome.hu: 2012-09-13 12:03 keltezéssel, Daniel Mustieles García írta: This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Hey Daniel! I know that you have some pretty utilities like this shell script and you're happy to share them. But, what do you think about put all these utilities into a github/bitbucket/gnome/whatever git repository? People will be able to improve and/or add more utilities in a more easy way than sharing them by mail. Cheers, Javi ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
On Thu, Sep 13, 2012 at 8:09 AM, Daniel Mustieles García daniel.mustie...@gmail.com wrote: Yes, I've considered it several times, but the main script I've developed (GTTK) has several bugs, and i'd like to fix them before sharing it with a big README file ;-) I hope I'll have some time these days to work on it and, when I fix it, sure I'll share it on github. BTW, as soon as I have time to create a repo and upload the scripts, I'll share them in this mail list. Many thanks for your interest! Dear Daniel, Thank you for this effort. Creation of workflows like this for global (or even individual) quality control is a wonderful contribution. I would not be too concerned about sharing them prior to final polishing as I think you have a very welcoming audience of beta testers on this list. I would encourage you to look at the Translate Toolkit for inspiration (or bits of code to borrow) as there are lots of widgets that perform similar work in a PO-file aware manner. The widgets there are readily wrapped in a little bash script for bulk operations. http://translate.sourceforge.net/wiki/toolkit/index For instance, I think a similar check is performed by the pofilter tool under the xmltags flag. translate.sourceforge.net/wiki/toolkit/pofilter_tests Just as a potential target for another such global analysis workflow, in my experience with Sugar Labs, I find that printf errors and mismatched terminal newlines are the most common causes of PO files causing build failures. One of the interesting things about xmltags, printf errors and terminal newlines mismatches is that very often, one does not need to be able to read the language in question to be able to provide a suitable correction. Simple understanding of the syntax of the original string is often sufficient to identify the error and correct it. I would also like to point out that one of the current Gnome Goals https://live.gnome.org/GnomeGoals/RemoveMarkupInMessages is, in fact, to find and remove markup from UI messages. I imagine your tool could be adapted to search for the presence of such tags in UI strings. I have filed a few i18n enhancement tickets on packages pointing out the Gnome Goal above where there was a lot of markup and referencing specific lines (from the PO location comment). At some point I may take a look at going back over them and trying to provide patches where the original developers have not taken action on their own. Warmest Regards, cjl ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Errors in documentation tags
El dj 13 de 09 de 2012 a les 14:09 +0200, en/na Daniel Mustieles García va escriure: Yes, I've considered it several times, but the main script I've developed (GTTK) has several bugs, and i'd like to fix them before sharing it with a big README file ;-) I hope I'll have some time these days to work on it and, when I fix it, sure I'll share it on github. BTW, as soon as I have time to create a repo and upload the scripts, I'll share them in this mail list. Many thanks for your interest! Release early, release often ;) Thanks for this tremendous job! As other said, do not hesitate to wait until its perfect and bug-free, because, you know, it will never be, and we will never be able to fix strings before sending them :) Thanks for all your work on QA!! 2012/9/13 Javier Hernández Antúnez jhernan...@emergya.com 2012/9/13 Gabor Kelemen kelem...@gnome.hu: 2012-09-13 12:03 keltezéssel, Daniel Mustieles García írta: This report has been generated using gtxml and a very simple bash script. If you are interested on it, of course I can send you the bash script I've generated. Also, if you want to improve it, you will be free to do it. Hey Daniel! I know that you have some pretty utilities like this shell script and you're happy to share them. But, what do you think about put all these utilities into a github/bitbucket/gnome/whatever git repository? People will be able to improve and/or add more utilities in a more easy way than sharing them by mail. Cheers, Javi ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Gil Forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net planet: http://planet.guifi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
Am Mittwoch, den 20.10.2010, 00:36 +0200 schrieb Ask Hjorth Larsen: This is a breakdown of every xml error in every translated documentation string in GNOME for those languages that have reasonable ( around 10%) coverage of the documentation. More precisely, every message where the English string is valid xml, but the translation is not. You may want to fix them as this probably means the messages are not displayed correctly in the help documents. … ./de/summary.txt:Total errors 14 These errors are fixed now for all the mentioned modules in German. Thanks for the hint. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
Op Wo, 2010-10-20 om 22:09 +0200 skryf Ask Hjorth Larsen: Hi Andre and Claude On Wed, Oct 20, 2010 at 9:50 AM, Claude Paroz cla...@2xlibre.net wrote: Le mercredi 20 octobre 2010 à 02:23 +0200, Andre Klapper a écrit : Am Mittwoch, den 20.10.2010, 00:36 +0200 schrieb Ask Hjorth Larsen: This is a breakdown of every xml error in every translated documentation string in GNOME Thanks a lot. Fixed for cs. Fixed for fr also. The xml checks were performed with the utility gtxml from pyg3t (in case you want to run your own xml checks subsequently): https://launchpad.net/pyg3t Naive idea: Could something similar could run on l10n.gnome.org and display an error on the website (or already when uploading it)? Talking of QA tool integration, I'd prefer beginning with translate-toolkit [1]. Can you tell us how this project is different from it and why they couldn't be merged? Claude It definitely has a lot in common with the translate toolkit. But also some differences. The present xml tool was written specifically because we wanted to weed out xml errors in the gnome docs without too many false positives. The xml check of the translate toolkit will write more complaints, but is also more likely to get false positives. If we want to run something like this on damned lies, I think it should only complain about real errors. Some of the pyg3t scripts are bit specialized to the kind of stuff we (Danish translation team) do, and tend to be less general than the translate-toolkit. It's the question of how one would want to combine utilities that do close to the same thing. Does anyone here work on translate toolkit? Yes. I am one of the developers for the project. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/draft-anloc-foss-localisation-manual ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
Jorge González González schreef op wo 20-10-2010 om 08:39 [+0200]: Thanks a lot, es fixed. However most of the errors came from epiphany, where I replaced ... with hellip; apparently xml doesn't like it. You can just use the character (…) U+2026 directly in a UTF-8 encoded file. Perhaps your encoding was not set correctly? (Fwiw, Latin1 doesn't include …) — Wouter signature.asc Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
El mié, 20-10-2010 a las 02:23 +0200, Andre Klapper escribió: The xml checks were performed with the utility gtxml from pyg3t (in case you want to run your own xml checks subsequently): https://launchpad.net/pyg3t Naive idea: Could something similar could run on l10n.gnome.org and display an error on the website (or already when uploading it)? Yeap, that would be awesome. andre -- Jorge González González alor...@gmail.com Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
El mié, 20-10-2010 a las 00:36 +0200, Ask Hjorth Larsen escribió: Hi language team coordinators (Sorry for writing to the i18n list, but I think this is the easiest way to reach every language - the alternative being making lots of bug reports) This is a breakdown of every xml error in every translated documentation string in GNOME for those languages that have reasonable ( around 10%) coverage of the documentation. More precisely, every message where the English string is valid xml, but the translation is not. You may want to fix them as this probably means the messages are not displayed correctly in the help documents. Thanks a lot, es fixed. However most of the errors came from epiphany, where I replaced ... with hellip; apparently xml doesn't like it. Cheers. -- Jorge González González alor...@gmail.com Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
Le mercredi 20 octobre 2010 à 02:23 +0200, Andre Klapper a écrit : Am Mittwoch, den 20.10.2010, 00:36 +0200 schrieb Ask Hjorth Larsen: This is a breakdown of every xml error in every translated documentation string in GNOME Thanks a lot. Fixed for cs. Fixed for fr also. The xml checks were performed with the utility gtxml from pyg3t (in case you want to run your own xml checks subsequently): https://launchpad.net/pyg3t Naive idea: Could something similar could run on l10n.gnome.org and display an error on the website (or already when uploading it)? Talking of QA tool integration, I'd prefer beginning with translate-toolkit [1]. Can you tell us how this project is different from it and why they couldn't be merged? Claude [1] http://translate.sourceforge.net/wiki/toolkit/index ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
Thanks a million for these valuable tools, now all of them are part of my QA toolkit. Here's the list of numbers of errors for each language (if it's zero, ignore this :)): ./gl/summary.txt:Total errors 22 Fixed for gl. Cheers, Fran ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
Op Wo, 2010-10-20 om 09:50 +0200 skryf Claude Paroz: Le mercredi 20 octobre 2010 à 02:23 +0200, Andre Klapper a écrit : Am Mittwoch, den 20.10.2010, 00:36 +0200 schrieb Ask Hjorth Larsen: This is a breakdown of every xml error in every translated documentation string in GNOME Thanks a lot. Fixed for cs. Fixed for fr also. The xml checks were performed with the utility gtxml from pyg3t (in case you want to run your own xml checks subsequently): https://launchpad.net/pyg3t Naive idea: Could something similar could run on l10n.gnome.org and display an error on the website (or already when uploading it)? Talking of QA tool integration, I'd prefer beginning with translate-toolkit [1]. Can you tell us how this project is different from it and why they couldn't be merged? Claude [1] http://translate.sourceforge.net/wiki/toolkit/index From a _very_ quick look, it seems that an XML parser is used to check for valid XML, whereas pofilter from the Translate Toolkit checks for the use of the same XML, and that attributes are unchanged (except for things like alt and title in HTML). I've wanted to do something similar to actually check for valid XML structure in pofilter's xmltags test, and I think that would be a good change to do. However, I think pofilter still has an interesting approach here in that it restricts the translator's XML vocabulary, and that it has 40 other tests, of course. In the case where the source string wasn't valid XML to begin with (snippets, or invalid entities), I guess pofilter will give the only possibility for automated QA. Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/draft-anloc-foss-localisation-manual ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
Hi Andre and Claude On Wed, Oct 20, 2010 at 9:50 AM, Claude Paroz cla...@2xlibre.net wrote: Le mercredi 20 octobre 2010 à 02:23 +0200, Andre Klapper a écrit : Am Mittwoch, den 20.10.2010, 00:36 +0200 schrieb Ask Hjorth Larsen: This is a breakdown of every xml error in every translated documentation string in GNOME Thanks a lot. Fixed for cs. Fixed for fr also. The xml checks were performed with the utility gtxml from pyg3t (in case you want to run your own xml checks subsequently): https://launchpad.net/pyg3t Naive idea: Could something similar could run on l10n.gnome.org and display an error on the website (or already when uploading it)? Talking of QA tool integration, I'd prefer beginning with translate-toolkit [1]. Can you tell us how this project is different from it and why they couldn't be merged? Claude It definitely has a lot in common with the translate toolkit. But also some differences. The present xml tool was written specifically because we wanted to weed out xml errors in the gnome docs without too many false positives. The xml check of the translate toolkit will write more complaints, but is also more likely to get false positives. If we want to run something like this on damned lies, I think it should only complain about real errors. Some of the pyg3t scripts are bit specialized to the kind of stuff we (Danish translation team) do, and tend to be less general than the translate-toolkit. It's the question of how one would want to combine utilities that do close to the same thing. Does anyone here work on translate toolkit? In any case, I'm willing to help integrating a periodic check on damned lies (shouldn't be difficult). Regards Ask Hjorth Larsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
xml errors in documentation
Hi language team coordinators (Sorry for writing to the i18n list, but I think this is the easiest way to reach every language - the alternative being making lots of bug reports) This is a breakdown of every xml error in every translated documentation string in GNOME for those languages that have reasonable ( around 10%) coverage of the documentation. More precisely, every message where the English string is valid xml, but the translation is not. You may want to fix them as this probably means the messages are not displayed correctly in the help documents. Here's the list of numbers of errors for each language (if it's zero, ignore this :)): ./eu/summary.txt:Total errors 0 ./ja/summary.txt:Total errors 2 ./el/summary.txt:Total errors 3 ./gl/summary.txt:Total errors 22 ./ko/summary.txt:Total errors 9 ./it/summary.txt:Total errors 6 ./de/summary.txt:Total errors 14 ./zh_CN/summary.txt:Total errors 27 ./sv/summary.txt:Total errors 1 ./es/summary.txt:Total errors 19 ./fr/summary.txt:Total errors 22 ./en_GB/summary.txt:Total errors 0 ./fi/summary.txt:Total errors 25 ./pt_BR/summary.txt:Total errors 8 ./ru/summary.txt:Total errors 10 ./uk/summary.txt:Total errors 8 ./cs/summary.txt:Total errors 3 ./bg/summary.txt:Total errors 3 ./hu/summary.txt:Total errors 4 ./ca/summary.txt:Total errors 5 ./pt/summary.txt:Total errors 0 ./da/summary.txt:Total errors 9 The total number of errors is 182. The specific location of each error can be found by consulting the text files located here (note that some browsers may assume the wrong encoding; in that case you may wish to download the file): http://www.student.dtu.dk/~ashj/documentation-errors/ The xml checks were performed with the utility gtxml from pyg3t (in case you want to run your own xml checks subsequently): https://launchpad.net/pyg3t Best regards Ask Hjorth Larsen Danish translation team ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
