From: eoli3n <eoli3n@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: firefox-i18n-fr installed, firefox still in english
Date: Sun, 20 Dec 2020 12:36:45 +0100 [thread overview]
Message-ID: <20201220113645.cu0-QqqIrwzRqoLd5R57FIXGWbqFlTYeyouOnIXjPF8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27255@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
New comment by eoli3n on void-packages repository
https://github.com/void-linux/void-packages/issues/27255#issuecomment-748595035
Comment:
From https://firefox-source-docs.mozilla.org/intl/locale.html#requested-locales
> After the sanitization, the value will be stored in a pref intl.locale.requested.
> [...]
> - If the pref is not set at all, Gecko will use the default locale as the requested one.
It seems that PKGBUILD does this as shown in my previous comment.
Void package fallback to [default locale](https://firefox-source-docs.mozilla.org/intl/locale.html#default-locale) (?) because no ``intl.locale.requested`` is set.
We can also read:
> If the developer wants to programmatically request the app to follow OS locales, they can assign null to requestedLocales.
next prev parent reply other threads:[~2020-12-20 11:36 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 13:29 [ISSUE] " eoli3n
2020-12-19 17:18 ` loreb
2020-12-19 17:36 ` ericonr
2020-12-19 19:16 ` Chocimier
2020-12-20 0:43 ` ericonr
2020-12-20 3:20 ` travankor
2020-12-20 9:15 ` eoli3n
2020-12-20 9:16 ` eoli3n
2020-12-20 9:23 ` eoli3n
2020-12-20 9:23 ` eoli3n
2020-12-20 9:23 ` eoli3n
2020-12-20 9:27 ` eoli3n
2020-12-20 11:27 ` eoli3n
2020-12-20 11:28 ` eoli3n
2020-12-20 11:34 ` eoli3n
2020-12-20 11:35 ` eoli3n
2020-12-20 11:36 ` eoli3n [this message]
2020-12-20 11:38 ` eoli3n
2020-12-20 11:55 ` eoli3n
2020-12-21 11:12 ` eoli3n
2020-12-21 12:05 ` eoli3n
2020-12-21 13:57 ` Anachron
2020-12-21 14:11 ` eoli3n
2020-12-22 20:25 ` Chocimier
2020-12-22 20:27 ` ericonr
2020-12-22 20:31 ` eoli3n
2020-12-22 20:34 ` Chocimier
2020-12-27 11:14 ` mvf
2021-01-06 22:43 ` ericonr
2021-01-06 22:57 ` pullmoll
2021-01-18 21:21 ` Chocimier
2021-01-18 21:29 ` jnbr
2021-01-21 15:09 ` [ISSUE] [CLOSED] " ericonr
2021-12-08 21:19 ` eoli3n
2021-12-09 19:27 ` artenaki
2021-12-09 19:48 ` Anachron
2021-12-10 18:18 ` Chocimier
2021-12-10 19:27 ` Anachron
2021-12-17 20:03 ` eoli3n
2021-12-18 7:17 ` Anachron
2021-12-18 9:30 ` eoli3n
2022-01-19 7:25 ` eoli3n
2022-01-22 5:38 ` ericonr
2022-01-22 5:38 ` ericonr
2022-01-22 9:33 ` eoli3n
2022-01-22 14:00 ` ericonr
2022-01-23 17:36 ` Duncaen
2022-01-23 18:22 ` eoli3n
2022-02-11 14:50 ` eoli3n
2022-02-11 16:54 ` Chocimier
2022-02-11 20:05 ` eoli3n
2022-05-13 2:15 ` github-actions
2022-05-13 10:06 ` eoli3n
2022-05-13 14:19 ` Chocimier
2022-05-13 17:32 ` eoli3n
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=20201220113645.cu0-QqqIrwzRqoLd5R57FIXGWbqFlTYeyouOnIXjPF8@z \
--to=eoli3n@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).