Revision as of 14:37, 28 March 2012

Status

Stage: Development
Are there B2G dependencies?
What functionality do we need to support in v1 (BusReq.)?
What languages do we need to support in v1 (BusReq.)?
- Fabien: We are building in support for all the language possibilities, but its up to the individual carrier to implement the languages and adjust the UI to fit. (March 22)
How is support implemented? eg: l10n, l20n?
Where is support manifested in UX? eg: keyboard, Settings, automatic translation, etc?

Last updated: Mar 28, 2012 (Patryk Adamczyk)

Support for multiple language display and input.
design considerations:

UTF-8/Unicode encoding support throughout B2G
String and phrases that could appear to the users including status bars, dialogue boxes, button text, alerts
Localized imagery and any images containing text
Layout - support for RTL languages eg. arabic
Date, currency, numeric formats
Fonts packages for each language
Flexible UI, partners should not need to adjust UI (much) if swapping fonts

Complete technical survey (read: http://groups.google.com/group/mozilla.dev.b2g/browse_thread/thread/841a0aef5f0a719f)
Complete "current implementation" survey
Clarify business requirements
Research UX precedents
Define UX requirements
Compare against current implementations

@@ Line 14: / Line 14: @@
 * UX: Patryk Adamczyk (IRC: patryk)
+* UX: Josh Carpenter (IRC: jcarpenter)
 * Dev: Fabien
 * Eng: Vivien