Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
1) Install scim-m17n and m17n-db (In Ubuntu, it is in the Universe
2) Download the m17n Wijesekera input method from:
3) Copy the file to /usr/share/m17n/
4) Logout and Login again, no need to restart
5) Select the M17N-si-wijesekera-preedit input method in SCIM
6) Type away
7) And don't forget to provide feedback!
On 12/5/06, Harshula <harshula@...> wrote:
> 1) Install scim-m17n and m17n-db (In Ubuntu, it is in the Universe
In case of Dapper there is a mess up in the universe repo's packages
for this : versions mismatch between libm17n-0 and m17n-db and the
result being if installed from repo then m17n keyboards don't show up
with scim. (If we compile from compatible versions tar balls of
m17n-db and m17n-lib to install, then they work fine with scim.
That's how I had done in my Dapper).
I have seen this bug being raised by Omi Azad and discussed in
different forums during latter part of last year. Here is a reply of
Takahashi N. (m17n.org) :
In different forums solution suggested is to upgrade to Edgy. The
concerned two packages in Dapper's universe repo continue to be the
same mismatched versions.
If package maintainers give up on older versions like in above case
then to users like us there is less practical benefits from
Canonical's policy of supporting them for many months more. I think
only LTS releases (with 36 months support commitment) once every 18
months would be better than the current too frequent once every 6
months shorter term releases. That way package maintainers can focus
on lesser number of versions at a given time for more updates for bug