Fennec/Features/langchoice

< Fennec‎ | Features
Revision as of 16:39, 29 April 2011 by Mbrubeck (talk | contribs)
Feature Status ETA Owner
L10N: Better first-run experience / language choice Concept 2011-07-01 Thomas Arend

Summary

Goal: reduce amount of locales packaged into apk & create better first-run experience for non-English native speakers for starting up Fennec in their language

We create language XPIs for many more languages than we ship in the multi-locale build. It's hard for users to find and install these locales. Putting our language XPIs on AMO, with a proper landing page, would be a big help. It would also be used as the foundation to the improved language firstrun experience. Perhaps the AMO landing page could _be_ the firstrun experience if the OS locale is not the current Firefox locale.

Team

  • UX: Brian Dils

Release Requirements

Summary of our most recent discussion

Next Steps

Summary of our most recent discussion

Open Issues

Pike's list:

  • Are there existing language packs on AMO? The list doesn't show any, but as far as Pike knows, that's only blessed ones.
  • Who'd be the "owner" of language packs? Mostly a question of attribution vs permissions.

And with respect to http://etherpad.mozilla.com:9000/VLDiPkfl8p :

  • Right now,restartless add-ons exclude modifications to the chrome registry. No idea how far folks are in fixing that. Need :bs, mossop?
  • Where do we get thelocalized UI buttons and language names from for the startpage UI? Both from localizers to us, and from us to the browser. How does this differ for langpacks we build and langpacks contributed by outside community?
  • How do we localize default bookmarks? Probably involves timing of language selection/installation and profile initialization, and/or a feature request on places.

Related Bugs & Dependencies

  • Infrastructure
    • bug 634679 - Language pack add-ons installed on nightly builds must remain compatible
  • Design

Designs

Mobile/Projects/Firstrun language choice

Test Plans

Goals/Use Cases

Non-Goals

Other Documentation

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked.
  At Risk: feature is at risk of missing its targeted release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.