David Deraedt

Welcome to lupo translator online help.

Help Menu

Downloading and installing Lupo Translator

Start Page

About the file structure

Main Translation Interface

The Translation Table

Checking the Translation Progess

About the Translation Memory Database

Using the Option Panel

CSV Import and Export

This project was discontinued.

You can grab the source here.

*** *** *** *** *** *** *** *** *** *** 

Lupo is a set of tools designed to help localizing Adobe® Flex® and Adobe AIR® applications.

As of today, lupo is comprised of three parts :

Lupo Manager, an Adobe AIR application, helps developers extract strings from their source code, manage resource bundles and implement i18n logic in their Adobe Flex / Adobe AIR applications, in a very productive way.

 This project was discontinued.

You can grab the source here.

*** *** *** *** *** *** *** *** *** *** 

With lupo manager, an Adobe® AIR® application, easily extract strings from your source code, manage resource bundles and implement i18n logic in your Adobe Flex® / Adobe AIR applications, in a very productive way.

Following the sneak peek video, I wanted to give you a better, in-depth overview of my new toy, Lupo Flex application Localization Studio. So here's a pseudo real-time video demo of me localizing a Flex app using Lupo Manager, and a feature list.

Real Time Demo

This video shows a case study : I use Lupo to translate a sample Flex ecommerce application in "real time" (not including the actual translation job). The video lasts about 8 minutes, but, presentation constrains aside, internationalizing such a small app shouldn't take more than 2 minutes with Lupo.

Update: Check out Lupo Flex Localization Studio page for more information

I'd like to introduce you to my latest AIR application, currently under development, code-named Lupo.

Lupo is a Flex application Localization Studio. It's a set of tools designed to help localizing Flex / AIR (and to some extends, Java) applications, with productivity in mind.

Why localization? Because it's a great way to increase revenues simply by opening new markets. And it is my understanding that this is the "reach" part of RIAs. After all, what's the point of having a 98%+ player penetration rate, an über ubiquitous desktop/browser/mobile & devices presence, if half of the users can't use the application simply because they don't understand it ?

As promised, here are the powerpoint presentations for the two Adobe eSeminar I just gave at Adobe France.

Reminder : these are in french, folks !

Hope you find it useful...

***

Comme promis, voici les présentations powerpoint des deux eSeminars que j'ai donné récemment chez Adobe France.

J'espère qu'elles sauront vous être utiles...

Hi all ;)

I just got back from San Francisco where I've had a great time. This city is fantastic. I really wish I didn't have to leave, actually.

Back in France, I'll be giving another eSeminar for Adobe on internationalisation in Flex application, next Friday, called Les stratégies de localisation d'une application Flex.

We'll talk about all sorts of things concerning translation and how to prepare your Flex / AIR apps for it.

You can sign up here to attend the seminar.

When talking about application localization, we should distinct two kinds of data :

1. Remote data that come, say, from a database, is dynamic by nature, and should then be localized via your application server logic.
2. User Interface data, however, is very different. Most of the time, it is set statically during development. It is spread all over the application, making it quite difficult to treat as normal "business" data.

Flex 2 deals with application UI localisation via static BundleRessources. There are several limits to this approach.