From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Unwelcomed non-native language support
Date: Sat, 30 May 2015 11:32:18 +0200 [thread overview]
Message-ID: <20150530113218.1fb9a4cc@marcec> (raw)
In-Reply-To: <CA+t6X7f_pS2fnOx_tJ5VfLQM2qrXY6uq09xdaFDvsC5vZF9hWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
Am Sat, 30 May 2015 11:36:28 +0300
schrieb gevisz <gevisz@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
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-30 9:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 15:35 [gentoo-user] Unwelcomed non-native language support gevisz
2015-05-28 22:41 ` Volker Armin Hemmann
2015-05-29 0:07 ` Mike Gilbert
2015-05-29 4:35 ` Gevisz
2015-05-29 7:08 ` Volker Armin Hemmann
2015-05-29 16:34 ` gevisz
2015-05-29 17:34 ` Marc Joliet
2015-05-29 20:52 ` gevisz
2015-05-29 18:47 ` gevisz
2015-05-29 4:24 ` Gevisz
2015-05-29 14:46 ` Mick
2015-05-29 16:20 ` gevisz
2015-05-29 16:36 ` Mick
2015-05-29 18:45 ` gevisz
2015-05-29 20:33 ` gevisz
2015-05-30 8:36 ` gevisz
2015-05-30 9:32 ` Marc Joliet [this message]
2015-05-30 10:57 ` gevisz
2015-05-30 11:11 ` gevisz
2015-05-30 11:36 ` Marc Joliet
2015-05-30 12:02 ` gevisz
2015-05-30 13:56 ` gevisz
2015-05-30 15:56 ` rhannek
2015-05-30 19:14 ` gevisz
2015-05-30 15:54 ` Peter Humphrey
2015-05-30 19:09 ` gevisz
2015-05-31 8:48 ` Neil Bothwick
2015-05-31 10:59 ` Marc Joliet
2015-05-31 12:00 ` Neil Bothwick
2015-05-30 10:02 ` rhannek
2015-05-30 11:07 ` gevisz
2015-05-30 11:31 ` rhannek
2015-05-30 11:59 ` gevisz
2015-05-30 12:13 ` Marc Joliet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150530113218.1fb9a4cc@marcec \
--to=marcec@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox