Description of problem:
In oocalc hitting the TAB key causes current cell to jump to the right.
Unfortunately if you are using IIIMF canna input in a cell, and hit TAB during
preedit before committing text, it goes to the right cell without canceling
preedit. Subsequent IIIMF state is not proper. SPACE brings up the candidate
selection window. Other keys do nothing. ENTER a few times cancels preedit
with apparently no effect, but it does recover from this state.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run oocalc.
2. Enable Japanese IIIMF input.
3. Type 'nihongo' then TAB
4. (BUG A) Type anything, nothing happens
5. Hit ENTER a few times to recover.
6. Type 'nihongo' then TAB
7. (BUG B) Hit SPACE SPACE, select anything, no effect.
Cell changes with TAB, but preedit is not canceled, leading to unexpected behavior.
Commit then preedit should be canceled immediately upon jumping cell.
It seems oocalc doesn't call gtk_im_context_reset() when TAB was pressed. I
could reproduce this problem with/without gtk_im_context_reset() implementation
Still needs to be forward-ported to FC2 & FC3.
Would forward porting be difficult? We had several FC updates of OOo lately...
Is this fixed in 2.0 beta upstream too?
caolanm->dcbw: is this done already for fc2/fc3 ?
openoffice.org-1.1.3-9.5.0.fc3 is not yet fixed.
Fixes are only in RHEL3 and RHEL4 builds at this time. I've got a patch for 2.0 that I'll be forwarding to
caolan, and I'll patch up the FC3 builds soon. However, are we able/willing to push updated IIIMF to
FC2 to support this, or is that not possible?
Updating IIIMF in FC2 will require updating xinitrc too, which is usually a
risky endeavor. I am looking at feasibility now as well as making FC2 and FC3
update candidates of im-sdk.
mharris is making me follow some procedure that involves product management and
business justification in order to make this change happen in FC2 xinitrc. I
don't have time for this especially given that FC2 will be transferred to Legacy
soon, so im-sdk will not be upgraded on FC2.
IIRC openoffice.org was never functional at all with FC2 IIIMF, so upgrading
openoffice without im-sdk really isn't much of a loss. Thoughts?
FC3 openoffice.org and im-sdk will be an easy upgrade.
ping dcbw, can we go ahead with the openoffice.org updates?
duping this to Bug 137398 as that has the fixes for this.
Warren: can you test and verify the packages in 137398 comment #17?
*** This bug has been marked as a duplicate of 137398 ***