Categories
Technology

Lost In Translation

A few days back I was talking to someone about natural language processing and the challenges it holds for the future. NLP has the potential to revolutionize the way we interact with computers, and all this may finally become possible with the increased processing power becoming available at cheaper price points. Cloud computing could be a way forward too; a few voice-based search services for cellphones record user input on a cell, transfer it via high-speed 3G data networks, and process it at the service provider’s grid.

Technology, currently, is far from accurate. So until some breakthrough takes place NLP will probably provide us a barrel of laughs. Lost In Translation utilizes BabelFish‘s SYSTRAN-based machine translation to convert input in English to some other language, and then use that output to convert it back to English. The outcome can be quite funny. Sample this (the one I tried out). I entered

Cups of filthy liquid almost, but not quite, entirely unlike tea.

…which became

It is different from brown, almost, but considerably the glass of the impure liquid, completely.

This is when it was converted back and forth between English and Japanese. Japanese is totally notorious because even intonation and slight differences in a word can make a huge differnce in meaning.

Some people might say that this is all a problem with the machine translation model which uses rigid rules of grammar. But statistics-based systems (for instance, the one used by Google Translate) are no better. The same test applied to the same phrase gave me

Brown, but most have been different, quite impure liquid glass is full.

What makes Google better, some say, is the fact that it allows you to suggest a better translation. I disagree and think this is risky. While it may theoretically be better in a perfect world, we know that we don’t live in Utopia. Google’s system once it gets critical mass could be open to gaming by people out to subvert the system or just for laughs. Like googlebombing, thousands of users across the globe may start ‘suggesting a better translation’ for the Japanese word for ‘miserable failure’ as ‘George Bush’.

Until NLP becomes more accurate stuff like Lost In Translation would remain as jolly good jokes. Try it out, and if you get something particularly funny then post it here in comments section for all to see. 😉

Categories
Technology

Enabling Sticky Keys in Ubuntu

Support for Sticky Keys in Ubuntu has been quite sketchy for the past few releases. For the uninitiated, Sticky Keys allows you to hit the Ctrl / Shift keys with their letter combination without having to press them down together. (This is available in Windows too; hit Shift key five times in a row to bring up the necessary dialog box.)

I prefer to use Sticky Keys a lot. It makes typing faster and more accurate (when it comes to capitalization). That’s why I’m kinda partial to KDE-based distros: apart from the interface with lots of eye-candy, KDE’s implementation of accessibility features works. This is not true with GNOME, where there seems to be a bug in at-spi (the Assistive Technology Service Provider). I’ve already filed a bug report for this issue in Launchpad for Ubuntu. For a distro which keeps a separate page on accessibility (shows the Sticky Kets feature there too), it is ironic that this bug has remained for such a long time at ‘Low’ priority.

Anyway, a few days back I figured out how to fix this problem. I was browsing through keys in gconf-editor when I came across the accessibility-related values. Here’s how you can enable Sticky Keys in Ubuntu.

  1. Go to System Tools > Configuration Editor. If it is not enabled, you may need to edit your Main Menu to show this item by going to System > Preferences > Main Menu and doing the necessary edits. You can also launch gconf-editor using the terminal.
  2. In Configuration Editor, go to /desktop/gnome/accessibility/keyboard. Check the box stickykeys_enable. Uncheck the boxes next to stickykeys_modifier_beep and stickykeys_two_key_off. (It’s the second one which you MUST turn off.) Do this step before the next. (Don’t change the order.) If timeout_enable is checked, uncheck it.
  3. Double-click on the timeout field value and change it to some high value like 7200.
  4. Close Configuration Editor without making any more edits. If you change any other value, or open gconf-editor any day later then note that your ‘timeout’ value will be reset to default of 120 seconds.

Methinks the issue (of Sticky Keys) getting switched off every once in a while is because the stickykeys_two_key_off value is enabled even when it has been disabled from Preferences > Keyboard. Moreover, the reset of timeout value is also not expected behavior and is probably a bug too.

Hope this solves the issues for anyone else who wants to use Sticky Keys in Ubuntu (or any other GNOME-using distro)!