maemo.org Bugzilla – Bug 1706
fr-FR and es_ES undefined entity proxyResolveFailure.longDesc / Invalid syntax error when connection is lost
Last modified: 2007-11-28 13:10:13 UTC
You need to
before you can comment on or make changes to this bug.
When wifi connection goes down sometimes, browser displays the following error
Numéro de ligne 147, Colonne 42 : <div
Locale used on n800 is french
eww, can you change your locale to en-US and en-GB and determine if it happens
there? I'll research this Monday.
I found an easier way to reproduce the problem :
ensure DNS resolution is always failing on your wifi access point (for
instance, unplug ethernet connection on it and disable DNS cache if present)
and try to access any website. Once DNS lookup fails, you'll get the error.
I've tested with en_US and en_UK and error isn't present but I'm also seeing it
with es_ES, so I think the problem is in the various translation ressources
(good luck with that ;) or that they aren't packaged correctly.
You should check all translations shipped with n800 (but I probably don't need
to tell you that :)
yeah, thanks for testing an extra. I'm assuming you were using fr-FR and not
fr-CA. Yes, I will make sure to test them all. Thankfully it's not too hard to
test them, unfortunately we clearly didn't. This beta didn't have a
localization testing phase (as you can see).
thanks. finally tracked this down, the problem is in
<!ENTITY proxyResolveFailure.longDesc "<p>Serveur proxy
introuvable.</p><ul><li>Vérifiez les paramètres et réessayez.</li><li>Vérifiez
que la connexion réseau est activée.<</li><li>Consultez l'administrateur réseau
ou le fournisseur d'accès Internet si le problème persiste.</li></ul>">
Note the doubled <<. It's actually bad in en-GB and en-US too, but we're not
using the correct set for those languages so English speakers get working
strings from mozilla.org :o.
walked over to the localizers yesterday and politely requested that they
address it now :).
temporary workaround (an updated localization package is scheduled for next
week, but we're releasing sooner...)
confirmed as fixed with latest update.
for reference, we got replacement bad localizations for 4.0, so while this
specific bug is fixed, people are expected to have dozens of complaints about
what's actually in 4.0 (please don't reopen this bug, just find newer bugs or
file them if you can't -- I'll try to file most of them first).
Closing. Resolution has been verified.