registry team mailing list archive

[Bug Watch Updater <260589@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 9 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=17468.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-09-07T06:59:07+00:00 Denis Jacquerye wrote:

In Fedora 10's rawhide and Ubuntu 8.10 alpha 4 the Congo DRC layout is
broken. Combining diacritics keys have somehow become deadkeys. The
symbol file hasn't changed so something went wrong in the way it is
interpreted.

For example, previously pressing the U+0301 key would actually produce
U+0301. Now it doesn't do anything but acts as a deadkey, so if followed
by a key of a character with precomposed acute accent existing that one
is produced.

Ex: press ɛ key followed by U+0301 key ... nothing after ɛ
press ɛ key followed by U+0301 key and then e, the result is ɛé
What is expected is ɛ́ always.

This is serious as combining diacritics are absolutely required because
strings like ɛ́ can only be represented with them.

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/2

------------------------------------------------------------------------
On 2008-09-25T03:52:29+00:00 Denis Jacquerye wrote:

xev output http://launchpadlibrarian.net/17950812/intrepid.cd.txt 
bug has also been reported there https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/260589

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/5

------------------------------------------------------------------------
On 2008-09-25T04:14:04+00:00 Simos Xenitellis wrote:

Let's see if GTK+ is interfering here.

Can you try

export GTK_IM_MODULE=xim
gedit

and check if the Congo layout works now in gedit?

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/6

------------------------------------------------------------------------
On 2008-09-25T05:09:18+00:00 Denis Jacquerye wrote:

(In reply to comment #2)
> Let's see if GTK+ is interfering here.
> 
> Can you try
> 
> export GTK_IM_MODULE=xim
> gedit
> 
> and check if the Congo layout works now in gedit?
> 

export GTK_IM_MODULE=xim does fix it.
So it's a Gtk+ bug?

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/7

------------------------------------------------------------------------
On 2008-09-25T07:37:07+00:00 Simos Xenitellis wrote:

(In reply to comment #3)
> (In reply to comment #2)
> > Let's see if GTK+ is interfering here.
> > 
> > Can you try
> > 
> > export GTK_IM_MODULE=xim
> > gedit
> > 
> > and check if the Congo layout works now in gedit?
> > 
> 
> export GTK_IM_MODULE=xim does fix it.
> So it's a Gtk+ bug?
> 

A change that took place, and I believe it relates to this bug, is at 
http://svn.gnome.org/viewvc/gtk%2B/trunk/gtk/gtkimcontextsimple.c?view=annotate
lines 928-932.

The order of check_algorithmically() and check_compact_table() changed
(check_algorithmically() was put first recently), so that issues with
the compose table mess are silently bypassed.

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/8

------------------------------------------------------------------------
On 2008-09-25T08:39:26+00:00 Simos Xenitellis wrote:

Denis,

Regarding workarounds for now, one option is to produce a patch for GTK+ that can be used for the OLPC now. 
Does the OLPC maintain patches on top of stable releases of libraries?

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/9

------------------------------------------------------------------------
On 2008-09-30T12:42:56+00:00 Simos Xenitellis wrote:

(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Let's see if GTK+ is interfering here.
> > > 
> > > Can you try
> > > 
> > > export GTK_IM_MODULE=xim
> > > gedit
> > > 
> > > and check if the Congo layout works now in gedit?
> > > 
> > 
> > export GTK_IM_MODULE=xim does fix it.
> > So it's a Gtk+ bug?
> > 
> 
> A change that took place, and I believe it relates to this bug, is at 
> http://svn.gnome.org/viewvc/gtk%2B/trunk/gtk/gtkimcontextsimple.c?view=annotate
> lines 928-932.
> 
> The order of check_algorithmically() and check_compact_table() changed
> (check_algorithmically() was put first recently), so that issues with the
> compose table mess are silently bypassed.
> 

I looked deeper into the issue.

The above information regarding the specific change in the GTK+ code is
not correct.

This bug was introduced in GTK+ in March 2008, when the first patch to update gtkimcontextsimple.c was committed.
There was a call at that point for testing,
http://blogs.gnome.org/simos/2008/03/05/testing-the-updated-im-support-in-gtk/
however this issue with the specific use of combining diacritics was missed.

I am planning to close this report as NOTOURBUG and open a report in
GNOME Bugzilla.

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/12

------------------------------------------------------------------------
On 2008-09-30T16:04:23+00:00 Simos Xenitellis wrote:

This issue has been reported to GNOME Bugzilla,
http://bugzilla.gnome.org/show_bug.cgi?id=554506

I am closing this report. Thanks Denis for reporting.

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/13

------------------------------------------------------------------------
On 2008-09-30T16:07:04+00:00 Sergey V. Udaltsov wrote:

Quite an exotic case. There were loads of bugs closed in gnome as
NOTGNOME, transferred here to xkeyboard-config. But this one went the
opposite direction.

Reply at: https://bugs.launchpad.net/gtk/+bug/260589/comments/14


** Changed in: xkeyboard-config (Fedora)
       Status: Invalid => Won't Fix

** Changed in: xkeyboard-config
       Status: Invalid => Won't Fix

** Changed in: xkeyboard-config (Fedora)
   Importance: Unknown => Medium

** Changed in: xkeyboard-config
   Importance: Unknown => Medium

-- 
combining diacritics replaced by deadkeys
https://bugs.launchpad.net/bugs/260589
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Fedora.