Am Sat, 30 May 2015 11:36:28 +0300 schrieb gevisz <gev...@gmail.com>:
[...] > As I still had a suspicion that those non-Eglish entries in the Firefox > menu remain because of some cash issues, I have just launched another > instance of the Firefox browser using a separate profile. > > Well, in a separate profile, the Firefox menu is in English while > in the default profile it is in a non-English language. > > So, it could be a cash issue: I have unmerged the gettext while > running Firefox and so its substitutions could be left somewhere > in cash... > > P.S. As I have already described it earlier, this issue with the Firefox > menu is only related to the menu I get while right-clicking on > a youtube video in Firefox. (All the other menus is in English, > as desired.) (Note: the word you are looking for is "cache".) I strongly suspect that the application doing the translating doesn't even use gettext. Besides which, I'm surprised you're not getting crashes from applications not finding the gettext libraries, which points to them not actually using it. You can use "emerge --depclean -pv gettext" to determine which do. In my case, firefox does *not* show up, despite me using nls (neither does adobe-flash, in case you're using that). (I also thought that maybe firefox bundles gettext, but the only references I could find on developer.mozilla.org pertain to localising websites with php and the like, and not to firefox-internal technologies.) So it seems to me that gettext is a false lead and that the root of your problem lies somewhere else. This document shows how websites can localise their content: https://developer.mozilla.org/en-US/docs/Web_Localizability/Creating_localizable_web_applications. -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
pgpi3ljYn6ySl.pgp
Description: Digitale Signatur von OpenPGP
