GNOME.org
 

Re: XML errors in documentation PO file

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


2013/9/13 Daniel Mustieles García <daniel mustieles gmail com>
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 <piotrdrag gmail com>
2013/9/10 Daniel Mustieles García <daniel mustieles 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.
>
> 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,


Attachment: gtxml-doc-reports.tar.gz
Description: GNU Zip compressed data

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]