L10n:B2G/RTL: Difference between revisions

Jump to navigation Jump to search
Removed questions and comments that conflict with the spec, and linked to the spec instead.
(Corrected the incorrect link to the UX RTL spec. Added a note that pseudolocales are not a substitute for testing in Arabic: we've seen different layout issues in Arabic than we have with pseudolocales.)
(Removed questions and comments that conflict with the spec, and linked to the spec instead.)
Line 27: Line 27:
Last but not least, we're seeing a need in more bidi education for our UX designs.  This is particularly interesting in touch interfaces which rely on spatial metaphors and finger gestures, like swiping.   
Last but not least, we're seeing a need in more bidi education for our UX designs.  This is particularly interesting in touch interfaces which rely on spatial metaphors and finger gestures, like swiping.   
Bugs that go into this category should block the tracking bug and have <code>[rtl-design]</code> in their whiteboard: [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&list_id=9321813&o1=substring&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=rtl-design&v1=906270&product=Firefox%20OS bugzilla query].
Bugs that go into this category should block the tracking bug and have <code>[rtl-design]</code> in their whiteboard: [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&list_id=9321813&o1=substring&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=rtl-design&v1=906270&product=Firefox%20OS bugzilla query].
The sections below are not exhaustive or accurate in all cases, for all apps, for 2.2. Please do not rely on this wiki, but be sure to reference [https://mozilla.box.com/s/bcm3s5i2v6js5uk0ws3tsywse8bgncgo the 2.2 specification for Arabic support].


====Spatial metaphors====
====Spatial metaphors====
* indicating progress:
* Progress Indicators (see [https://mozilla.box.com/s/bcm3s5i2v6js5uk0ws3tsywse8bgncgo page 15 of the spec for complete behavior)]:
** in FTU the progress indicator slides towards the right edge of the screen,
** In FTU the progress indicator slides towards the right edge of the screen,
** in various places, the back button is on the left and the next button is on the right,
** For 2.2, the back button is ALWAYS on the left and the next button is on the right,
** in Haida, the history of navigation is represented as sheets on a LTR timeline,
** The history of navigation (Haida model) is represented as sheets on a LTR timeline, and does not change for 2.2.
** subpanels slide in from the right edge of the screen
** subpanels slide in from the right edge of the screen
* learn more, expand, start:
* learn more, expand, start:
Line 44: Line 46:


====Finger gestures====
====Finger gestures====
* swipe to dismiss notification currently only works from left to right
Most animations and gestures will not change for the 2.2 release.
* [x] and [<] to close should be consistently on one side;  right now it depends on the app
* Swipe to dismiss notification does not change for 2.2 and works LTR.
* scrollbars are on the left;  is this okay for using the right hand's thumb?
* [x] and [<] to close should be consistently on one side;  right now it depends on the app (as noted in the pattern)
** for instance, for RTL, Android places scrolling indicators on the left, but a quicklook index of each letter on the right for easy thumb access
* Scrollbar behavior is noted on [https://mozilla.box.com/s/bcm3s5i2v6js5uk0ws3tsywse8bgncgo page 16 of the 2.2 spec].
* currently the swipe to unlock is always to the right,
* Currently the swipe to unlock is always to the right, [https://mozilla.box.com/s/bcm3s5i2v6js5uk0ws3tsywse8bgncgo as noted on page 6 of the spec].
* checkbox state: off [o  ], on [  o] - should this change in RTL?
* Behavior for check boxes is [https://mozilla.box.com/s/bcm3s5i2v6js5uk0ws3tsywse8bgncgo described on pages 18 and 19 of the spec].


===Performance===
===Performance===
Confirmed users
208

edits

Navigation menu