From Fedora Project Wiki

m (Wiki cleanup)
Line 148: Line 148:
| Japanese PASS
| Japanese PASS
| PASS (firefox, evolution)
| PASS (firefox, evolution)
FAIL (abiword) <ref> In abiword, a hiragana character 'no' is settled on a kanji character 'ton', unicode 5678, UTF8 E5 99 B8 </ref>
FAIL (abiword) <ref> In abiword, a hiragana character 'no' is settled on a kanji character 'ton', unicode 5678, UTF8 E5 99 B8. (added 15th. May) It's not a IBus issue. AbiWord has a bug.</ref>
| <references/>
| <references/>

Revision as of 01:54, 15 May 2009

2009-05-14 all day #fedora-qa)

What to test?

Today's installment of Fedora Test Day will focus on:

IBus is the new input method framework for Asian languages being used in F11.

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

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- at the time of writing: eg with F11-Preview.

Live Image

Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture MD5SUM
i386 ce576738ef1ea7bda2accc20bb374eb5
x86_64 0920091e080839847da9349a08d55df7

Latest syslinux package?
Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows liveusb-creator. Users of F10 and below can upgrade to the latest syslinux package using
yum --enablerepo=rawhide update syslinux

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
  • QA:Testcase_ibus_start
    • 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.
  • QA:Testcase_ibus_input
    • 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 US GNOME English (en_US) 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)

WARN (inkscape, abiword) [1] [2]

  1. 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;
  2. odities with turning on/off filled as 500731
User:Jassy US GNOME Punjabi (pa) PASS Punjabi FAIL [1] PASS (gedit, firefox)
  1. 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 FAIL [1] PASS (gedit, kwrite, oowriter, xchat, firefox, lokalize)
  1. 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 [1] PASS (gedit, kwrite, lokalize, firefox)
  1. 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 (terminal, stardic, firefox, openoffice, gedit, vi, thunderbird, xchat)

FAIL (AbiWord) [1] [2] [3] [4]

  1. it seems AbiWord doesn't support Chinese.
  2. 500760
  3. 500762
  4. 500763
Ryo Fujita US GNOME Japanese (ja) PASS Japanese PASS PASS (firefox, evolution)

FAIL (abiword) [1]

  1. In abiword, a hiragana character 'no' is settled on a kanji character 'ton', unicode 5678, UTF8 E5 99 B8. (added 15th. May) It's not a IBus issue. AbiWord has a bug.
User:Tagoh JP GNOME Japanese (ja) PASS Japanese(anthy) PASS PASS (gedit, evolution, firefox, pidgin)
Rajesh US GNOME Hindi (hi-IN) PASS Hindi FAIL [1] PASS (gedit, kwrite, lokalize, firefox, openoffice)
  1. changing the Hindi local after when trying to type something, Hindi keymaps should be enabled bydefault but it is not working in this case. Recently selected keymap type is loaded by default always. It should be what I have chosen as a preference as my keymap.
Rajesh US GNOME Maithili (mai-IN) PASS Maithili FAIL [1] PASS (gedit,firefox, openoffice)

FAIL (kwrite, lokalize) [2]

  1. changing the Maithili local after when trying to type something, Maithili keymaps should be enabled bydefault but it is not working in this case.
  2. FIXME - add bug(s) here
Amitakhya Phukan US GNOME Assamese (as-IN) PASS Assamese PASS [1] PASS (gedit,firefox, openoffice, kwrite, lokalize)
  1. For Assamese, after logging in to the GNOME Desktop, IBUS was enabled by default. I had to choose the Assamese keyboard layouts manually, but once selected, it was convenient to use.
  • The short cut keys for changing the input methods are different from SCIM. Typing in applications like gedit, FireFox, OpenOffice, kate and lokalize are working fine.
Shankar Prasad US GNOME Kannada (kn-IN) PASS PASS Kannada PASS (gedit,firefox, openoffice, kwrite, lokalize) Test 2:
  1. Automatic addition of the keymaps and activating a default keymap would be good for any user.
  2. There is some ambiguity in the steps of test case
  3. Unless we click on any editor, the ibus won't get activated and left clicking on the icon will lead to nothing
Sandeep Shedmake US GNOME Marathi (mr_IN) PASS FAIL for Marathi [1] PASS (gedit, kwrite, oowriter, firefox, lokalize)
  1. Having logged-in with Marathi language resources, ibus service gets enabled but keymaps aren't added by default (hence, added manually). Above tests were done for ibus-
Krishnababu K US GNOME Telugu (te_IN) PASS Telugu FAIL [1] PASS (gedit, kwrite, oowriter, firefox, lokalize)
  1. Test Case 2: After logging into GNOME session by Telugu language support, input method ibus has been enabled by default. But Telugu key maps were not enabled by default, so i added them manually. (They have to be added and enabled by default according to the test case 2). I had perform these test cases on ibus-
Ani Peter US GNOME Malayalam (ml_IN) PASS FAIL [1] PASS (gedit, kwrite, oowriter, firefox, lokalize) [2]
  1. Test case 2, the results fails. ie, As per instructions in steps 2,3 & 4, the left click does not list any keymaps added in the "Input Method" page. Instead, if we place cursor in any text input area, the keymaps we have added manually are displayed on left click.
  2. My observations in Test Case 3: Selected keymaps in the order Inscript and Swanalekha, opened Gedit and enabled Ibus. Since the order of keymaps selected is last added first, Swanalekha appeared as default keymap when Ibus was enabled. Swanalekha does not have an icon, hence the default icon for Ibus appeared initially and once started input, the name "swanalekha" appeared in the Ibus tab. Switching to the second keymap and input using all keymaps worked fine in gedit, kwrite, lokalize and oowriter.