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
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
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
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
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
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
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
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,
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
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
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:
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;,
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).
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
14 matches
Mail list logo
