GNOME.org
 

Re: XML errors in documentation PO file

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 <rafael f f1 gmail com>
Christian,

Try the trunk version in Pyg3t's bzr repository. The latest released version has a known issue with some utf8 chars. [1]


Cheers,
Rafael Ferreira


2013/9/21 Christian Kirbach <christian kirbach gmail com>
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>
...
    xml = u''.join([u'<xml>', string.replace(u'\\"', u'"'), u'</xml>'])
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 <piotrdrag gmail com>
>         2013/9/15 Daniel Mustieles García
>         <daniel mustieles 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
>         > 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 <christian kirbach gmail com>
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


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