Reporting broken sites with langpacks

Cuipo

unread,

Nov 14, 2007, 10:03:28 PM11/14/07

to

When I try reporting a broken site with my fur-it langpack, the result
is similar to that of trying to update Firefox: a button appears in my
taskbar but no window shows up. Is this all part of the same problem,
the langpack not being recognized at headquarters?

Thanks,

Cuipo

Michael Wolf

unread,

Nov 15, 2007, 4:15:57 PM11/15/07

to

Cuipo napisa:

What Firefox version your language pack for?

Axel Hecht

unread,

Nov 15, 2007, 5:42:24 PM11/15/07

to

Could you try this with http logging on?
http://www.mozilla.org/projects/netlib/http/http-debugging.html.

The software update bug should have been something different, and that's
fixed by now on the 2.0.0.x.

Btw, I just tried on a 2.0.0.9 with the Furlan langpack, works like
charm for me.

http://reporter.mozilla.org/app/report/?report_id=RMO11951658394122&submit_reportID=Lookup+Report
is the report I did.

Axel

Cuipo

unread,

Nov 18, 2007, 10:17:32 PM11/18/07

to

Axel Hecht wrote:
> Cuipo wrote:
>> When I try reporting a broken site with my fur-it langpack, the result
>> is similar to that of trying to update Firefox: a button appears in my
>> taskbar but no window shows up. Is this all part of the same problem,
>> the langpack not being recognized at headquarters?
>

> ...Btw, I just tried on a 2.0.0.9 with the Furlan langpack, works like
> charm for me.

I'd been using an updated langpack that hasn't yet been uploaded to AMO.
Now I just tried the AMO version, and it works fine. So the problem
is with the new version. Would appearing on AMO affect a langpack's
ability to report broken websites, or should I be looking for an error
in the provisional langpack? (The provisional langpack can be found at
http://www3.sympatico.ca/rpontisso/FirefoxFurlan2.0.0.4.xpi)

I tried the provisional langpack on a SunOS machine, with the same problem.

> Could you try this with http logging on?
> http://www.mozilla.org/projects/netlib/http/http-debugging.html.

Ok, done. But I have no idea how to interpret the results.

Thanks for your help.

Cuipo

Axel Hecht

unread,

Nov 19, 2007, 5:41:35 AM11/19/07

to

If you have them in a file, attach them here? You should probably do a
really short session, about:blank as homepage, with only your language
pack as activated add-on. Check updates, and exit. That way the log is
nice and small, and you don't leak all your private data into the world.
I'd still review the log for any data you don't want to share, though.

Axel

Michael Wolf

unread,

Nov 19, 2007, 5:55:59 AM11/19/07

to

Cuipo napisa:

> I'd been using an updated langpack that hasn't yet been uploaded to AMO.
> Now I just tried the AMO version, and it works fine. So the problem is
> with the new version. Would appearing on AMO affect a langpack's
> ability to report broken websites, or should I be looking for an error
> in the provisional langpack? (The provisional langpack can be found at
> http://www3.sympatico.ca/rpontisso/FirefoxFurlan2.0.0.4.xpi)
>
> I tried the provisional langpack on a SunOS machine, with the same problem.

Hi Cuipo,

I found the error. I was looking for it a long time until I had the idea
to use the Error Console. And there I saw that the error is not in the
reporter folder itself but in the file /locale/global/wizard.dtd. There
is an entity "button-back-win.accesskey" which has the value "&". This
character is not allowed because it is a reserved character for mark-up.
The previous version has another character, an allowed one, for this
entity. Therfore that one is working.

Cuipo

unread,

Nov 19, 2007, 5:08:28 PM11/19/07

to

Ah, thank you, Michael. It was the pesky ampersand. No idea how that
got there. While I was in the file I noticed some other
less-than-desirable access keys, too. Everything's fine now.

Thanks again.