keywords in desktop files, again
I sent a mail about this in January already[1], but we are still seeing a steady stream of broken syntax in translations for the Keywords field in desktop files. Please, try to educate your fellow translators about this issue, it is really making building GNOME package updates cumbersome, since the desktop-file-validate call in the spec file is normally the first place where this breakage becomes apparent. Matthias [1] https://mail.gnome.org/archives/gnome-i18n/2013-January/msg00030.html ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: keywords in desktop files, again
Is there a easy way to track down this bug in every module, except for going in and out of each one? I'd love to make sure it doesn't happen to my language. Rafael Ferreira 2013/3/22 Matthias Clasen matthias.cla...@gmail.com: I sent a mail about this in January already[1], but we are still seeing a steady stream of broken syntax in translations for the Keywords field in desktop files. Please, try to educate your fellow translators about this issue, it is really making building GNOME package updates cumbersome, since the desktop-file-validate call in the spec file is normally the first place where this breakage becomes apparent. Matthias [1] https://mail.gnome.org/archives/gnome-i18n/2013-January/msg00030.html ___ 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: keywords in desktop files, again
El vie, 22-03-2013 a las 10:24 -0400, Matthias Clasen escribió: I sent a mail about this in January already[1], but we are still seeing a steady stream of broken syntax in translations for the Keywords field in desktop files. Please, try to educate your fellow translators about this issue, it is really making building GNOME package updates cumbersome, since the desktop-file-validate call in the spec file is normally the first place where this breakage becomes apparent. We already have validation of .po files in a pre-receive git hook[1]. Might it be an idea to add validation of .desktop files? Philip [1]: https://git.gnome.org/browse/sysadmin-bin/tree/git/pre-receive-check-po 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: keywords in desktop files, again
On Fri, Mar 22, 2013 at 02:42:39PM +, Philip Withnall wrote: We already have validation of .po files in a pre-receive git hook[1]. Might it be an idea to add validation of .desktop files? Any idea how that could be implemented? I am willing to make it happen, just don't see how. E.g. figure out exactly which line is the Keywords line, etc. -- Regards, Olav ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: keywords in desktop files, again
If you have a jhbuild build, you can run desktop-file-validate on the desktop files in the module. You'll have to rebuild after making translation changes to regenerate those files. Sent from my Samsung Galaxy Note™, an ATT LTE smartphonerafael ff1 rafael.f...@gmail.com wrote:Is there a easy way to track down this bug in every module, except for going in and out of each one? I'd love to make sure it doesn't happen to my language. Rafael Ferreira 2013/3/22 Matthias Clasen matthias.cla...@gmail.com: I sent a mail about this in January already[1], but we are still seeing a steady stream of broken syntax in translations for the Keywords field in desktop files. Please, try to educate your fellow translators about this issue, it is really making building GNOME package updates cumbersome, since the desktop-file-validate call in the spec file is normally the first place where this breakage becomes apparent. Matthias [1] https://mail.gnome.org/archives/gnome-i18n/2013-January/msg00030.html ___ 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: keywords in desktop files, again
El vie, 22-03-2013 a las 15:46 +0100, Olav Vitters escribió: On Fri, Mar 22, 2013 at 02:42:39PM +, Philip Withnall wrote: We already have validation of .po files in a pre-receive git hook[1]. Might it be an idea to add validation of .desktop files? Any idea how that could be implemented? I am willing to make it happen, just don't see how. E.g. figure out exactly which line is the Keywords line, etc. Well, Matthias mentioned desktop-file-validate[1], which appears to do exactly what’s needed, according to its web page. I’ve never used it, though, so I can’t be sure. Philip [1]: http://freedesktop.org/wiki/Software/desktop-file-utils 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: keywords in desktop files, again
On Fri, 2013-03-22 at 15:46 +0100, Olav Vitters wrote: Any idea how that could be implemented? I am willing to make it happen, just don't see how. E.g. figure out exactly which line is the Keywords line, etc. Grep for a line that starts with #: ../ and includes the string .desktop.in.in.h: then find the next line that starts with msgid and ends with ; then count the number of ; in that specific line, compare that number with the next line that starts with msgstr and which is not msgstr which would mean not translated yet. Trigger a warning if the number is not the same. Or something like that. Cough. Sounds error-prone. 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: keywords in desktop files, again
In bash it may be tricky to do this check, but I guess Python could help. I tried to do it in bash and I wasted my time :( 2013/3/22 Andre Klapper ak...@gmx.net On Fri, 2013-03-22 at 15:46 +0100, Olav Vitters wrote: Any idea how that could be implemented? I am willing to make it happen, just don't see how. E.g. figure out exactly which line is the Keywords line, etc. Grep for a line that starts with #: ../ and includes the string .desktop.in.in.h: then find the next line that starts with msgid and ends with ; then count the number of ; in that specific line, compare that number with the next line that starts with msgstr and which is not msgstr which would mean not translated yet. Trigger a warning if the number is not the same. Or something like that. Cough. Sounds error-prone. 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: keywords in desktop files, again
Hi Ask, The Keywords string just has to end with ; to be ok, no need to have the same number of words Many thanks fin advance for your script! 2013/3/22 Ask Hjorth Larsen asklar...@gmail.com Hi Could someone specify how these files *should* be translated? Must there be the same number of elements in the list? I suppose the most obvious thing is that it should end with ;. I'll write a script and check it on all the files, then send a complete list. Regards Ask 2013/3/22 Daniel Mustieles García daniel.mustie...@gmail.com: In bash it may be tricky to do this check, but I guess Python could help. I tried to do it in bash and I wasted my time :( 2013/3/22 Andre Klapper ak...@gmx.net On Fri, 2013-03-22 at 15:46 +0100, Olav Vitters wrote: Any idea how that could be implemented? I am willing to make it happen, just don't see how. E.g. figure out exactly which line is the Keywords line, etc. Grep for a line that starts with #: ../ and includes the string .desktop.in.in.h: then find the next line that starts with msgid and ends with ; then count the number of ; in that specific line, compare that number with the next line that starts with msgstr and which is not msgstr which would mean not translated yet. Trigger a warning if the number is not the same. Or something like that. Cough. Sounds error-prone. 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 ___ 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: keywords in desktop files, again
Hi, here's a script (uses pyg3t): http://www.student.dtu.dk/~ashj/opendir/desktopfilecheck.py I'm actually at work at the moment, but someone can run it or I'll do it tomorrow or so when I have time. Let me know about any issues or if it needs to check for anything else. Regards Ask 2013/3/22 Daniel Mustieles García daniel.mustie...@gmail.com: Hi Ask, The Keywords string just has to end with ; to be ok, no need to have the same number of words Many thanks fin advance for your script! 2013/3/22 Ask Hjorth Larsen asklar...@gmail.com Hi Could someone specify how these files *should* be translated? Must there be the same number of elements in the list? I suppose the most obvious thing is that it should end with ;. I'll write a script and check it on all the files, then send a complete list. Regards Ask 2013/3/22 Daniel Mustieles García daniel.mustie...@gmail.com: In bash it may be tricky to do this check, but I guess Python could help. I tried to do it in bash and I wasted my time :( 2013/3/22 Andre Klapper ak...@gmx.net On Fri, 2013-03-22 at 15:46 +0100, Olav Vitters wrote: Any idea how that could be implemented? I am willing to make it happen, just don't see how. E.g. figure out exactly which line is the Keywords line, etc. Grep for a line that starts with #: ../ and includes the string .desktop.in.in.h: then find the next line that starts with msgid and ends with ; then count the number of ; in that specific line, compare that number with the next line that starts with msgstr and which is not msgstr which would mean not translated yet. Trigger a warning if the number is not the same. Or something like that. Cough. Sounds error-prone. 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 ___ 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: keywords in desktop files, again
It works great!! I've detected (and fixed) an error in gnome-control-center. Thanks!! This weekend ill try to clean the output to be less verbose and I'll create a report with it. Stay tuned!! Again, many thanks! 2013/3/22 Ask Hjorth Larsen asklar...@gmail.com It can be used like this: askhl@mime:~/translate$ find -name *.po | xargs desktopfilecheck.py ./gdm-and-friends/gnome-control-center.gnome-3-8.da.po ERROR, bad syntax line 6684: #. Translators: those are keywords for the wacom tablet control-center panel #: ../panels/wacom/gnome-wacom-panel.desktop.in.in.h:4 msgid Tablet;Wacom;Stylus;Eraser;Mouse; msgstr Tegneplade;Wacom;Pen;Viskelæder;Mus Regards Ask 2013/3/22 Ask Hjorth Larsen asklar...@gmail.com: Hi, here's a script (uses pyg3t): http://www.student.dtu.dk/~ashj/opendir/desktopfilecheck.py I'm actually at work at the moment, but someone can run it or I'll do it tomorrow or so when I have time. Let me know about any issues or if it needs to check for anything else. Regards Ask 2013/3/22 Daniel Mustieles García daniel.mustie...@gmail.com: Hi Ask, The Keywords string just has to end with ; to be ok, no need to have the same number of words Many thanks fin advance for your script! 2013/3/22 Ask Hjorth Larsen asklar...@gmail.com Hi Could someone specify how these files *should* be translated? Must there be the same number of elements in the list? I suppose the most obvious thing is that it should end with ;. I'll write a script and check it on all the files, then send a complete list. Regards Ask 2013/3/22 Daniel Mustieles García daniel.mustie...@gmail.com: In bash it may be tricky to do this check, but I guess Python could help. I tried to do it in bash and I wasted my time :( 2013/3/22 Andre Klapper ak...@gmx.net On Fri, 2013-03-22 at 15:46 +0100, Olav Vitters wrote: Any idea how that could be implemented? I am willing to make it happen, just don't see how. E.g. figure out exactly which line is the Keywords line, etc. Grep for a line that starts with #: ../ and includes the string .desktop.in.in.h: then find the next line that starts with msgid and ends with ; then count the number of ; in that specific line, compare that number with the next line that starts with msgstr and which is not msgstr which would mean not translated yet. Trigger a warning if the number is not the same. Or something like that. Cough. Sounds error-prone. 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 ___ 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: Typos in documentation tags
Hi, Thank you for nice report. Japanese is fixed for only mismathed tags problem. Please allow the rest issue of 'undefined entities'. 'undefined entities' error happen at de-report.txt and ja-report.txt, and all of them belong to GIMP Documentation. These entities consist of nbsp;, hellip;, times;, gt;, mdash;, ndash;, eacute;, and emsp; on the report. As a member of GIMP Documentation Team, I think these terms do not seem to be harmful. In fact such expressions are used, though, even in the XML document source in the standard American English (LANG=C), you can see documents are still well formed on the nightly built HTML of http://docs.gimp.org/ . -- SimaMoto,RyōTa liangtai...@gmail.com, rsimam...@src.gnome.org http://code.google.com/p/gimp-docs-ja/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Regarding Someone to volunteer in GSOC2013 for Gnome Damned-lies project
El dc 20 de 03 de 2013 a les 14:43 +0100, en/na Claude Paroz va escriure: Le mercredi 20 mars 2013 à 06:39 +0530, chandan kumar a écrit : Hello, I am Chandan Kumar who is currently pursuing B.tech in Computer Science And Engineering from Dr.B.C.Roy Engineering College, Durgapur (India). I am contributing to gnome project through Hindi translation and also acting as a committer of Gnome Hindi l10n team from gnome 3.4 release.[1] I know git, Mercurial, python and Django (Beginner), and Basic shell commands. I have tried to solve sum patches for gnome-damned-lies with the help of claude and solving others also.[2] I have approached to apply for GSOC 2013 under the guidance of GIl Forcada for this project. But due to some reason, he is not volunteering for gsoc 2013 for this project. If anybody wants to or willing to volunteer me as a mentor for gnome Damned-lies project? it would be appreciable. Links:- [1] https://l10n.gnome.org/users/chandankumar/ [2] https://git.gnome.org/browse/damned-lies/commit/?id=a3aa061a8f2e677f0d1a0870b019754709686802 I will repeat what I have already said: I'm always available to give any counsel about DL development, but I will not act as an official GSOC mentor. Cheers, Claude and sadly, as I already said, me being father in a week or so doesn't give me too much confidence on being able to be a proper mentor. Ocasional help, as I've done by now is what I can mostly offer. So if you find someone wanting to put more time, Claude and me helping here and there maybe you can still make it! Cheers, -- 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: Typos in documentation tags
Hi Daniel, Thank you for the report. I'll check errors like this before commit. Could you tell me how you caught the broken tags? On Thu, Mar 21, 2013 at 12:49 AM, Daniel Mustieles García daniel.mustie...@gmail.com wrote: Hi again. As promised, here is the updated report about typos in documentation tags. If your language is on the list, please review and fix to avoid errors when compiling the affected modules. Below is the list of the languages with errors. Please note that this report reflects typos in ALL the documentation files. Since we are near the 3.8 release, maybe you'll want to focus your efforts in just the core modules. If someone wants it, I can generate a report with just the typos in core documentation. Many thanks for your help and happy translating! ca cs da de el eu fa fi fr gl id it ja ko mk nl pa pl pt_BR ro ru sl sr@latin sr sv th uk zh_CN zh_HK zh_TW 2013/2/21 Andika Triwidada and...@gmail.com On Wed, Feb 20, 2013 at 7:45 PM, Daniel Mustieles García daniel.mustie...@gmail.com wrote: Please forget about my previous mail... i didn't change the RELEASE variable in my script, so the reports generated were about the 3.6 release. Here are the 3.8 reports and the list of the languages affected: de el es fr id pt_BR ru sl Thanks for pointer. id was fixed. Regards, Andika Triwidada ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Jiro Matsuzawa E-mail: jmatsuz...@gnome.org jmatsuz...@src.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
