Bug 134194 - [UnitLE] does not turn on for bn_BD.UTF-8
[UnitLE] does not turn on for bn_BD.UTF-8
Product: Fedora
Classification: Fedora
Component: im-sdk (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jens Petersen
: i18n
Depends On:
Blocks: IIIMF Indic
  Show dependency treegraph
Reported: 2004-09-30 00:15 EDT by Jatin Nansi
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version: im-sdk-12.0.1-17.svn1994
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-18 05:27:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jatin Nansi 2004-09-30 00:15:52 EDT
Description of problem:
The bengali(Bangladesh) locale (bn_BD.UTF-8) is technically similar to
bengali(India) locale (bn_IN.UTF-8). Only the translations differ.
IIIMF should be turned on for this locale as well.

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

How reproducible:
Every time

Steps to Reproduce:
1. Log into the bengali(Bangladesh) locale (bn_BD.UTF-8).
2. Start gedit
3. Ctrl+space
Actual results:
Cannot input bengali

Expected results:
Should be able to input bengali

Additional info:
Comment 1 Leon Ho 2004-09-30 05:13:00 EDT
Will need to add a extra section for this lang and give some test.
Assigning to Jatin.
Comment 2 Jens Petersen 2004-10-04 22:36:58 EDT
Just need to add bn_BD to indic_locale in im-sdk.spec.
Comment 4 Akira TAGOH 2004-10-14 06:21:14 EDT
should be fixed in 12.0.1-13.svn1943 or later.
Comment 5 Lawrence Lim 2004-10-18 05:27:16 EDT
Confirmed fixed. Tested with im-sdk-12.0.1-17.svn1994. 

Noted that GIMLET has no display of locale, like TC for zh_TW and Ja
for ja_JP.

Comment 6 Jens Petersen 2004-10-18 11:15:32 EDT
Later should be fixed in 12.1-1.
Comment 7 Jens Petersen 2004-10-19 12:47:21 EDT
Sorry the Bengali locale patch was actually in 12.1-1:
it should be in 12.1-3 though.

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