Lupo Manager

 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.

 Lupo Manager is part of the Lupo Flex localization studio.



 Tour  | ReviewsDownload FAQ  | Help  | Get Satisfaction !



Tour: introducing lupo key features

Video made using early alpha builds. Current versions offer a significantly improved experience.

This div will be replaced


Code Extraction

  • Parse ActionScript and MXML code using a smart search engine to find the strings which should be localized.
  • Automatically extract those strings by creating the corresponding key/value pair in your properties files
  • Replace extracted strings by ActionScript code, at the same time you extract them.
  • You keep complete control over the key naming and code generation. 

Bundle Management

  • Forget syntax errors: edit key / value pairs in a super simple spreadsheet, and preview the resulting properties file.
  • Easily search, filter, sort your bundles contents.
  • Key refactoring : renaming a key will rename all instances of this key in every locale file of the related bundle.
  • For values representing embedded image files, such as icons, it displays the actual icons, not just the file path.

Developer / Translator Workflow

  • Agile and simple workflow: create a translation project, send it to your translator, and import it back when (s)he's done.
  • Export / import simple CSV files or complete translation projects for Computer Aided Translation (CAT) tools
  • Choose which language(s) to include for translation, and which other language(s) should be "read-only"
  • Importing lets you preview the resulting translations files before merging them to the actual source code.

Code Generation

  • Compiler command lines generation, such as Adobe Flex Builder ® "additional compiler arguments"
  • AS3 and MXML code generation : easily implement the actual i18n logic in your application. Resource Bundles metadatas, an Array of available languages, and other advanced tools to create more sophisticated classes encapsulating your bundles data.

A focus on productivity

Now, we all know that the real question is: Can lupo really help you be more productive ? Here are the results of some tests I ran :

  • Small Flex application (lita): about 5000 lines of code / 35 classes => 105 strings extracted. Total i18n time : 6 minutes.
  • Medium Flex application (client work): about 10k lines of code / 53 classes => 200+ strings. Total time: 11 minutes.
  • Big Flex application (client work): 20k+ lines of code / 100+ classes => 350 strings. Total time: 21 minutes.

If you've ever internationalized / localized a Flex application before, you probably realize that these results are quite explicit. Our beta testers, using early builds of the software, noted a productive boost which was about 40% to 75% percent. From my experience, the release version of lupo should be closer to a productivity gain of 100%. In other words, you can expect to be twice as fast as you would be doing the tedious and very error prone manual work. And we're just talking about string extraction here...


If you're still not convinced this tool is for you, check the frequently asked questions, and take a look at our online help which will guide you through lupo's various features in more details. Note that because no tool is perfect, we also maintain a known issues list, and use Get Satisfaction to keep in touch with lupo's users.


Reviews & mentions

Lupo manager review on Refreshing apps

Lupo on Code Moi un Mouton (french)

Lupo article on the Adobe AIR developer center



Please upgrade your Flash Player This is the content that would be shown if the user does not have Flash Player 6.0.65 or higher installed.

Install your software by clicking on the install badge above, or download the AIR file here.





Q: I'm confused... What's the difference between lupo manager and lupo translator ?
A: lupo manager is a tool intended to be used by Flex developers, so that they can create bundles, implement i18n, and properly work with translators. Lupo translator is a separately sold AIR application, intended to be used by translators to actually translate the data created by lupo manager (or another software).

Q: What ? You mean that I can't use lupo manager to actually translate the strings it has extracted for me?
A: You can use lupo manager to translate your bundle data since lupo translator main interface is integrated in lupo manager. Lupo translator is actually simplified version of the Bundle Translation tab. In other words, lupo manager can do anything lupo translator can do.

Q: What are the requirements for installing lupo manager & lupo translator ?
A: lupo manager and lupo translator both run on the Adobe AIR runtime, therefore it is compatible with Windows, Mac OS and Linux Systems. You don't have to wonder if you have Adobe AIR installed on your system, it will be automatically installed if you don't.

Q: Is lupo manager compatible with Flex N ?
A: lupo manager is very independent from the Flex SDK, you can use it with any version of Flex. The default values provided are thought with Flex 3 / Flex 4 in mind, but you can change that anytime you want.

Q: Can I use lupo manager if I don't use Adobe Flex Builder as my primary IDE ?
A: Absolutely, lupo manager is 100% independent from any IDE.

Q: Can I use lupo manager to localize Adobe AIR projects ?
A: Yes, lupo was designed to help localizing flex apps whether they run in the browser or in the Adobe AIR runtime.

Q: Can I use lupo manager to extract Java files ?
A: Yes. Theorically, you can extract any source file since you can extract any text file. However, you'll want to modify the search engine & code generation patterns via the preferences panel. Keep in mind that lupo was primarily designed to localize Flex apps. More java specific support might be added in the future.

Q: How can I know if lupo supports feature X?
A: The online help can help you get to know more deeply how lupo manager works.

Q: I have a feature request. Where can I share it ?
A: You can use lupo manager GetSatisfaction page for that.

Q: Localization aside, can I use lupo to have redactors edit the text of my application ?
A: Yes, you can use lupo not only for localization, but also as a simple way to externalize strings and assets out of your application. This way you can have, you can have your text edited by people who can actually write proper english :).

Q: Why lupo manager itself isn't localized ?
A: Because it is intended to be used by developers, and developers are supposed to be able to read basic computer english.

Q: I have a problem. Is there some kind of help?
A: Yes, the online help can be found here.

Q: I have found a bug or problem. Where can I report it  and find help ?
A: You can use lupo manager GetSatisfaction page for that.


Translation / Workflow

Q: Can you help me find translators?
A: Maybe. Please contact me via email.

Q: I'm a translator. Can you help me find a job?
A: If you're a professional translator and you do have some experience with software localization, yes. Please contact me via email.

Q: I'm lost in localization. Can you help me get the job done ?
A: Yes, I also do consulting and development. For more informations, please contact me via email.

Q: Do I have to use american English (en_US) as the master language ?
A: No, but English is strongly recommended. It will also be easier to find translators this way.

Q: Do my translators need to use lupo translator to work with lupo translation projects?
A: No, translators can use any CAT tool or properties editor. They can even use CSV editors since lupo manager can export and import this file format.



Adobe, the Adobe logo, Acrobat, ActionScript, Adobe AIR, Flash, Flex, Flex Builder, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.