InputSwitcher or national input features

Problem

Working in Leopard, I was faced with the fact that the state of the input language is the same for all applications. At first glance, this is not a big problem, but it is literally crazy. If you worked in xCode in the English layout, and then switched to iChat and changed the language to Russian - what a surprise when returning to xCode, the input language remains Russian. In Windows, the state of the input language is stored separately for each application, and my brain is already very used to this. The situation is bad even in the fact that in Tiger it could be controlled in the settings, but in Leopard there is no such possibility.

Solution to the problem

Googling I found how to partially solve this injustice, and the InputSwitcher will help us in this.

Setting InputSwitcher

InputSwitcher allows us for most applications to make their state of the input language. Installing this application is a bit non-trivial, but not problematic. To do this, we need to perform such steps.

1. Download and install from the image the application SIMBL , which we need for the correct operation of the InputSwitcher.
2. Download InputSwitcher .
3. Copy InputSwitcher.app to / Applications and InputSwitcherClient.bundle to ~ / Library / Application Support / SIMBL / Plugins
4. Now, so that each application has its own state of the input language, you need to run InputSwitcher.app and restart all applications.

How it works

Everything is simple, InputSwitcher remembers the input status for all applications. If you go to another application, then its previous state is activated. But at the same time there is one drawback, it works only for Cocoa applications, so for some applications this trick will not work, for example:

• Finder
• Firefox
• Thunderbird
• iTunes

But the applique does not fall, it just uses the global state of the input language.
')

findings

The problem is partially solved. I have been using this solution for more than a week and no glitches have been noticed. But the most important thing is the bug report in apple, because the more such reports there are, the faster this bug will be fixed. This can be done by bugreport.apple.com .

ps There is no Mac Os X blog, that's why I created it, so everyone is welcome.