(One year later, anyway:)
On Fri, 2013-03-22 at 10:24 -0400, Matthias Clasen wrote:
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.
A pre-commit check for po files could refuse
Hi Ask,
You can use this script to get all the PO files for the most relevant
languages. The script also has the ability to get all the language codes
from DL, sou you can get all the PO files from all the languages.
Cheers!
2013/3/23 Ask Hjorth Larsen asklar...@gmail.com
Hi
What is the
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
Thanks, the one in Danish has been corrected :)
2013/3/24 Daniel Mustieles García daniel.mustie...@gmail.com:
Hi all,
Here is the report I've generated about the missing «;» in the Keywords
translated string.
Translation team coordinator: As this is an important fix we should do
before the
Hi
What is the easiest way to download all the translations in all languages?
Regards
Ask
2013/3/22 Daniel Mustieles García daniel.mustie...@gmail.com:
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
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
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
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
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
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
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:
Wouldn't both tasks - XML syntax check and keyword check in desktop
files - make a fine GnomeGoal?
Am Donnerstag, den 17.01.2013, 14:04 +0100 schrieb Daniel Mustieles
García:
Another check that should be implemented is the XML syntax check done
in gtxml [1]. It checks the documentation PO
Speaking of keywords:
When translating - I add the Bulgarian translation and then copy and add
the English original because people will search and expect both the
translated and the original version.
Is there any problem with this strategy?
Kind regards:
al_shopov
On Wed, Jan 16, 2013 at 02:31:41PM -0500, Matthias Clasen wrote:
In trying to build 3.7.4 in Fedora, I've come across a few modules
where translations got this wrong. Here is an example:
I usually just commit fixes for that, but Mageia is sticking with 3.6
for now.
Any way to check this on the
On Thu, Jan 17, 2013 at 3:55 AM, Olav Vitters o...@vitters.nl wrote:
On Wed, Jan 16, 2013 at 02:31:41PM -0500, Matthias Clasen wrote:
In trying to build 3.7.4 in Fedora, I've come across a few modules
where translations got this wrong. Here is an example:
I usually just commit fixes for that,
On Thu, Jan 17, 2013 at 05:55:18AM -0500, Matthias Clasen wrote:
On Thu, Jan 17, 2013 at 3:55 AM, Olav Vitters o...@vitters.nl wrote:
On Wed, Jan 16, 2013 at 02:31:41PM -0500, Matthias Clasen wrote:
In trying to build 3.7.4 in Fedora, I've come across a few modules
where translations got
Another check that should be implemented is the XML syntax check done in
gtxml [1]. It checks the documentation PO files syntax, and is really
useful to avoid errors in malfomed or wrong tags in doc files.
[1] https://launchpad.net/pyg3t
2013/1/17 Matthias Clasen matthias.cla...@gmail.com
On
Thanks Matthias for your advice. I've also noticed this same error in some
originals strings, and I've fixed it, but It would be great if there were a
way to check it without reviewing all the PO files. I'll investigate it and
will post here the results.
I'd also like to comment that adding this
Il giorno mer, 24/11/2010 alle 00.36 +0200, Lucian Adrian Grijincu ha
scritto:
Hi,
In
http://git.gnome.org/browse/gnome-control-center/tree/panels/display/gnome-display-panel.desktop.in.in
There's this string marked for translation:
# Translators: those are keywords for the display
Hi,
In
http://git.gnome.org/browse/gnome-control-center/tree/panels/display/gnome-display-panel.desktop.in.in
There's this string marked for translation:
# Translators: those are keywords for the display control-center panel
_X-GNOME-Keywords=Panel;Projector;xrandr;Screen;Resolution;Refresh;
25 matches
Mail list logo
