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
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
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
...
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
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
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
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.
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
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
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
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
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:
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
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
--
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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
39 matches
Mail list logo
