From Fedora Project Wiki

Line 56: Line 56:
| anthy, chewing, hangul, pinyin, rawcode, table?
| anthy, chewing, hangul, pinyin, rawcode, table?
| de, fr, gb, us, jp, kr, etc?
| de, fr, gb, us, jp, kr, etc?
| gedit, firefox, openoffice, pidgin, kate, etc?
| gedit, firefox, openoffice, pidgin, kate, eclipse, etc?
| OK or FAIL?  (problem: bug#)?
| OK or FAIL?  (problem: bug#)?
| more problem details?
| more problem details?

Revision as of 06:19, 30 April 2009

DATE TIME WHERE
2009-05-14? TBD: fedora-i18n team available during Asian daytime/evening #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 ...

Prerequisite for Test Day

  • Rawhide fully updated or at least the Preview release
  • A native keyboard for your country/region if you have one

How to test?

Testing iBus usage to input native languages:

  • Login to desktop in your native language or the one you wish to test.
  • Run im-chooser to turn on iBus if it is not enabled by default in your language
  • Test iBus usage by inputting in various applications like gedit, firefox, openoffice.org, pidgin, evolution, thunderbird, kate, your favourite applications, etc in your desktop (GNOME, KDE, or others).

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 Cases and Results

User Desktop Desktop language Activation Input method Keyboard Application Result Comments
Explanation: User:Example GNOME, KDE, XFCE, LXDE? de, en, fr, hi, ja, ko, zh, etc? input method system starts ok? anthy, chewing, hangul, pinyin, rawcode, table? de, fr, gb, us, jp, kr, etc? gedit, firefox, openoffice, pidgin, kate, eclipse, etc? OK or FAIL? (problem: bug#)? more problem details?