Al 19/01/13 17:59, En/na Pascal Finette | Mozilla ha escrit: > Hi, > > The builds shipped with the phones are the ones with fewer locales, >> which is the main concern for localizers. And also my main concern to >> discuss here if this is something OEMs are asking us to do and if so, why. > > > I am not 100% sure I understand the specific concern around Telco's > shipping (only) a specific set of locales tailored to the market they sell > the phone in. As this is a piece of hardware which is tied to a Telco and > sold only in one market - why would you want to have all possible languages > on the phone? If, say a Telco would sell the phone in Russia > (hypothetically), that particular phone would only be sold and used in > Russia (as it's tied to the specific Telco). You would want to have all > languages on the phone which are relevant to that market (plus probably a > set of "global" languages such as English, Spanish, etc) - but why would it > matter that you have Scottish Gaelic on the phone? > > I would love to understand that concern better. >
Hello all, first of all, thanks to Nukeador for bringing the issue here. Let me help you to understand a bit the concerns from a point of view of a speaker of a minorised (not necessarily minor) language. As example of what Ruben explains, I can tell you about what happened a few months ago with some Android-shipped Samsung devices in Spain. Even Android was localised in Catalan for long enough, the company didn't ship it in that language in the Spain market for whatsoever reason (http://www.324.cat/noticia/1665832/ciencia/Samsung-Espanya-veta-el-catala-als-mobils) After that, there was a public outcry and, AFAIK, new Samsung devices are currently shipped in Catalan. However, I'm not sure if other potential languages (in the Spanish market) were lucky enough to be included as well. Focusing on Mozilla, assuming that there is a partnership involved —ergo, Firefox brand and logos are used—, can we know whether a FirefoOS phone to be shipped in UK will include Scottish Gaelic? And, let's say, the same for Ligurian in Italy? I can understand that some telcos or third parties may not have 'resources'/will to translate their own extra/custom apps in these languages, but I think there should be an easy way that interested users might enable these locales (and ideally also have their localised vanilla apps). Third parties might always offer a disclaimer of not having a fully localised experience for some locales but, at least, I think they should not block/remove them. Allowing these locales to be enabled, you are also facilitating that a webapp ecosystem considering these languages can exist. >From a localiser point of view, I would love to have a clearer idea of the real product expectations for the different involved locales. As you can understand, telling our voluntary localisers that their contributions might end up being only accessible to a super-reduced geeky public does not help to motivate them. Best, -- Toni Hermoso Pulido http://www.cau.cat _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
