subject:"xml errors in documentation"

Re: XML errors in documentation PO file

2013-09-22 Thread Daniel Mustieles García

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 problems, but hopefully we should get around
> to doing a new release soon. In the meantime, it is not that difficult to
> simply run it from a source code checkout. It just requires adding the
> relevant paths to $PATH and $PYTHONPATH in the .bashrc. Let me know if it
> gives you any trouble.
>
> Regards Kenneth
>
>
> 2013/9/21 Rafael Ferreira 
>
>> 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 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 = u''.join([u'', string.replace(u'\\"', u'"'), u''])
>>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7:
>>> ordinal not in range(128)
>>>
>>>
>>> Am Montag, den 16.09.2013, 11:05 +0200 schrieb Daniel Mustieles García:
>>> > Thanks Piotr (and all of you) for fixing the errors.
>>> >
>>> >
>>> > Here is a new report, generated with a previous version of Pyg3t, so
>>> > most of the invalid token errors are now away. There are still some
>>> > erros in tags, so it would be interesting to take a look into it.
>>> >
>>> >
>>> > This is the list of the affected languages:
>>> >
>>> > de
>>> > fi
>>> > fr
>>> > ja
>>> > sl
>>> > zh_CN
>>> >
>>> >
>>> > Like other times, just fixing mismatching tags in translated string
>>> > should be enough, so you can ignore the rest of the error messages.
>>> >
>>> >
>>> > Again, thanks to all of you for taking care of this.
>>> >
>>> >
>>> > Best regards
>>> >
>>> >
>>> >
>>> > 2013/9/16 Piotr Drąg 
>>> > 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 enough.
>>> > >
>>> >
>>> >
>>> > Thank you! I think all known errors are fixed now. Thanks to
>>> > everyone
>>> > for fixing their translations!
>>> >
>>> > --
>>> > Piotr Drąg
>>> > http://raven.fedorapeople.org/
>>> >
>>> >
>>> >
>>> > ___
>>> > gnome-i18n mailing list
>>> > gnome-i18n@gnome.org
>>> > https://mail.gnome.org/mailman/listinfo/gnome-i18n
>>>
>>> --
>>> Christian Kirbach 
>>> Keine Lust auf NSA und den Lauschangriff? Mein PGP-Schlüssel 1FE120E3
>>> (seit 2005)
>>>  -> http://www.elektronikinfo.de/pc/pgp.htm
>>>
>>>
>>>
>>>
>>> ___
>>> 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
>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-22 Thread 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 problems, but hopefully we should get around
to doing a new release soon. In the meantime, it is not that difficult to
simply run it from a source code checkout. It just requires adding the
relevant paths to $PATH and $PYTHONPATH in the .bashrc. Let me know if it
gives you any trouble.

Regards Kenneth


2013/9/21 Rafael Ferreira 

> 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 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 = u''.join([u'', string.replace(u'\\"', u'"'), u''])
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7:
>> ordinal not in range(128)
>>
>>
>> Am Montag, den 16.09.2013, 11:05 +0200 schrieb Daniel Mustieles García:
>> > Thanks Piotr (and all of you) for fixing the errors.
>> >
>> >
>> > Here is a new report, generated with a previous version of Pyg3t, so
>> > most of the invalid token errors are now away. There are still some
>> > erros in tags, so it would be interesting to take a look into it.
>> >
>> >
>> > This is the list of the affected languages:
>> >
>> > de
>> > fi
>> > fr
>> > ja
>> > sl
>> > zh_CN
>> >
>> >
>> > Like other times, just fixing mismatching tags in translated string
>> > should be enough, so you can ignore the rest of the error messages.
>> >
>> >
>> > Again, thanks to all of you for taking care of this.
>> >
>> >
>> > Best regards
>> >
>> >
>> >
>> > 2013/9/16 Piotr Drąg 
>> > 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 enough.
>> > >
>> >
>> >
>> > Thank you! I think all known errors are fixed now. Thanks to
>> > everyone
>> > for fixing their translations!
>> >
>> > --
>> > Piotr Drąg
>> > http://raven.fedorapeople.org/
>> >
>> >
>> >
>> > ___
>> > gnome-i18n mailing list
>> > gnome-i18n@gnome.org
>> > https://mail.gnome.org/mailman/listinfo/gnome-i18n
>>
>> --
>> Christian Kirbach 
>> Keine Lust auf NSA und den Lauschangriff? Mein PGP-Schlüssel 1FE120E3
>> (seit 2005)
>>  -> http://www.elektronikinfo.de/pc/pgp.htm
>>
>>
>>
>>
>> ___
>> 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: XML errors in documentation PO file

2013-09-21 Thread Rafael Ferreira

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 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 = u''.join([u'', string.replace(u'\\"', u'"'), u''])
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7:
> ordinal not in range(128)
>
>
> Am Montag, den 16.09.2013, 11:05 +0200 schrieb Daniel Mustieles García:
> > Thanks Piotr (and all of you) for fixing the errors.
> >
> >
> > Here is a new report, generated with a previous version of Pyg3t, so
> > most of the invalid token errors are now away. There are still some
> > erros in tags, so it would be interesting to take a look into it.
> >
> >
> > This is the list of the affected languages:
> >
> > de
> > fi
> > fr
> > ja
> > sl
> > zh_CN
> >
> >
> > Like other times, just fixing mismatching tags in translated string
> > should be enough, so you can ignore the rest of the error messages.
> >
> >
> > Again, thanks to all of you for taking care of this.
> >
> >
> > Best regards
> >
> >
> >
> > 2013/9/16 Piotr Drąg 
> > 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 enough.
> > >
> >
> >
> > Thank you! I think all known errors are fixed now. Thanks to
> > everyone
> > for fixing their translations!
> >
> > --
> > Piotr Drąg
> > http://raven.fedorapeople.org/
> >
> >
> >
> > ___
> > gnome-i18n mailing list
> > gnome-i18n@gnome.org
> > https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
> --
> Christian Kirbach 
> Keine Lust auf NSA und den Lauschangriff? Mein PGP-Schlüssel 1FE120E3
> (seit 2005)
>  -> http://www.elektronikinfo.de/pc/pgp.htm
>
>
>
>
> ___
> 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: XML errors in documentation PO file

2013-09-21 Thread Christian Kirbach

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 = u''.join([u'', string.replace(u'\\"', u'"'), u''])
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7:
ordinal not in range(128)


Am Montag, den 16.09.2013, 11:05 +0200 schrieb Daniel Mustieles García:
> Thanks Piotr (and all of you) for fixing the errors.
> 
> 
> Here is a new report, generated with a previous version of Pyg3t, so
> most of the invalid token errors are now away. There are still some
> erros in tags, so it would be interesting to take a look into it.
> 
> 
> This is the list of the affected languages:
> 
> de
> fi
> fr
> ja
> sl
> zh_CN
> 
> 
> Like other times, just fixing mismatching tags in translated string
> should be enough, so you can ignore the rest of the error messages.
> 
> 
> Again, thanks to all of you for taking care of this.
> 
> 
> Best regards
> 
> 
> 
> 2013/9/16 Piotr Drąg 
> 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 enough.
> >
> 
> 
> Thank you! I think all known errors are fixed now. Thanks to
> everyone
> for fixing their translations!
> 
> --
> Piotr Drąg
> http://raven.fedorapeople.org/
> 
> 
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n

-- 
Christian Kirbach 
Keine Lust auf NSA und den Lauschangriff? Mein PGP-Schlüssel 1FE120E3 (seit 
2005)
 -> http://www.elektronikinfo.de/pc/pgp.htm





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: XML errors in documentation PO file

2013-09-15 Thread Piotr Drąg

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 enough.
>

Thank you! I think all known errors are fixed now. Thanks to everyone
for fixing their translations!

-- 
Piotr Drąg
http://raven.fedorapeople.org/
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-15 Thread Enrico Nicoletto


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 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 enough.


I'm going to talk with PyG3t maintainers to see if there is a way to 
avoid the invalid token message, to simplify reports and do not 
generate noise.


Best regards


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-13 Thread Daniel Mustieles García

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 errors may break the modules's compilation
> > process, so it would be great if each afected language coordinator could
> fix
> > them.
> >
> > These reports are generated by an automated script using gtxml. If you
> want
> > a copy of the script, feel free to ask me about it.
> >
> > Thanks in advance and best regards
> >
>
> Hi,
>
> It seems that most of the errors have been fixed. Do you mind
> generating the report again so we can be sure?
>
> Thanks for taking care of this,
>
> --
> Piotr Drąg
> http://raven.fedorapeople.org/
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-13 Thread 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 errors may break the modules's compilation
> process, so it would be great if each afected language coordinator could fix
> them.
>
> These reports are generated by an automated script using gtxml. If you want
> a copy of the script, feel free to ask me about it.
>
> Thanks in advance and best regards
>

Hi,

It seems that most of the errors have been fixed. Do you mind
generating the report again so we can be sure?

Thanks for taking care of this,

-- 
Piotr Drąg
http://raven.fedorapeople.org/
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-11 Thread Enrico Nicoletto


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, 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ía escreveu:

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 the list of the affected languages:

cs
de
el
eu
fr
gl
id
it
ja
ko
pt_BR
ru
sl
sr
sr@latin
sv
th
uk
zh_CN

These reports are generated by an automated script using gtxml.
If you want a copy of the script, feel free to ask me about it.

Thanks in advance and best regards


___
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: XML errors in documentation PO file

2013-09-11 Thread Fran Dieguez


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
#: C/index.docbook:815
msgid ""
"to /hosts.deny. You may also need to add"
msgstr "a /hosts.deny. Tamén precisa engadir"

Cheers!


Ok, done
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-11 Thread Daniel Mustieles García

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 needs our attention.
>
> Kindly Regards,
> Enrico Nicoletto.
> __
>
> Em 10/09/2013 11:45, Daniel Mustieles García escreveu:
>
>   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 the list of the affected languages:
>
> cs
> de
> el
> eu
> fr
> gl
> id
> it
> ja
> ko
> pt_BR
> ru
> sl
> sr
> sr@latin
> sv
> th
> uk
> zh_CN
>
>  These reports are generated by an automated script using gtxml. If you
> want a copy of the script, feel free to ask me about it.
>
>  Thanks in advance and best regards
>
>
> ___
> gnome-i18n mailing 
> listgnome-i18n@gnome.orghttps://mail.gnome.org/mailman/listinfo/gnome-i18n
>
>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-11 Thread Daniel Mustieles García

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. You may also need to add"
msgstr "a /hosts.deny. Tamén precisa engadir"

Cheers!


2013/9/10 Fran Dieguez 

> 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 modules's
>>> compilation process, so it would be great if each afected language
>>> coordinator could fix them.
>>>
>>>
>>> This is the list of the affected languages:
>>>
>>> cs
>>> de
>>> el
>>> eu
>>> fr
>>> gl
>>> id
>>> it
>>> ja
>>> ko
>>> pt_BR
>>> ru
>>> sl
>>> sr
>>> sr@latin
>>> sv
>>> th
>>> uk
>>> zh_CN
>>>
>>>
>>> These reports are generated by an automated script using gtxml. If you
>>> want a copy of the script, feel free to ask me about it.
>>>
>>>
>>> Thanks in advance and best regards
>>>
>>> __**_
>>> 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
>>
>
> Hi Dani,
>
> Thanks a lot for taking your time and report those errors.
>
> All fixed from the Galician group side.
>
> Regards.
>
> __**_
> 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: XML errors in documentation PO file

2013-09-11 Thread Коростіль Данило


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 coordinator could fix
them.

This is the list of the affected languages:

el
eu
ko
sr
sr@latin
sv
th
uk


I've fixed errors in above languages.


Thanks!
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-10 Thread 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 coordinator could fix
> them.
>
> This is the list of the affected languages:
>
> el
> eu
> ko
> sr
> sr@latin
> sv
> th
> uk
>

I've fixed errors in above languages.

-- 
Piotr Drąg
http://raven.fedorapeople.org/
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-10 Thread 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 needs our attention.

Kindly Regards,
Enrico Nicoletto.
__

Em 10/09/2013 11:45, Daniel Mustieles García escreveu:

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 the list of the affected languages:

cs
de
el
eu
fr
gl
id
it
ja
ko
pt_BR
ru
sl
sr
sr@latin
sv
th
uk
zh_CN

These reports are generated by an automated script using gtxml. If you 
want a copy of the script, feel free to ask me about it.


Thanks in advance and best regards


___
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: XML errors in documentation PO file

2013-09-10 Thread Fran Dieguez


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 modules's
compilation process, so it would be great if each afected language
coordinator could fix them.


This is the list of the affected languages:

cs
de
el
eu
fr
gl
id
it
ja
ko
pt_BR
ru
sl
sr
sr@latin
sv
th
uk
zh_CN


These reports are generated by an automated script using gtxml. If you
want a copy of the script, feel free to ask me about it.


Thanks in advance and best regards

___
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


Hi Dani,

Thanks a lot for taking your time and report those errors.

All fixed from the Galician group side.

Regards.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-10 Thread Andika Triwidada

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 could fix 
> them.
>
> This is the list of the affected languages:
>
> id

Thank you. Indonesian translation cleaned up.

>
>
> These reports are generated by an automated script using gtxml. If you want a 
> copy of the script, feel free to ask me about it.
>
> Thanks in advance and best regards
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-10 Thread Marek Černocký

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 each afected language
> coordinator could fix them.
> 
> 
> This is the list of the affected languages:
> 
> cs
> de
> el
> eu
> fr
> gl
> id
> it
> ja
> ko
> pt_BR
> ru
> sl
> sr
> sr@latin
> sv
> th
> uk
> zh_CN
> 
> 
> These reports are generated by an automated script using gtxml. If you
> want a copy of the script, feel free to ask me about it.
> 
> 
> Thanks in advance and best regards
> 
> ___
> 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: XML errors in documentation PO file

2013-09-10 Thread Yuri Myasoedov

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.
>
> This is the list of the affected languages:
>
> ru

Russian translations fixed.

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-10 Thread Daniel Mustieles García

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 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
>
>
> --
> Jiro Matsuzawa
> E-mail:
>  jmatsuz...@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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: XML errors in documentation PO file

2013-09-10 Thread Jiro Matsuzawa

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


-- 
Jiro Matsuzawa
E-mail:
 jmatsuz...@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

Re: More on xml errors in documentation

2013-04-15 Thread Daniel Mustieles García

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 useful to have this check, so translators and
coordinators would be aware of them.

Cheers

2013/4/8 Shaun McCance 

> 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 adds some tags
> > to the original strings, translators should keep those strings. Also,
> > having freedom to add our own tags to translated string may break the
> > building process so fixing those errors should be fixed.
> >
> > I don't know how Mallard documents work, and how translators have to
> > deal with tags (I mean: should we add or remove tags when translating
> > strings? Shouldn't it be done by the Documentation team?) I think
> > translators shouldn't change the format adding or removing tags
> > (althouhg it doesn't break the compilation), but having some comments
> > from docs team would be really useful.
>
> I think there are cases where it's worthwhile for translators to add
> tags, but they're probably the exception. Thinking out loud:
>
> * East Asian languages might want to add Ruby markup. And this will
> actually work correctly in 3.10.
>
> * Some languages might want to use an English word for a technical
> term when there isn't yet an established local word. They might want
> to mark this with .
>
> * The instructions for certain actions on different keyboard layouts
> might involve more or fewer  elements than for en-US.
>
> If we really end up getting a lot of false positives, or if we want
> to turn these checks into hard pre-commit checks, we could add some
> sort of markup to allow translators to say "I know what I'm doing in
> this case". But that can be a hassle, so it's only worthwhile if we
> have a real problem with false positives.
>
> --
> Shaun
>
>
>
>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: More on xml errors in documentation

2013-04-08 Thread Shaun McCance

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 adds some tags
> to the original strings, translators should keep those strings. Also,
> having freedom to add our own tags to translated string may break the
> building process so fixing those errors should be fixed.
> 
> I don't know how Mallard documents work, and how translators have to
> deal with tags (I mean: should we add or remove tags when translating
> strings? Shouldn't it be done by the Documentation team?) I think
> translators shouldn't change the format adding or removing tags
> (althouhg it doesn't break the compilation), but having some comments
> from docs team would be really useful.

I think there are cases where it's worthwhile for translators to add
tags, but they're probably the exception. Thinking out loud:

* East Asian languages might want to add Ruby markup. And this will
actually work correctly in 3.10.

* Some languages might want to use an English word for a technical
term when there isn't yet an established local word. They might want
to mark this with .

* The instructions for certain actions on different keyboard layouts
might involve more or fewer  elements than for en-US.

If we really end up getting a lot of false positives, or if we want
to turn these checks into hard pre-commit checks, we could add some
sort of markup to allow translators to say "I know what I'm doing in
this case". But that can be a hassle, so it's only worthwhile if we
have a real problem with false positives.

--
Shaun

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: More on xml errors in documentation

2013-04-08 Thread Daniel Mustieles García

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 tags to translated string may break the building
process so fixing those errors should be fixed.

I don't know how Mallard documents work, and how translators have to deal
with tags (I mean: should we add or remove tags when translating strings?
Shouldn't it be done by the Documentation team?) I think translators
shouldn't change the format adding or removing tags (althouhg it doesn't
break the compilation), but having some comments from docs team would be
really useful.

Cheers!


>
> Regards and thanks for the feature
> Gabor Kelemen
>
>
> ___
> 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: More on xml errors in documentation

2013-04-06 Thread Gabor Kelemen

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 add, say, ... to a programme name
> when the msgid didn't.  I will appreciate any feedback ("this is
> ridiculous, everything was totally okay" or otherwise).
> 

For me, it is useful - these indeed show some real bugs, like using gui
tag instead of app. However, there are some really harmless false
positives reported like adding extra tags where there was none in the
original - we should have this much freedom.

I think these kinds of warnings are useful, until it is not compulsory
to fix all of them :).

Regards and thanks for the feature
Gabor Kelemen



signature.asc
Description: OpenPGP digital signature
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: More on xml errors in documentation

2013-04-05 Thread Daniel Mustieles García

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 for taking care of this

2013/4/5 Christian Kirbach 

> 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 schrieb Ask Hjorth Larsen:
> > 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 cases where
> > the translator chooses to add, say, ... to a programme name
> > when the msgid didn't.  I will appreciate any feedback ("this is
> > ridiculous, everything was totally okay" or otherwise).
> >
> > Here are the reports.  Only some languages with many doc translations
> > have been included.
> >
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt
> >
> > Best regards
> > Ask
> > ___
> > gnome-i18n mailing list
> > gnome-i18n@gnome.org
> > https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
> --
> Christian Kirbach 
>
> ___
> 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: More on xml errors in documentation

2013-04-05 Thread Christian Kirbach

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 schrieb Ask Hjorth Larsen:
> 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 cases where
> the translator chooses to add, say, ... to a programme name
> when the msgid didn't.  I will appreciate any feedback ("this is
> ridiculous, everything was totally okay" or otherwise).
> 
> Here are the reports.  Only some languages with many doc translations
> have been included.
> 
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt
> 
> Best regards
> Ask
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n

-- 
Christian Kirbach 


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: More on xml errors in documentation

2013-04-05 Thread Daniel Mustieles García

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 they aren't
mandatory, there is no need to do this kind of check, but then there are
other problems: unreviewd tags may become deprecated, so documentaion might
not been shown properly, these tags might neve be included in translated
strings, just bothering translators...

Both Ask and me have no much idea about Mallard, so any comment or
explanation about how it works will be welcome.

Thanks in advance!

2013/4/4 Ask Hjorth Larsen 

> 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 cases where
> the translator chooses to add, say, ... to a programme name
> when the msgid didn't.  I will appreciate any feedback ("this is
> ridiculous, everything was totally okay" or otherwise).
>
> Here are the reports.  Only some languages with many doc translations
> have been included.
>
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt
>
> Best regards
> Ask
> ___
> 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: xml errors in documentation

2010-11-06 Thread Mario Blättermann

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 string is valid xml, but the translation is
> not. You may want to fix them as this probably means the messages are
> not displayed correctly in the help documents.
> 
…
> ./de/summary.txt:Total errors 14

These errors are fixed now for all the mentioned modules in German. Thanks for 
the hint.

Best Regards,
Mario
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-22 Thread F Wolff

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 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 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
> >> display an error on the website (or already when uploading it)?
> >
> > Talking of QA tool integration, I'd prefer beginning with
> > translate-toolkit [1].
> > Can you tell us how this project is different from it and why they
> > couldn't be merged?
> >
> > Claude
> 
> It definitely has a lot in common with the translate toolkit.  But
> also some differences.  The present xml tool was written specifically
> because we wanted to weed out xml errors in the gnome docs without too
> many false positives.  The xml check of the translate toolkit will
> write more complaints, but is also more likely to get false positives.
>  If we want to run something like this on damned lies, I think it
> should only complain about real errors.
> 
> Some of the pyg3t scripts are bit specialized to the kind of stuff we
> (Danish translation team) do, and tend to be less general than the
> translate-toolkit.  It's the question of how one would want to combine
> utilities that do close to the same thing.  Does anyone here work on
> translate toolkit?

Yes. I am one of the developers for the project.

Keep well
Friedel


--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/draft-anloc-foss-localisation-manual

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-22 Thread Wouter Bolsterlee

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 encoding was not set correctly? (Fwiw, Latin1 doesn't
include …)

— Wouter


signature.asc
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-20 Thread 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 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 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
>> display an error on the website (or already when uploading it)?
>
> Talking of QA tool integration, I'd prefer beginning with
> translate-toolkit [1].
> Can you tell us how this project is different from it and why they
> couldn't be merged?
>
> Claude

It definitely has a lot in common with the translate toolkit.  But
also some differences.  The present xml tool was written specifically
because we wanted to weed out xml errors in the gnome docs without too
many false positives.  The xml check of the translate toolkit will
write more complaints, but is also more likely to get false positives.
 If we want to run something like this on damned lies, I think it
should only complain about real errors.

Some of the pyg3t scripts are bit specialized to the kind of stuff we
(Danish translation team) do, and tend to be less general than the
translate-toolkit.  It's the question of how one would want to combine
utilities that do close to the same thing.  Does anyone here work on
translate toolkit?

In any case, I'm willing to help integrating a periodic check on
damned lies (shouldn't be difficult).

Regards
Ask Hjorth Larsen
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-20 Thread F Wolff

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 lot. Fixed for cs.
> 
> Fixed for fr also.
> 
> > > 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
> > display an error on the website (or already when uploading it)?
> 
> Talking of QA tool integration, I'd prefer beginning with
> translate-toolkit [1].
> Can you tell us how this project is different from it and why they
> couldn't be merged?
> 
> Claude
> 
> [1] http://translate.sourceforge.net/wiki/toolkit/index


>From a _very_ quick look, it seems that an XML parser is used to check
for valid XML, whereas pofilter from the Translate Toolkit checks for
the use of the same XML, and that attributes are unchanged (except for
things like alt and title in HTML).

I've wanted to do something similar to actually check for valid XML
structure in pofilter's xmltags test, and I think that would be a good
change to do.  However, I think pofilter still has an interesting
approach here in that it restricts the translator's XML vocabulary, and
that it has 40 other tests, of course.

In the case where the source string wasn't valid XML to begin with
(snippets, or invalid entities), I guess pofilter will give the only
possibility for automated QA.

Friedel


--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/draft-anloc-foss-localisation-manual

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-20 Thread Fran Dieguez

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-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-20 Thread 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 lot. Fixed for cs.

Fixed for fr also.

> > 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
> display an error on the website (or already when uploading it)?

Talking of QA tool integration, I'd prefer beginning with
translate-toolkit [1].
Can you tell us how this project is different from it and why they
couldn't be merged?

Claude

[1] http://translate.sourceforge.net/wiki/toolkit/index

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-19 Thread Jorge González González

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 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 string is valid xml, but the translation is
> not.  You may want to fix them as this probably means the messages are
> not displayed correctly in the help documents.

Thanks a lot, "es" fixed. However most of the errors came from epiphany,
where I replaced ... with … apparently xml doesn't like it.

Cheers.
-- 
Jorge González González 
Weblog: http://aloriel.no-ip.org
Fotolog: http://www.flickr.com/photos/aloriel

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-19 Thread Jorge González González

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
> display an error on the website (or already when uploading it)?
Yeap, that would be awesome.

> 
> andre

-- 
Jorge González González 
Weblog: http://aloriel.no-ip.org
Fotolog: http://www.flickr.com/photos/aloriel

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: xml errors in documentation

2010-10-19 Thread Andre Klapper

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 checks subsequently):
>   https://launchpad.net/pyg3t

Naive idea: Could something similar could run on l10n.gnome.org and
display an error on the website (or already when uploading it)?

andre
-- 
mailto:ak...@gmx.net | failed
http://blogs.gnome.org/aklapper

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

xml errors in documentation

2010-10-19 Thread Ask Hjorth Larsen

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 reasonable
(> around 10%) coverage of the documentation.  More precisely, every
message where the English string is valid xml, but the translation is
not.  You may want to fix them as this probably means the messages are
not displayed correctly in the help documents.

Here's the list of numbers of errors for each language (if it's zero,
ignore this :)):

./eu/summary.txt:Total errors 0
./ja/summary.txt:Total errors 2
./el/summary.txt:Total errors 3
./gl/summary.txt:Total errors 22
./ko/summary.txt:Total errors 9
./it/summary.txt:Total errors 6
./de/summary.txt:Total errors 14
./zh_CN/summary.txt:Total errors 27
./sv/summary.txt:Total errors 1
./es/summary.txt:Total errors 19
./fr/summary.txt:Total errors 22
./en_GB/summary.txt:Total errors 0
./fi/summary.txt:Total errors 25
./pt_BR/summary.txt:Total errors 8
./ru/summary.txt:Total errors 10
./uk/summary.txt:Total errors 8
./cs/summary.txt:Total errors 3
./bg/summary.txt:Total errors 3
./hu/summary.txt:Total errors 4
./ca/summary.txt:Total errors 5
./pt/summary.txt:Total errors 0
./da/summary.txt:Total errors 9

The total number of errors is 182.

The specific location of each error can be found by consulting the
text files located 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):
  https://launchpad.net/pyg3t

Best regards
Ask Hjorth Larsen
Danish translation team
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

40 matches

Mail list logo