GNOME Bugzilla – Bug 113277
gtkmozembed prompts create localization problems
Last modified: 2009-09-10 22:34:35 UTC
so according to menthos, the fact that we can't localize dialogs in gnome cvs really sucks since moz translations tend to be pretty poor. Teuf suggested using a strcmp hack on dialogs. I'm not sure of the effort involved, but afaict there are really only two dialogs that ever popup on me when using epiphany, so maybe its worth it.
The proper solution is of course for Mozilla to expose some sort of dialog identifier, to allow embedding applications to substitute their own dialogs. See meta bug http://bugzilla.mozilla.org/show_bug.cgi?id=65233 for such discussions. It's marked as RESOLVED now though, perhaps someone can take a look at how they did it. If that solution isn't adequate, I'm all for a temporary strcmp solution, even if it's a scary type of hack in all sorts of ways.
I dont think that bug is related ... About the strcmp hack ... the main problem is the conflict with translated versions of mozilla ihmo.
What prompts etc. from mozilla do we still use? Is this bug effectively fixed once the rest of the certs stuff is added?
The "Submit data over insecure link", and the cookie dialogue come from mozilla I think.
CHPE don't we disable those by default?
All the alerts created by mozilla have this problem. It doesnt matter if they are gtk or not.
marco my point was that we disable most moz dialogs anyway right?
Well the connection failed one is an example of one we dont suppress.
Mass reassigning of Epiphany bugs to epiphany-maint@b.g.o
*** Bug 153293 has been marked as a duplicate of this bug. ***
Depends on http://bugzilla.mozilla.org/show_bug.cgi?id=228207 .
*** Bug 413566 has been marked as a duplicate of this bug. ***
This problem has gotten worse with Gecko >= 1.8 since the mozilla translations aren't picked up at all any more.
*** Bug 541196 has been marked as a duplicate of this bug. ***
OBSOLETE now that we don't have a mozilla backend anymore.
*** Bug 578071 has been marked as a duplicate of this bug. ***
*** Bug 594781 has been marked as a duplicate of this bug. ***