Canmove, confirm, emeritus
6,906
edits
Changes
m
{| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| [[Fennec/Features/langchoice|L10N: Better first-run experience / language choice]]
| {{StatusHealthy|status=Development in progress; basic functionality landed}}
| 2011-07-01
| Thomas Arend
<section end="status" />
|}
== 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<br> ==
* '''UX:''' Brian Dils
* '''QA:''' Aaron Train
== Release Requirements ==
[http://etherpad.mozilla.com:9000/VLDiPkfl8p Summary of our most recent discussion]
== Next Steps ==
[http://etherpad.mozilla.com:9000/VLDiPkfl8p Summary of our most recent discussion]
Finkle is working on a proof of concept restartless add-on. We can use an AMO API to retrieve locales. The add-on is using Brian's design as a guide for the selection UI.
== Open Issues ==
Pike's list:
*Are there '''existing language packs on AMO'''? [https://addons.mozilla.org/en-US/mobile/language-tools/ 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 http://etherpad.mozilla.com:9000/VLDiPkfl8p] :<br>
*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 the'''localized 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.<br>
== Related Bugs & Dependencies ==
* Infrastructure
** {{bug|634679}} - Language pack add-ons installed on nightly builds must remain compatible
* Design
** <s>{{bug|653141}}</s> (FIXED) - allow language choice on first-run
** {{bug|658278}} - revise language pref UI to match new system
== Designs ==
[[Mobile/Projects/Firstrun language choice]]
== Test Plans ==
[https://wiki.mozilla.org/Fennec/Features/langchoice/TestPlan QA Test Plan]
== Goals/Use Cases ==
== Non-Goals ==
== Other Documentation ==
== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status= }}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status= }}
| Blocked: feature is currently blocked.
|-
| {{StatusAtRisk|status= }}
| 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.
|}
__NOTOC__
[[Category:Features]] [[Category:Mobile]] [[Category:Firefox]] [[Category:L10N]] [[Category:Priority_1]] [[Category:UX]]
clearing in prep for migration to new feature page format
