A good translation should read naturally and respect the conventions of the target language. One factor which plays a significant role in creating a natural end result is context-aware string translation.

Post-translation text expansion and contraction can significantly impact on the end quality of your localized Mobile app. With text sometimes expanding by more than 33%, UI elements struggle for valuable screen space.

There are 128 Regional Windows Phone Stores currently available for developers to publish their apps to, and 50 languages supported on the Windows Phone 8 device. So, how is an app developer to navigate these device supported languages and regional store languages while maximizing market reach?

Why you should translate your Video: As a result of numerous customer requests, and the ever increasing number of marketing reports heralding video as the must-have marketing tool, we feel it is passed time that we demystify some of the complexity around Video localization.

There are 155 territories currently available for developers to publish their apps to, and 34 languages supported on iOS 6.1.4. Additional language support is expected in iOS 7, not long to wait….

Internationalization, commonly abbreviated to i18n, is not a feature. It is not something you do after you have shipped your product. It is something you need to build in right from the beginning as part of your core design and architecture.

I was pleasantly surprised to receive the latest email from the App Store team at Apple, and especially pleased with the topic and the overall message coming from 1 Infinite Loop.

So, what is localization, and how is it different from translation? Let’s start with the more obvious translation and explain what that is. Translation is the act of taking a word, or phrase from one language and rendering it into another language.

In January we wrote a blog entitled iOS App Localization - Why and Where? giving advice on what language regions to localize your iOS app into, to maximize your market reach.