|Line 138:||Line 138:|
| [[User:rfujita|Ryo ]]
Revision as of 07:55, 14 May 2009
What to test?
Today's installment of Fedora Test Day will focus on:
- Features/IBus input methods
IBus is the new input method framework for Asian languages being used in F11.
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - User:Petersen, User:Tagoh, User:Phuang, User:dchen, WarrenTogami
- Quality Assurance - Liam Li,
Prerequisites for Testing
- Please test with either Rawhide (with latest ibus packages installed) or a current Fedora Desktop Live image in a real or virtual machine.
- A native keyboard for your country/region if you have one
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide.
Note ibus is installed by default in F11 but if you should have upgraded from F10 you will need to "yum install @input-methods". At the very least you need to be running the latest ibus, which is ibus-184.108.40.20690417-1.fc11 at the time of writing: eg with F11-Preview.
Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
How to test?
Testing iBus usage to input native languages:
- Login to desktop in your native language or the one you wish to test.
- QA:Testcase_imsettings_enable (if your desktop is in an Asian language you may be able to skip this step since ibus should be enabled by default for most Asian language)
- Run im-chooser to turn on iBus if it is not enabled by default in your language
- ibus can be activated in an application from the ibus icon in the panel notification area and choosing the desired input method there. If you desktop language does not use a input method normally you may need to add the input method with ibus-setup too.
- Test iBus correctness by inputting in various applications and desktop environments (such as GNOME and KDE) listed in below table. Tests with other applications and other environment are also welcome. Please note that at least one input method should be installed and enabled to performed the test.
Test Cases and Results
|User||Keyboard||Desktop||Desktop Language||Startup activation||Input method||Application:Result||Comments|
|Explanation: User:Example||Country or code (de, fr, gb, us, jp, kr, etc)||GNOME, KDE, XFCE, LXDE, etc||Language or locale (de, en, fr, hi, ja, ko, zh, etc)||PASS/FAIL - Input method system started and running ok?||Name of language or engine (anthy, chewing, hangul, pinyin, rawcode, sayura, table)||PASS/FAIL (gedit, firefox, openoffice, pidgin, kate, eclipse, etc)||Details of any problems [bug#] or suggestions|
|User:Petersen||US||GNOME||Japanese (ja)||PASS||Japanese(anthy) PASS||PASS (gedit, firefox)|
|User:Mso||CZ, but using en_US locale||GNOME||Japanese (ja)||PASS with unwanted side-effects when compositing turned on||Japanese(anthy) PASS||PASS (gedit, epiphany, midori, gnome-terminal, gajim, stardict, fantasdict, evolution, rhythmbox, totem, gnumeric, subtitleeditor), PASS with hickups (inkscape, abiword)||PASS with hickups means the typed text does not appear at the cursor position until final output is selected (it does appear in a separate toolbox though), considering how it works in other cases though, this might be actually correct/expected behaviour; odities with turning on/off filled as rhbz #500731|
|User:Jassy||US||GNOME||Punjabi (pa)||PASS||Punjabi FAIL||PASS (gedit, firefox)||When trying to type, Punjabi keymaps should be enabled default, which is not the case. In KDE punjabi input is not working (Tried with kate and kwrite).|
|Runa Bhattacharjee||US||GNOME||Bengali India (bn_IN)||PASS||PASS (comments in the last field)||PASS (gedit, kwrite, oowriter, xchat, firefox)||Test 2: The ibus service was enabled but the keymaps were not added or any default keymap linked for the locale. The steps for Test 2 indicate the manual addition of the keymaps as a feature. Automatic addition of the keymaps and activating a designated default map amongst them, when logging in a particular language would be of benefit. Additionally, it would be a seamless migration for users habituated to using a similar approach with scim in earlier Fedora versions. Apologies in advance if this is not the case and my test environment was the culprit.|
|Sweta Kothari||US||GNOME||Gujarati (gu-IN)||PASS||Gujarati FAIL||PASS (gedit, kwrite, lokalize, firefox)||changing the Gujarati local after when trying to type something, Gujarati keymaps should be enabled bydefault but it is not working in this case. Rest of all are working fine.|
|Liam Li||US||GNOME||Chinese (zh_CN)||PASS||Chinese(PinYin) PASS||PASS with terminal/stardic/firefox/openoffice/gedit/vi/thunderbird/xchat. AbiWord failed,it seems AbiWord doesn't support Chinese.||#500760 #500762 #500763|
|Ryo Fujita||US||GNOME||Japanese (ja)||PASS||Japanse PASS||PASS (firefox, evolution), FAIL (abiword)||In abiword, a hiragana character 'no' is settled on a kanji character 'ton', unicode 5678, UTF8 E5 99 B8|