Bug 426002 - Kbabel from kdesdk does not allow Indic input
Kbabel from kdesdk does not allow Indic input
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kdesdk (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-17 13:01 EST by Sankarshan Mukhopadhyay
Modified: 2007-12-27 09:40 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-12-27 09:40:41 EST
Type: ---
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 Sankarshan Mukhopadhyay 2007-12-17 13:01:20 EST
Description of problem:

Using Kbabel to input bn_IN does not work.

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

kdesdk-3.5.8-2.fc8
kdesdk-libs-3.5.8-2.fc8
im-chooser-0.5.3-1.fc8
scim-bridge-gtk-0.4.13-6.fc8
scim-1.4.7-7.fc8
scim-m17n-0.2.2-2.fc8
scim-libs-1.4.7-7.fc8
scim-lang-bengali-1.4.7-7.fc8
scim-bridge-0.4.13-6.fc8
m17n-db-1.4.0-6.fc8
m17n-db-bengali-1.4.0-6.fc8
scim-m17n-0.2.2-2.fc8
m17n-contrib-1.1.3-3.fc8
m17n-lib-1.4.0-2.fc8
qt4-x11-4.3.2-4.fc8
qt4-4.3.2-4.fc8
qt-3.3.8-9.fc8


How reproducible:


Steps to Reproduce:
1. Open KBabel, type in en_US
2. Ctrl+Space to shift to bn_IN keyboard with SCIM activated
3. Type bn_IN text
  
Actual results:

English characters are input and displayed

Expected results:

Bengali (India) bn_IN characters to be input and displayed

Additional info:
Comment 1 Sankarshan Mukhopadhyay 2007-12-17 23:05:09 EST
This happened in en_US locale if that information is of any use.
Comment 2 Sankarshan Mukhopadhyay 2007-12-27 00:30:03 EST
Had to yum remove and yum install the scim bits and set preferences through
im-chooser again to get it working.

Please CLOSE this
Comment 3 Rex Dieter 2007-12-27 09:40:41 EST
Thanks.

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