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 th
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 ta
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 o
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
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,
gi
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í
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 documenta
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.
Hungarian is fixed, thanks Daniel!
-- Balázs
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
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
>
> 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 t
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
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,
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
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
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
of
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 :
> Hello
>
> Thanks Daniel, ¡muchas gracias como siempre! And thanks, Piotr.
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 :
> 2014-03-07 16:32 GMT+01:00 Daniel Mustieles García
> :
>> As usual, I've made a report with some typos or errors in X
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
2014-03-07 16:32 GMT+01:00 Daniel Mustieles García :
> 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
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
07.03.2014, 19:33, "Daniel Mustieles García" :
> 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.
_
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 rel
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
Also you can download latest version from the repo and it works properly
for me ;-)
2013/9/22 Kenneth Nielsen
> 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
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
simp
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
> Hi Daniel
>
> thanks for running t
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
...
xml
2013/9/15 Daniel Mustieles García :
> 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 enou
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 t
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
> 2013/9/10 Daniel Mustieles García :
> > I've generated a report with some bugs and typos in documentation PO
> files.
> > As you know, these kind of error
2013/9/10 Daniel Mustieles García :
> 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 gene
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 mailto:live...@gmail.com>>
Thank you,
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
in the translated string)
gl/gdm-help.master.gl.po, line 1308: mismatched tag
---
#. (itstool) path: sect2/para
#:
Everything seems to be ok in your language Enrico.
Thanks for your quick fix :)
2013/9/11 Enrico Nicoletto
> 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 nee
Thanks to you Fran.
It seems there is a remaining mismatching tag in GDM (missin in
the translated string)
gl/gdm-help.master.gl.po, line 1308: mismatched tag
---
#. (itstool) path: sect2/para
#: C/index.docbook:815
msgid ""
"to /hosts.deny. Y
11.09.13 03:28, Piotr Drąg написав(ла):
2013/9/10 Daniel Mustieles García :
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 coordinato
2013/9/10 Daniel Mustieles García :
> 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 th
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í
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 modul
On Tue, Sep 10, 2013 at 9:45 PM, Daniel Mustieles García
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
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
10.09.2013, 18:45, "Daniel Mustieles García" :
> 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.
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
> Hi Daniel,
>
> Thank you for the report.
>
> As for Japanese, all gtxml detected are "undefined enti
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
--
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 use
On Mon, 2013-04-08 at 11:30 +0200, Daniel Mustieles García wrote:
> 2013/4/6 Gabor Kelemen
>
>
> 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 ad
2013/4/6 Gabor Kelemen
>
>
> 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
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
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
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 sc
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 the
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 c
Hi
2012/9/16 Piotr Drąg :
> 2012/9/15 Alexandre Franke :
>> Can you try & 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
2012/9/15 Alexandre Franke :
> Can you try & 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
On Fri, Sep 14, 2012 at 6:52 PM, Piotr Drąg wrote:
> 2012/9/14 Daniel Mustieles García :
> 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 & as a r
2012/9/14 Tom Tryfonidis :
> 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.gnom
On 14 September 2012 19:52, Piotr Drąg wrote:
> 2012/9/14 Daniel Mustieles García :
> > 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 except
2012/9/14 Daniel Mustieles García :
> 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
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
> 2012/9/13 Daniel Mustieles García :
> > I've generated several reports, one for each language, about errors in
> tags
> > in the docume
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 d
2012/9/13 Daniel Mustieles García :
> 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
On Thu, Sep 13, 2012 at 8:09 AM, Daniel Mustieles García
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
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 tim
2012/9/13 Gabor Kelemen :
> 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 wil
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 a
To view te report properly, just do cat 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ý
> Yeah, fixed.
> Reported file for Czech displays some garbage characters and I
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:
>
> UpravitPřidat soubory "gui>.
>
> Note that the first tag (opening «guiseq») has a slash.
>
> You can find
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 cor
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
Here is the bug:
UpravitPřidat soubory.
Note that the first tag (opening <>) 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ý
> Where I can find this PO files? I checked the Czech translation a
Hi
2012/9/13 Daniel Mustieles García :
> 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
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
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.
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 Englis
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 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
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 … apparently xml doesn't like it.
You can just use the character (…) U+2026 directly in a UTF-8 encoded
file. Perhaps your enc
Hi Andre and Claude
On Wed, Oct 20, 2010 at 9:50 AM, Claude Paroz 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 s
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 million for these valuable tools, now all of them are part of
my Q&A 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-i
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
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
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 a
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.
> The xml checks were performed with the utility gtxml from pyg3t (in
> case you want to run your own xml c
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
85 matches
Mail list logo
