Feature Request: multilanguage keystroke reinterpretation - DonationCoder.com
Welcome Guest.   Make a donation to an author on the site August 28, 2015, 10:07:31 PM  *

Please login or register.
Or did you miss your validation email?

Login with username and password (forgot your password?)
Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.

You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.
The N.A.N.Y. Challenge 2014! Download dozens of custom programs!
   Forum Home   Thread Marks Chat! Downloads Search Login Register  
Pages: [1]   Go Down
  Reply  |  New Topic  |  Print  
Author Topic: Feature Request: multilanguage keystroke reinterpretation  (Read 1922 times)
Supporting Member
Posts: 3

View Profile Give some DonationCredits to this forum member
« on: September 24, 2009, 02:40:01 AM »

The main point of FARR is to launch things ultra-fast, without pausing for mouse clicks or other niceties. However, one item which the user still must do first is to switch the keyboard into the correct language.
For instance, on my computer I have both Hebrew and English keyboards installed. If my active keyboard happens to be Hebrew when I launch FARR, and I try to type in "notepad", what I will get instead is a jumble of hebrew letters ("מםאקפשג").
Google has actually implemented a feature which takes care of this in its search engine: when a bunch of nonsensical foreign language characters are entered, google's search suggest feature automatically calculates what the search term would have been if the same keystrokes had been pressed with the English keyboard active, and it presents search suggest terms based upon that calculation.
I'd like to see FARR do something similar. The basic implementation would go as follows:
- If the characters entered into FARR are not english characters, FARR should calculate the English characters which correspond to those foreign-language keystrokes. The results box should of course first show items which match the foreign characters, but after that it should also display items which match the corresponding English keystorkes.
- As a second stage, you might want to make this configurable to work in the other direction as well: that is, a user might want English keystrokes to also display results for certain foreign-language equivalents. FARR would do this for any of the currently installed keyboards.

Thank you,
Avi Shmidman

Charter Member
Posts: 2,708

see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #1 on: September 24, 2009, 03:56:25 PM »

Here, have a look at this thread. Maybe will it solve your problem as it solved mine... in the mean time...


"I suppose it can be said that I'm an absent-minded driver. It's true that I've driven through a number of red lights on occasion, but on the other hand, I've stopped at a lot of green ones but never gotten credit for it."
Glenn Gould
First Author
Posts: 34,916

see users location on a map View Profile WWW Read user's biography. Give some DonationCredits to this forum member
« Reply #2 on: September 24, 2009, 04:03:47 PM »

This reminds me a lot of the plugin that ewemoa (where is he i miss him) wrote for FARR, called Bakko:

  The main point of this plugin is to provide a customizable means for transforming the main FARR window's text field content.  At the moment, "customizable" means that the user can write a bit of JavaScript to operate on the text field content.
Pages: [1]   Go Up
  Reply  |  New Topic  |  Print  
Jump to:  
   Forum Home   Thread Marks Chat! Downloads Search Login Register  

DonationCoder.com | About Us
DonationCoder.com Forum | Powered by SMF
[ Page time: 0.03s | Server load: 0.11 ]

Share on Facebook
submit to reddit