On 21.01.13 16:46, Toni Hermoso Pulido wrote:
Al 21/01/13 16:37, En/na Axel Hecht ha escrit:
On 21.01.13 16:25, Toni Hermoso Pulido wrote:
Al 21/01/13 15:28, En/na Gervase Markham ha escrit:
On 20/01/13 00:11, Pascal Finette | Mozilla wrote:
Thank you for taking the time to explain - makes perfect sense and I
believe I get it now. So this seems to be (at least partly) a
question of:
In which countries will FxOS phones ship and making sure we support all
languages in those countries?
As we all know, Boot2Gecko is open source. And the phones are not being
shipped by Mozilla. Therefore (to my understanding; I could be wrong)
the only way Mozilla can influence exactly what software the OEMs ship
and how they configure it is via our agreement with them which lets them
use the Firefox logo and Firefox OS name.
So are you (Toni/Ruben) saying that we should make some locale-related
provision a condition of this agreement? If so, what do you think it
should be?
* the OEM agrees to ship all available signed-off-by-Mozilla locales?
* the OEM agrees to ship all locales which are official languages of
the country or territory in which they ship?
* something else?
Hello,
* the user should have easy means to enable all Mozilla Gaia locales
(https://github.com/mozilla-b2g/gaia/blob/master/locales/languages_all.json)
by default (even if not a complete or signed-off translation were
available for some of them yet). Even better, that list should be:
http://hg.mozilla.org/mozilla-central/file/tip/toolkit/locales/en-US/chrome/global/languageNames.properties
(as people can currentlty select in Desktop Firefox)
* Moreover, I think they also should provide all signed-off available
translations of the Gaia environment they are using —especially for
shared components—.
I think that would be enough and, if agreed, we would not need to enter
into region per region discussion.
Best,
Can you detail on what you mean by "enable"?
Hi,
When I mean enable, I mean that the user can assign the value of the
locale (e.g. 'de') to:
https://developer.mozilla.org/en-US/docs/DOM/window.navigator.language
and, therefore, HTTP Header Accept-Language, for instance:
http://hg.mozilla.org/releases/l10n/mozilla-aurora/de/file/tip/toolkit/chrome/global/intl.properties
(intl.accept_languages)
I'm afraid that's not technically feasible in a reasonable time frame.
The current technical limitations are:
- one language is the preferred language, exposed as navigator.language
and the first entry in the http accept-language header.
- that language is part of a finite list of languages that are packaged
into the bits we ship on the phone.
- that language is used in the "UI".
Everything else are fine comments, but for mozilla.dev.b2g much rather
than for .governance.
I'm not sure that we should postpone the discussion about what languages
a Firefox-branded phone should have until a redesigned l10n system is
designed, implemented, and on a branch that's ready to ship on phones.
The questions that I have in my mind would be:
- what happens if an external partner comes in and wants some particular
localization, that we don't have yet.
- what happens if we have a localization that we assume would be good to
include, but an external partner disagrees with that suggestion
- what happens if a external partner disagrees with the contents of an
existing localization?
All within the context of a Firefox-branded phone, that is.
Axel
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
