Closed Bug 214412 Opened 22 years ago Closed 20 years ago

No way to switch the GTK input modules

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: unmadindu, Assigned: blizzard)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 Epiphany/0.8.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 My $LANG variable is set to bn_IN.UTF-8, and I have the Bengali GTK input method module imbeng installed. When I start up mozilla, the input method defaults to Bengali, and I cannot type in urls in English. Apparently, there is no way to switch the input module. a possible workaround is to set the $LANG to en_US from a terminal, and start mozilla after that from that terminal. Reproducible: Always Steps to Reproduce: 1. Download and install the imbeng package from http://sourceforge.net/project/showfiles.php?group_id=43331&release_id=136965 2. Download and install the Sagar font from http://savannah.nongnu.org/files/?group=freebangfont&highlight=0.6.0#Sagar0.6.0 3. Set the $LANG variable as $bn_IN.UTF-8 4. Start Mozilla 5. Try to write anything in the address bar Actual Results: All characters typed are in Bengali Expected Results: There should be some way (a menu perhaps??) which lets you switch the Input Method to English.
Assignee: general → blizzard
Component: Browser-General → GFX: Gtk
QA Contact: general → ian
You mean like in every other gtk2 application?
Blocks: gtk2
another possible workaround is to set $GTK_IM_MODULE to the input method you want, in this case you would do GTK_IM_MODULE=xim mozilla I think... personally I use GTK_IM_MODULE=scim and use scim to switch between input methods, but this is not always available and scim does not currently support alot of input methods. http://scim.freedesktop.org/
Yeah, SCIM and IIIIMF should 'solve' this problem without anything changed on the part of Mozilla.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.