Re: Static compose table in gtkimcontextsimple.c

[Simos Xenitellis <simos lists googlemail com>]

On Thu, 2007-12-06 at 12:28 +0000, Paul LeoNerd Evans wrote:
> On Tue, 04 Dec 2007 05:38:56 +0000
> Simos Xenitellis <simos lists googlemail com> wrote:
> 
> > If you would like to help with bug 321896 it would be great. The current 
> > state is on how to make the table much smaller, even with the addition of
> > more keysyms. There is a script that converts en_US.UTF-8/Compose into a
> > series of arrays that should be easy for GTK+ to work on. 
> 
> OK, I've had a good read through that bug, and now I'm confused again.
> 
> Can someone explain why GTK has to have this large table compiled into
> it..? I thought X itself provided ways to perform input composition into
> Unicode strings. Otherwise, why do I have a file
> 
>   /usr/share/X11/locale/en_US.UTF-8/Compose
> 
> Can we just use that?

There are issues on GTK+ running on other platforms that require to have a separate copy. 
Having the file contents in the library as static data is good for performance and memory use.

I just compiled Tor's working patch which actually eliminates most of 
the compose sequences and it is amazing in the way it simplifies the work.
I think it is the way to go once the small issues are resolved.

Simos