[openi18n-im:01439] Re: Upcoming Gimlet related enhancements

Federic,

> From: Federic Zhang <[email protected]>
> IMHO, our work isn't directly related to the original sub-tasks ("unify
> all configuration to one window" and "move all lang data out to LEs"),
> it would be great if someone can give more description of the two
> sub-tasks in details.

The "unify all configuration to one window" subtask is exactly 
the same with the dynamic GUI configuration framework Phill
has done. So this side of story is simple :-).

The "move all lang data out to LEs" subtask may not exactly be
same with your updates on detailed LE info and enhanced IM switching
capability. It actually pauses further necessity of this task.

The reason currently Gimle holds the lang data within itself is
for translation.

It's a traditional prblem of distributed messaging. There are several 
options to do this. We just need to pick which method to use, and
implement it. (Technically it's not a big deal.)
Here is some options:
- Instead of Gimlet, LE to prepare all traslated strings, and
  LE to pass it onto iiimd.
- LE to pass the textdomain info so that Gimlet can use PO file of LE
  to perform messaging
- Create message DB for Gimlet from LEs at build time by extracting
  translatable messages from LE.


Hideki