GNOME Bugzilla – Bug 433377
Epiphany-extensions don't use localised strings.
Last modified: 2007-04-25 20:49:07 UTC
Arabic has a complete translation for both epiphany and epiphany extensions. When starting epiphany with the Arabic locale, the interface is in Arabic, but the extensions still use the original English text. This behaviour does not happen in the extension list itself. Steps to reproduce: Install epiphany and epiphany-extensions. Enable the "page information" extension. Install the arabic language packs. LANGUAGE=ar epiphany Start epiphany and go to View (third option from the left), and see "Page Information" in english. The same thing happens for Spanish and French. ----- I suspect the reason is because the extensions don't use the epiphany-extensions textdomain when incorporated into the browser. This really should be fixed if it is not that hard because translators keep working on epiphany extensions translations. http://l10n.gnome.org/module/epiphany-extensions
dgettext(GETTEXT_PACKAGE, "string") can be used for C/C++ files. I haven't test it yet. I'd write a patch if I knew how to specify the textdomain in .glade files.
It works here; the page info extension is translated. Can you use strace to find out where it's trying to locate the .mo files, and if they exist in the right place on your system?
You're right - It is a problem with ubuntu's language packs. https://bugs.launchpad.net/langpack-o-matic/+bug/110030