Tuesday, June 17th, 2008

Adobe AIR v1.1 Released, Enhanced Support for Internationalization

Category: Adobe

<p>Adobe AIR, the SDK & runtime which has become the popular choice for building desktop-enabled web applications, has been updated with enhanced support for internationalization. With AIR v1.1, Adobe has bumped the number of supported languages to ten including Japanese, Chinese, Russian, Spanish & Brazilian Portuguese and included support for double-byte keyboard input.

Other notable enhancements include:

  • Support for 64-bit editions of Microsoft Vista
  • API enhancements to report disk space availability
  • Ability to determine if the OS can support transparent windows

The full release notes for Adobe AIR v1.1 provide more details about the features and changes in this update.

Adobe AIR 1.1 FAQ (includes new features and sample bug fixes)
http://www.adobe.com/go/air1-1faq

Article: Building a multilingual HTML-based application
http://www.adobe.com/devnet/air/ajax/quickstart/multilingual_air_apps.html?devcon=f3b

Fresh RSS Reader Sample Application & Source Code
Localized to 11 languages
http://www.adobe.com/devnet/air/ajax/samples.html

Adobe AIR 1.1 SDK
http://www.adobe.com/go/getairsdk

Related Content:

Posted by Rey Bango at 5:45 am
10 Comments

++++-
4.1 rating from 31 votes

10 Comments »

Comments feed TrackBack URI

I assume you mean Internationalization?

Comment by codedread — June 17, 2008

Additional Adobe AIR links that might prove helpful:

Adobe AIR 1.1 FAQ (includes new features and sample bug fixes)
http://www.adobe.com/go/air1-1faq

Article: Building a multilingual HTML-based application
http://www.adobe.com/devnet/air/ajax/quickstart/multilingual_air_apps.html?devcon=f3b

Fresh RSS Reader Sample Application & Source Code
Localized to 11 languages
http://www.adobe.com/devnet/air/ajax/samples.html

Adobe AIR 1.1 SDK
http://www.adobe.com/go/getairsdk

Rob Christensen
Product Manager, Adobe AIR

Comment by adoberob — June 17, 2008

@codedread Yep you assumed correctly. That’s called a late night posting session :P

Comment by Rey Bango — June 17, 2008

@Rob: I updated the post to include the links you posted in your comment.

Comment by Rey Bango — June 17, 2008

They updated Webkit! Unfortunately it looks like the build they used is significantly behind Safari 3.1. Now to figure out how to update Flex for AIR 1.1…

Comment by eyelidlessness — June 17, 2008

@eyelidlessness: If you are using Flex Builder, Matt Chotin has written a great article that describes how to migrate from 1.0 to 1.1: http://www.adobe.com/devnet/flex/articles/flex_air1.1.html?devcon=f2

Comment by adoberob — June 17, 2008

Thanks, I figured it out.

I’m disappointed that they didn’t use a newer Webkit build. :( I have read their position on it, but clearly at least the Safari 3.1 release is not only stable, but a better candidate for AIR.

Comment by eyelidlessness — June 17, 2008

“the popular choice for building desktop-enabled web applications”

..unless you’re targeting Linux.

Comment by patspam — June 17, 2008

@eyelidlessness: I hear you. The next version of AIR will include a much newer version of WebKit.

@patspam: We have a Linux alpha available on our Labs website. We’re making excellent progress on a beta that will be near feature complete. It’s an important priority for us. Stay tuned!

AIR for Linux alpha:
http://labs.adobe.com/technologies/air/

Comment by adoberob — June 18, 2008

@adoberob: Thank you very much for responding to the concern, I’ve seen it posed in a variety of places, and Adobe in general has a paucity of details about how Webkit is updated in AIR in their own materials.
¶
Can you tell us whether “a much newer version of Webkit” means you’ll be targeting builds newer than the current release (for instance, a stable release of SquirrelFish)… or a general timeframe in which we might expect such a release? This information will be very helpful for what kind of expectations to have about in-development applications and the environment they’ll be expected to live in, and will allow us to target future releases by using Webkit builds for most HTML/CSS/JS purposes.
¶
Again, thanks for your input.

Comment by eyelidlessness — June 18, 2008

Leave a comment

You must be logged in to post a comment.