Gaia/System/Localization: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
== Reading == | == Reading == | ||
* dev-b2g | * dev-b2g: [http://groups.google.com/group/mozilla.dev.b2g/browse_thread/thread/841a0aef5f0a719f Gaia & Localization] | ||
* dev-webapi | * dev-webapi: [https://groups.google.com/d/topic/mozilla.dev.webapi/Pb6w22fTcnk/discussion document.mozL10n] | ||
== Questions == | == Questions == | ||
Revision as of 09:38, 2 April 2012
Status
- Stage: Development
- Release target: B2G Milestone 3 [Alpha], Q2 2012
Team
- UX: Patryk Adamczyk (IRC: patryk)
- UX: Josh Carpenter (IRC: jcarpenter)
- Dev: Fabien Cazenave (IRC: kaze)
- Eng: Vivien Nicolas (IRC: vingtetun)
- Eng: Zbigniew Braniecki (Github)
- Eng: Tim Dream (keyboard)
Reading
- dev-b2g: Gaia & Localization
- dev-webapi: document.mozL10n
Questions
- What functionality do we need to support in v1 (BusReq.)?
- In the centralized settings, ability to specify input (keyboard) language & system language
- 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)
- Flexible UI, partners should not need to adjust UI (much) if swapping fonts
UX Requirements
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