Skip to main content

Blogging in telugu

Wow.. This is wonderful.. Do you know it is as much easier to write in Telugu (or other Indian languages) in any application (not just Orkut)

Theory:

There are many ways of doing it. First try to understand how it is done. The direct way is to get yourself a Telugu keyboard (or a simulator in your OS). This way you will have a steep learning curve. This is also called Inscript. Though this is hard on your mind, its good on the output - I mean - since there will be no conversion, it is the perfect way to write in digital Telugu.

For the other not-so-professional-about-the-telugu-text-YET people (like me), There are two other easy ways. My favorite is RTS (Rice Transliteration Scheme). Another is WX. RTS is a little more standard and some what comprehensive for most phonetic languages. WX is another notation from IIIT - its much easier to learn with lesser rules. As they say - no pain no gain - WX offers lesser "Strict-ability" on achieving correct text.

Both these work on what is called as KeyMap translations. What it does is, it translates keys pressed in a sequence into lexical units and converts them to Unicode Telugu characters. Folks with familiar with the aforementioned orkut's java script feature would see the point. Well there are online tools and Installable tools too. You can quickly start writing in telugu (using RTS) from this application. Once you get a hold of RTS, which by the way is a lot of fun- You can also install this one(I dint see if this was actively supported, but the version available is good enough). Here is a detailed lookup of how RTS is KeyMapped. You can also learn more about how google offers these in its own services.

Troubleshooting:
If you have issues - You can start here.
There are some issues in Firefox that renders telugu text improperly. Here is one solution.

If you want you can get some telugu fonts here

Leave comments in Guestbook

Popular posts from this blog

Javascript: Convert Strings to Binary (and representing in a nerdy way!)

I follow those GoogleDevelopers Videos . Sometime back, in one of the presentations on GoogleIO, there was this interesting string of dots at the bottom of each page of the presentation . They looked like random big and small dots. A similar bunch of dots were also on the T-shirt of a presenter was wearing in another presentation . While it seemed something in the pattern, I could not find what it was. Finally, another presenter cleared the matter that those dots are just binary representation of "GOOGLEIO" (So much for advertizing Google IO, Impressive!). So I wanna do it. Takes me back to days of those DSP classes at school. Nerdy me had to churn some old brain cells. I remember those first programming language classes in Pascal and C when you were asked to do fibonacci series and converting a binary string to ascii codes. That *experience* came handy here: Check it out! Text to Binarize: For those who came to copy the javascript code to convert string to binary,

MySql Copying Table Structures.

Some times you need to copy only table structures across databases. This article describes two ways of doing it. If the whole database schema need to be exported, mysqldump is very effective. A --nodata flag will dump all tables' schema. Like this. mysqldump --nodata -p -u username databaseName But if you want to copy a specific table, individually, you could use "create table like" feature. You could create it even from a different database. However it must be on the same mysqld instance. Like this. create table newtable like oldtable; --Or from a table in other database create table mytable like otherdatabase.tablename;

javascript maxlength for textarea with \r\n breaks in java (esp Firefox)

Textareas allow new lines to enter. These are represented by \n (1) or \r\n (2) characters. But when you save to DB you have a limit to certain length of chars. There is no maxlength attribute in HTML that will stop you from entering data. This is generally acomplished by Javascript. You do a onkeyup hook and stop event or trim after textarea.value.length > maxlength. There are many other solutions out there.. But.. Here is the problem that most of those solutions overlook, How do you deal with the count on \n and \r\n representations. Lets first see how it matters. If the text entered has new lines, the length is calculated differently in Firefox and IE. When you enter a Text like 01234 567890 You expect the textarea.value.length to be 11. (10 chars + new line).On the backend, however, java would recieve it as 12 chars (10 chars + \r\n) (this is irrespective of FF or IE). So you are effectively saving 12 chars to DB. Worse yet, IE seems to figure textarea.value.length as 12 (