From OLPC
This page is obsolete. The information has been merged into[1].
| A request has been made for this page to be deleted.
If you disagree with its deletion, please explain why on its talk page.
Before deleting verify that no links will break.
|
| WARNING:
The content of this section is considered
DEPRECATED and OBSOLETE
It is preserved for historical or documenting reasons.
|
| Stream
| 8.2, Any
|
| Category
| I18N
| Sub-category
| keyboard
|
| Component
| Keyboard
|
| Feature
| http://wiki.laptop.org/go/Tests/Keyboard_mappings
|
| Objective
| Ensure that a new release booted up on an Arabic keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen.
|
| Tools
| SKU7 keyboard
|
| Setup
| See link to feature
|
| Procedure
| See link to feature
|
Expected Results
and Pass Criteria
| The characters on the keyboard are properly represented after booting latest build.
|
| Comments
| warning.pngEmpty strings are not accepted.
|
| Release
| Stream
| Build
| Pass/Fail
| Trac Ticket(s)
| Comment(s)
| Date of Test
|
| Candidate
| 8.2
| 760
| Fail
| #8489
| The font for numbers is weird...the character fonts are fine. I don't know how to test Right-to-Left -- we really need some good details in this test case about how to ensure the compose characters are working; when to expect RTL and LTR; what fonts are supposed to be used, etc.
| warning.pngThe date "" was not understood (support for dates is still experimental).
|
| Candidate
| 8.2
| 767
| Fail
|
| the characters looked pretty good in a search bar or in terminal, but when you use the arabic font in write it just looks like defragmented latin characters. Also, the letter B's arabic counterpart shows up incorrectly as well as the G's arabic counterpart. In terminal the difference between the 2 and 3 arabic counterparts are indistinguishable.
| warning.pngThe date "" was not understood (support for dates is still experimental).
|
Facts about Tests/I18N/keyboards/ArabicRDF feed
| Build number | 760 +, and 767 + | | Build stream | 8.2 +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , and Any +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride | | Comments | The font for numbers is weird...the charac … The font for numbers is weird...the character fonts are fine. I don't know how to test Right-to-Left -- we really need some good details in this test case about how to ensure the compose characters are working; when to expect RTL and LTR; what fonts are supposed to be used, etc. ; what fonts are supposed to be used, etc., and the characters looked pretty good in a sea … the characters looked pretty good in a search bar or in terminal, but when you use the arabic font in write it just looks like defragmented latin characters. Also, the letter B's arabic counterpart shows up incorrectly as well as the G's arabic counterpart. In terminal the difference between the 2 and 3 arabic counterparts are indistinguishable. arabic counterparts are indistinguishable. | | Created | warning.pngThe date "" was not understood (support for dates is still experimental). | | More notes | warning.pngEmpty strings are not accepted. | | Pass criteria | The characters on the keyboard are properly represented after booting latest build. | | PassFail | Fail + | | Short name | Keyboard test for Arabic + | | Software release | Candidate + | | System component | Keyboard + | | System feature | http://wiki.laptop.org/go/Tests/Keyboard_mappings + | | Test category | I18N + | | Test objective | Ensure that a new release booted up on an Arabic keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen. + | | Test procedure | See link to feature | | Test setup | See link to feature | | Test subcategory | keyboard + | | Test tools | SKU7 keyboard + | | Trac bug number | 8,489 +info.pngTrac ticket |
|
