Skip to main content

Enabling Sinhala in Linux

How to install

  1. Add to /etc/apt/sources.list

    1. On Debian 4.0 (Etch)

      deb http://sinhala.sourceforge.net/debian/i386/etch/ ./

    2. On Debian testing (Lenny)

      deb http://sinhala.sourceforge.net/debian/i386/lenny/ ./

    3. On Ubuntu 7.10 (Gutsy) i386

      deb http://sinhala.sourceforge.net/ubuntu/i386/gutsy/ ./

    4. On Ubuntu 7.10 (Gutsy) amd64

      deb http://sinhala.sourceforge.net/ubuntu/amd64/gutsy/ ./

  2. Update repository metadata:
    apt-get update

  3. Install Sinhala packages:
    apt-get install sinhala-gnu-linux

  4. Upgrade relevant packages:
    apt-get upgrade

  5. Logout and login again. Environment variables need to be set/updated (NO NEED TO REBOOT)


How to test

  1. Visit http://si.wikipedia.org/ and see if the Sinhala letters render correctly.

  2. Copy and paste some of the content from Sinhala wikipedia to Open Office Writer. Then highlight the Sinhala text and choose the LKLUG font to display them.

  3. To test SCIM, press Control-space whilst you are running a GNOME application. Then select one of the Sinhala input methods


Read More

Comments

4srilankan said…
explain how to enable sinhala in computer which doesn't have internet connection.
January 16, 2008 at 1:22 PM
4srilankan said…
explain how to enable sinhala in computer which doesn't have internet.
January 16, 2008 at 1:26 PM
Prabath Ariyarathna said…
Hi....

If you haven't Internet connection you can follow very easy way to do this. You want to go to the computer with E-net connection.This computer must use same Linux version which you use in you're computer.After you can follow my article and enable sinhala in computer. After you can make a repository.Using this Repo you can enable sinhala in you're computer.
If you don't know how to make Repo use this article:-http://prabu-lk.blogspot.com/2008/04/repo-linux-command-for-ubuntu.html
October 8, 2008 at 12:14 PM
Post a Comment

Popular posts from this blog

How to enable proxy service security in ESB 4.9.0?

Security is  one of the major concern when we developing API base integrations or application developments. WSO2 supports WS Security , WS-Policy and WS-Security Policy specifications. These specifications define a behavior model for web services. Proxy service security requirements are different from each others. WSO2 ESB providing pre-define commonly used twenty security scenarios to choose based on the security requirements. This functionality is provided by the security management feature which is bundled by default in service management feature in ESB. This configuration can be done via the web console until ESB 4.8.1 release, but this has been removed from the ESB 4.9.0. Even though this feature isn't provided by the ESB web console itself same functionality can be achieved by the new WSO2 Dev Studio . WSO2 always motivate to use dev studio to prepare required artifacts to the ESB rather than the web console. Better way to explain this scenario is by example. Following...
3 comments
Read more

How to preserving HTTP headers in WSO2 ESB 4.9.0 ?

Preserving HTTP headers are important when executing backend services via applications/middleware. This is because most of the time certain important headers are removed or modified by the applications/middleware which run the communication. The previous version of our WSO2 ESB, version 4.8.1, only supported “ server ” and “ user agent ” header fields to preserve with, but with the new ESB 4.9.0, we’ve introduced a new new property ( http.headers.preserve ) for the passthru ( repository/conf/ passthru-http.properties ) and Nhttp( repository/conf/ nhttp.properties ) transporters to preserve more HTTP headers. Passthru transporter – support header fields               Location Keep-Alive Content-Length Content-Type Date Server User-Agent Host Nhttp transport – support headers Server User-Agent Date You can specify header fields which should be preserved in a comma-separated list, as shown below. http.headers.p...
Post a Comment
Read more

How to monitor the Thread CPU usage in the WSO2 Products?

1. Download JConsole topthreads Plugin. 2. Add following entries to the PRODUCT_HOME/bin/wso2server.sh     -Dcom.sun.management.jmxremote \     -Dcom.sun.management.jmxremote.port=PORT \     -Dcom.sun.management.jmxremote.ssl=false \     -Dcom.sun.management.jmxremote.authenticate=false \     -Djava.rmi.server.hostname=IP_ADDRESS \ Define your IP_ADDRESS address and PORT (port should be not used anywhere in that instance) 3. Run the JConsole using following command.     jconsole -pluginpath PATH_TO_JAR/topthreads-1.1.jar 4. Copy "JMXServerManager JMX Service URL" from the wso2carbon logs after restart the Wso2 Server (Eg:- service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi) to the Remote process with the username and password. 5. Under Top Threads tab you can monitor the thread CPU usage.
1 comment
Read more