Omissions are
1. No dropbox
2. No torrents
3. No cheese
Helping visually handicapped is a remarkable feature of Ubuntu.
I wish them success with their new endeavour with Unity.
Postscript
If one wants to save time one could have uesd an external dirve to do the job and I have several (DVD witers) of them but thay are not used for odd jobs but only image writing.
I recommend netbook for laptop which can be easily booted up with a USB Key.
I hate heavy luggage to do simple jobs.
One should check the battery before any of these and if the battery is not chargin it is not worth the try.Most up-to-date version of this document can always be found here.
Latest version of SCIM module is 0.3.3. Download it here.
If you are looking for a reference while typing with Sayura, download this brochure.
I wrote the first implementation of Sayura transliterated scheme in mid 2004 to include in our first package (version 0.1 it was called) to enable Sinhala in GNU/Linux. It was only for GTK, and not properly named. For the GTK part of the implementation, I used some code from another im-module written by Chamath Keppitiyagama.
Sayura defines context dependant behaviour of keys. For example, "i" at the beginning of a word produced "ඉ", after another "i" it converted "ඉ" to "ඊ", after a consonant it added an ispilla, and after a consonant with an ispilla, it converted the ispilla to a diga ispilla. Multiple use of keys depending on the context allowed us to use fewer keys in very intuitive ways.
Sayura algorithm internally uses bytes, not UTF-8. Sinhala code page is mapped to characters 128-255, and ZWJ and ZWNJ are given 0x0d and 0x0c.
In September 2004, I announced an attempt to port the GTK im-module to QT. After first implementing surrounding text support, the QT port of the im-module was announced in late September 2004, and included in Sinhala GNU/Linux 0.2.
However, my patch to QT broke binary compatibility, so applying it also required a complete recompile of dependant apps. Therefore, it was unlikely to go upstream. Although Kazuki Otta's port made to QT4 upstream, QT3 apps were going to be there for a long time to come.
Typing in OpenOffice was yet to be solved.
In October 2005, there was a Codefest in Colombo as a part of the Asia OSS conference. Kazuki Otta ported the GTK module to SCIM. As SCIM stands below GTK, QT and OpenOffice and all other X apps, it provided a unified input mechanism.
The algorithm's dependency on surrounding text support was also removed. The package was called "scim-sinhala-trans".
For the next couple of years, scim-sinhala-trans became the primary input scheme on GNU/Linux systems, and was shipped with some distros including Fedora/Redhat. Debs were always available here.
In early 2008, S Pravin sent some patches to add preedit support and other improvements. I added several tweaks to the Sayura algorithm itself to preserve old semantics with the new preedit code, and also to improve in certain places. A key improvement is bringing back surrounding text support, but only to use it when available.
A development series 0.3.x was announced in May 2008 to continue and test the new set of developments, and the scheme was named "Sayura" to distinguish from other schemes such as Samanala and Sumihiri.
Long wovels are typed by pressing the same key twice. For example, "aa" produces "ආ".
For example, "kii" produces "කී", while "kU" gives us "කෘ".
Latest version of SCIM module is 0.3.3. Download it here.
If you want to try out the present stable version of Sayura SCIM module (which is called scim-sinhala-trans), follow the instructions at sinhala.sourceforge.net. However, we encourage you to test 0.3 series, which brings out "preedit" support and improvements to the scheme itself.
On Debian based systems, make a DEB package:
% tar -xzvf scim-sayura-0.3.3.tar.gz
% cd scim-sayura-0.3.3
% dpkg-buildpackage -b
If you get a "command not found" error, install the "dpkg-dev" package, and preferably "build-essential" package as well.
If dpkg-buildpackage complains about missing packages, install them and try again.
Locate your RPM directory, usually in /usr/src/. Following examples assume /usr/src/rpm. You also need the 'rpmbuild' tool.
First unpack the tarball to a temporary location, and copy the rpm/scim-sayura.spec file to the SPECS subdirectory in RPM directory. Copy the tarball into SOURCES subdirectory.
# cd /tmp
# tar -xzvf /wherever/is/scim-sayura-0.3.3.tar.gz
# cp scim-sayura-0.3.3/rpm/scim-sayura.spec /usr/src/rpm/SPECS/
# cp /wherever/is/scim-sayura-0.3.3.tar.gz /usr/src/rpm/SOURCES/
Now run the rpmbuild command with the -bb options to build a binary RPM inside RPMS subdirectory.
# cd /usr/src/rpm/SPECS/
# rpmbuild -bb scim-sayura.spec