Overview

appTranslator helps easily manage translations of your Windows applications. It provides a resource translation editor and keeps track of the translation work items. appTranslator helps the developer separate development work and translation work. It helps the translator by providing an easy-to-use environment therefore eliminating the hassle of textual data transfer back and forth from Visual Studio to Excel or Word.

Using executable files as translation input makes developers' life MUCH easier

Since appTranslator's work is based on the executable files rather than on the resource scripts, the developer is freed from the tedious housekeeping involved in managing translated projects and .rc files.

Visual Studio is not cluttered with the different language versions of each project. appTranslator keeps track of it all and lets you, the developer, concentrate on your job: Developing the best applications.

Read more about common misconceptions related to using exe file-based localization and translation.

appTranslator Professional Edition helps developers and translators work together

When the app reaches a point where it's worth sending it to the translator, all you need to do is to import your executable(s) into a new appTranslator project and send a copy of this appTranslator project file to the translator(s).

The translators use appTranslator Translator Edition to translate the application. If the developer agrees, they can even create translated EXEs to test their translation. When they are done, they send the appTranslator project back to the developer.

The project manager merges the translation back into the main appTranslator project file. If you added or modified some resources while the translators were working, appTranslator detects the changes and takes them into account. You can immediately see what is new and modified. At any time you can decide to make a 2nd round of translations to take your last changes into account.

Professional translators who prefer to work with their favorite tools can take advantage of appTranslator's XLIFF export function: Instead of using appTranslator Translator Edition, translators may decide to receive an XLIFF file, allowing them to work with their favorite XLIFF-compliant translation editor.

No longer wait until the last minute! And don't freeze your app! appTranslator allows iterative work

This is one cool feature of appTranslator: The developers need not freeze their apps while waiting for the translations to be delivered. appTranslator supports iterative work: You no longer need to wait until your app is finished to have your translation work started. The translators can start working while you are still developing your app !

appTranslator also makes translators happy

Thanks to the WISYWIG editor of appTranslator, translators no longer have to make blind translations. They see the texts in their context. Needless to say this highly improves the quality of the translation.

The Items to be Translated view mode shows exactly what still need to be translated. Or the items whose source text was modified, hence requiring an update of the translation: No longer wonder what was changed. Never browse through lists of texts again, tediously looking for differences in source items contents!

Translating MyKillerApp 2.0 is so easy thanks to appTranslator

A software product is not static. It keeps evolving over time. It's cool to have MyKillerApp 1.0 translated. But what happens when Service Pack 1 is released. And when version 2.0 is about to hit the market ?

Simple: Just click the Update Module Source menu item and appTranslator will update its database with the new contents of your app. Of course, all unmodified resources translations are preserved. The new and modified items will be very easily identified using the Items to be Translated view mode.

Translating successive versions become a simple incremental translation job: Just translate the new and modified items.