alternate input methods (redux)
Posted: 06 Mar 2012, 14:55
Hi all,
There has been some discussion on the boards lately regarding alternate input methods in Porteus. These are programs (examples: gcin, ibus, uim, scim) that enable users to enter characters in other (non-latin) languages, such as chinese, japanese, etc. Rather than continuing to spread the discussion over threads in other areas, I'm starting this one here in the Development section, with a hope of getting something accepted into either the module repo or the Language-Selection-Tool
I've been working on getting gcin and scim built for Porteus and would like some user input as to which works better for users. My initial impression (though I don't speak any of these languages) is that gcin provides more variety for inputting Chinese (and seems to be favored in Taiwan), but scim seems to handle a broader variety of languages. Scim is present upstream in Slackware, which means it would also be less work to maintain (gcin would require maintenance of a porteus slackbuild, which I have mostly finished).
Here are the modules:
32-bit SCIM: http://porteus-xfce.googlecode.com/file ... n-i486.xzm
64-bit SCIM: http://porteus-xfce.googlecode.com/file ... x86_64.xzm
32-bit gcin: http://porteus-xfce.googlecode.com/file ... s-i486.xzm
64-bit gcin: http://porteus-xfce.googlecode.com/file ... x86_64.xzm
I should note that scim did not work for me right away -- I had to add some additional packages (namely, scim-bridge, but I added a bunch of others to add as much support as possible); I also had to make two files executable: /etc/profile.d/scim.csh and /etc/profile.d/scim.sh -- when installed via txz2xzm, they are set without the executable bit turned on.
If you have other suggestions please let me know. I should note that these packages should be used one at a time, as they will conflict with each other (they each need the same environmental variables set, so one will always take precedence over the other). I think both could be included in the repo if the maintainers approve them, but if we're going to add an IM to Language Selection Tool, I think we should choose one and run with it, and the other can serve as an alternate.
Note that for most languages you'll need a font that supports displaying characters in that language. While we're on the subject, if you all have font suggestions for languages that you speak, that would be helpful as well (must be free; GPL would be best).
In order to start typing in with either program, start up an application and press ctrl+space. This will load up the interface and you can start typing. You can click on the panel icons to select your desired language/dialect.
Note that these modules work with all Desktop Environments's for all GTK and QT4 apps that I have tested so far; however, they do not work with QT3 apps in any DE -- so if you're using 32-bit (Trinity), you'll need to use GTK apps (e.g. lxterminal, abiword, leafpad) instead of QT apps (e.g. konsole and kwrite). Firefox is GTK and appears to work out of the box.
@brokenman, I'm beginning to wonder if trinity's qt3 includes support for immodules? There was a patch for qt3 written back in 2004 and it looks like someone revived it for trinity, here: http://code.google.com/p/trinityqt3/ but I don't know if the folks at trinity already included an implementation or some other approach to this.
Thanks, all!
There has been some discussion on the boards lately regarding alternate input methods in Porteus. These are programs (examples: gcin, ibus, uim, scim) that enable users to enter characters in other (non-latin) languages, such as chinese, japanese, etc. Rather than continuing to spread the discussion over threads in other areas, I'm starting this one here in the Development section, with a hope of getting something accepted into either the module repo or the Language-Selection-Tool
I've been working on getting gcin and scim built for Porteus and would like some user input as to which works better for users. My initial impression (though I don't speak any of these languages) is that gcin provides more variety for inputting Chinese (and seems to be favored in Taiwan), but scim seems to handle a broader variety of languages. Scim is present upstream in Slackware, which means it would also be less work to maintain (gcin would require maintenance of a porteus slackbuild, which I have mostly finished).
Here are the modules:
32-bit SCIM: http://porteus-xfce.googlecode.com/file ... n-i486.xzm
64-bit SCIM: http://porteus-xfce.googlecode.com/file ... x86_64.xzm
32-bit gcin: http://porteus-xfce.googlecode.com/file ... s-i486.xzm
64-bit gcin: http://porteus-xfce.googlecode.com/file ... x86_64.xzm
I should note that scim did not work for me right away -- I had to add some additional packages (namely, scim-bridge, but I added a bunch of others to add as much support as possible); I also had to make two files executable: /etc/profile.d/scim.csh and /etc/profile.d/scim.sh -- when installed via txz2xzm, they are set without the executable bit turned on.
If you have other suggestions please let me know. I should note that these packages should be used one at a time, as they will conflict with each other (they each need the same environmental variables set, so one will always take precedence over the other). I think both could be included in the repo if the maintainers approve them, but if we're going to add an IM to Language Selection Tool, I think we should choose one and run with it, and the other can serve as an alternate.
Note that for most languages you'll need a font that supports displaying characters in that language. While we're on the subject, if you all have font suggestions for languages that you speak, that would be helpful as well (must be free; GPL would be best).
In order to start typing in with either program, start up an application and press ctrl+space. This will load up the interface and you can start typing. You can click on the panel icons to select your desired language/dialect.
Note that these modules work with all Desktop Environments's for all GTK and QT4 apps that I have tested so far; however, they do not work with QT3 apps in any DE -- so if you're using 32-bit (Trinity), you'll need to use GTK apps (e.g. lxterminal, abiword, leafpad) instead of QT apps (e.g. konsole and kwrite). Firefox is GTK and appears to work out of the box.
@brokenman, I'm beginning to wonder if trinity's qt3 includes support for immodules? There was a patch for qt3 written back in 2004 and it looks like someone revived it for trinity, here: http://code.google.com/p/trinityqt3/ but I don't know if the folks at trinity already included an implementation or some other approach to this.
Thanks, all!