Report XML SyntaxError in XPI files as TranslationFormatSyntaxError

[Jeroen T. Vermeulen]

An XML parser error in XPI is reported as an unexpected exception:

https://pastebin.canonical.com/4120/

It should be reported as a syntax error (TranslationFormatSyntaxError), so the user gets proper feedback.

[Diogo Matsubara (matsubara)]

Moved the URL from a Librarian file to pastebin.
Is this exception recorded as an OOPS? How does the user get feedback?

[Alexander Sack (asac)]

maybe paste the actual xml that is invalid here? we probably want to carry that to upstream translation group if its a bug in the .xpi's imported.

[Jeroen T. Vermeulen (jtv)]

Diogo: no, this is not recorded as an oops, only as error output on error-reports. Our scripts don't use the oops infrastructure yet.

Alexander: we don't know, and this bug is probably not the best place for that. But if upstream has tools to validate this stuff, we could perhaps add a reference to that somewhere. We already do for gettext.

[Jeroen T. Vermeulen (jtv)]

It turns out this problem is caused only by parse errors in install.rdf, so we see it while trying to retrieve the last translator. Syntax errors in DTD aren't detected at all (bug 353664).

[Jeroen T. Vermeulen (jtv)]

Fixed in RF 8155