Bug 166231

Summary:	input preedit string gets replicated in Evolution Cal (devel)
Product:	[Fedora] Fedora	Reporter:	Dave Malcolm <dmalcolm>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	aalam, eng-i18n-bugs, llim, majain
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-08-31 14:56:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	131227
Bug Blocks:	150221

Description Dave Malcolm 2005-08-18 03:38:06 UTC

+++ This bug was initially created as a clone of Bug #131227 +++

Description of problem:
In CJK locale, input characters gets replicated when they are not
comitted.

Version-Release number of selected component (if applicable):
- evolution-data-server-0.0.97-2
- evolution-1.5.92.2-2
- im-sdl-12.0.1-1

How reproducible:
Always

Steps to Reproduce:
1.Select any CJK locale at gdm and log in (in this example, we use Japan)
2.Start Evolution -> Select Cal
3.Ctrl+SPACE to activate the Language Engine
4.Single click any of the time widget and enter 'aka' 
5.Repeat Step 4, you should see the charcters replicating 
  
Actual results:
Please refer to screen shot

Expected results:
Characers does not get replicated.

Additional info:
Tested in GNOME environment

Comment 1 Dave Malcolm 2005-08-18 03:39:15 UTC

What's the status of this in rawhide?

Comment 2 Akira TAGOH 2005-08-18 07:24:12 UTC

Well, I apologize I totally misunderstood about this problem. so this problem
still appears. the real problem is that the preedit buffer isn't reset when the
focus is changed by clicking another cell during preediting. I mean
gtk_im_context_reset has to be called at the focus in/out events.
So correctly this isn't "input preedit string gets replicated" because the
preedit characters isn't committed at the editing cell when another cell is
clicked. but it just appears again at the another cell so that GtkIMContext
doesn't get any the end of preediting notification or so by neither pressing
'enter' nor gtk_im_context_reset().

Comment 3 Christopher Aillon 2006-01-27 20:24:34 UTC

there appears to be a fix in http://bugzilla.gnome.org/show_bug.cgi?id=264485
that is stagnating.

Comment 4 Akira TAGOH 2006-02-21 05:31:03 UTC

This behavior disappears to me in the latest evolution now. so perhaps we could
close this now?

Comment 5 Akira TAGOH 2006-02-21 11:54:57 UTC

Err, this bug is still there. why I couldn't see this at that time is, I've
enabled the global IC mode on scim. but even it introduces another bug on evo.
so the handling of IM on calendar view is totally broken.

Comment 7 Mayank Jain 2006-05-16 10:20:10 UTC

This bug is duplicate of #131227, marking as duplicate.

Comment 8 Mayank Jain 2006-05-16 10:21:48 UTC


*** This bug has been marked as a duplicate of 131227 ***

Comment 11 Mayank Jain 2006-06-21 08:24:39 UTC

Fixed in upstream code... adding the external
bugzilla ref - http://bugzilla.gnome.org/show_bug.cgi?id=264485

Comment 13 Mayank Jain 2006-07-06 09:06:58 UTC

Hi Matt,

The Patch in http://bugzilla.gnome.org/attachment.cgi?id=65213&action=view seems
to be missing from the latest builds. Can you please apply it to the latest code
base?

If you need any more info, please let me know.

PS: this is same bug as bug #157391 and bug #131227 & hopefully the same patch
should do.

Thanks,
Mayank

Comment 14 Matthew Barnes 2006-07-06 16:58:51 UTC

Done - evolution-2.7.3-8

Only two of the three hunks in the patch applied.  The third (plugs a memory
leak) is already fixed upstream.

Changing component from evolution-data-server to evolution.

Comment 15 A S Alam 2006-08-31 14:56:40 UTC

for ja_JP is working fine, no replication for strings

Comment 16 A S Alam 2006-08-31 14:57:51 UTC

*** Bug 157391 has been marked as a duplicate of this bug. ***