Bug 1008075 - ibus preedit don't works with non-latin language
ibus preedit don't works with non-latin language
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: ibus-anthy (Show other bugs)
19
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: fujiwara
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-14 08:22 EDT by mortilla
Modified: 2013-09-16 22:51 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-16 22:51:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mortilla 2013-09-14 08:22:13 EDT
Description of problem:
When switched form non-latin language (Russian) to Japanese (anthy) iBus don't change layout and continue russian.


Version-Release number of selected component (if applicable):
1.5.3

How reproducible:
Always

Steps to Reproduce:
1. Have tri-language setup: RU-EN-JA
2. Switch to RU
3. Switch to JA.

Actual results:
Input continues in russian, with exception of punctuation marks and space which is Japanese.

Expected results:
Show preedit and begin conversion regardless of previously selected layout.

Additional info:
If i switch from EN to JA - everything works as expected. But not if switch form RU to JA.
Downgrading ibus ibus-gtk3 ibus-gtk2 ibus-setup ibus-libs to 1.5.2 with yum resolves problem.
ibus-anthy 1.5.3 doesn't seems being source of this problem and i haven't downgraded it.
Comment 1 fujiwara 2013-09-16 22:51:04 EDT
ibus-anthy does not change the keymap by default.
If you use non-latin layout, you need to customize ibus-anthy below.

1. Run ibus anthy setup (/usr/libexec/ibus-setup-anthy)
2. Select "Typing Method" tab.
3. Choose" "us" in keyboard layout.
4. Restart ibus (ibus restart)

Note You need to log in before you can comment on or make changes to this bug.