[Localization] Status on SCIM

[Sayamindu Dasgupta]

On Fri, Sep 5, 2008 at 7:25 PM, Jim Gettys <jg at laptop.org> wrote:
> Seems like the next step is a proof of concept....
>
> What's the basic footprint of SCIM, anyway?
>                     - Jim
>


I just managed to strip out the perl (and whatnot dependency), and the
base packages (without the keyboard layout data) takes up around 3 MB
(gathered from the rpm -qi information). I have not analysed memory
usage yet, but I guess that will depend on the IMEngine being used
(Chinese and the rest of the CJKV stuff would probably take up much
more memory than others).
Once of the nice things I noticed about SCIM and m17n packaging in
Fedora is that all keyboard layout data are separated into language
specific packages, which should mean some space saving for us.
Thanks,
Sayamindu


>
> On Fri, 2008-09-05 at 19:01 +0530, Sayamindu Dasgupta wrote:
>> On Fri, Sep 5, 2008 at 6:22 PM, Jim Gettys <jg at laptop.org> wrote:
>> > Sayamindu,
>> >
>> > I still see no compelling reason to convert the existing layouts to
>> > scim, at least in the short term.  It may certainly be best for future
>> > keyboards to do it "the new way".
>> >
>> > What am I missing?
>> >                           - Jim
>> >
>>
>> If we want to keep the existing XKB based system, we would have to
>> load SCIM conditionally, which I want to avoid (and maintaining and
>> supporting two different IMs might be a bit of pain). Also, even some
>> of the existing keyboard layouts would benefit from a switch to SCIM
>> (eg: Amharic and Nepali).
>> >From what I understand (till now) - it is not a major effort to
>> convert existing XKB symbol files to .mim files, the process should be
>> relatively straightforward and easily scriptified. Of course, I don't
>> have a proof of concept yet :-)
>>
>> Thanks,
>> Sayamindu
>>
>>
>> >
>> > On Fri, 2008-09-05 at 17:48 +0530, Sayamindu Dasgupta wrote:
>> >> Hello,
>> >> During this week, I poked SCIM a bit more, especially on the topic of
>> >> migrating our existing layouts to the framework. It looks like the
>> >> m17n IMEngine would be the best way to go forward at this stage for
>> >> our existing layouts (though I need to check a bit more on the
>> >> dependencies it will be pulling in). I'll try to come up a (semi)
>> >> automate way to migrate our XKB symbol files to the m17n .mim format
>> >> by next week.
>> >> Thanks,
>> >> Sayamindu
>> >>
>> >>
>> > --
>> > Jim Gettys <jg at laptop.org>
>> > One Laptop Per Child
>> >
>> >
>>
>>
>>
> --
> Jim Gettys <jg at laptop.org>
> One Laptop Per Child
>
>



-- 
Sayamindu Dasgupta
[http://sayamindu.randomink.org/ramblings]