I just updated my Air 1.2 (iirc) to 2.0 and noticed (in TweetDeck, in case that's not an Air problem) that neither Dead Keys nor Compose works.
For example, when I want to create an ä I type: <Shift>+2, a. In Air, I don't get an ä but just an a (Same with é, which is ' + e, gives just an e without accent)
To create ™ I type <Compose>, t, m, but in Air I get just m.
This works flawlessly in all other applications.
(what does work is generating € using <AltGr>+e)
Since I type quite a lot of these special characters, this bug renders all Air applications unusable.
Is there some setting I could change, to restore the 1.x behaviour?
So, we've been waiting for a month now and by "we" I mean almost every "customer" that relies on graphical signs to communicate on their native language: Brazil, Argentina, Uruguay, Paraguay, Chile, Colombia, Bolivia, Mexico, Spain, and so on....
The feeling is that we were left behind, so now we just can't use any AIR application, which sadly resembles the lack of a decent, unified Flash player for Linux distros.
So, c'mon guys, for a company of the size and popularity of Adobe this problem should already been solved. Give us a date, at least, so we don't have to keep coming back to your site to check if a new version is out. This is not only a PITA, but it's humiliating and depressing.
It's time for Adobe to show some respect to Linux/Latin users.
Unfortunately, I don't have a hard date I can give you. A release of AIR requires coordination between multiple product teams. However, if everything goes to plan, it should hopefully be just a few weeks (early August).
Europe, Middle East and Africa