appTranslator helps translate the resources of Win32 and WinCE executables (EXE, DLL, OCX, SCR,...).
YES, EXE-based localization (rather than RC-based) is a damn good idea ! Read why.
In addition to resources translation tasks, appTranslator helps you manage your translations painlessly during the whole life cycle of your application.
Tracking of Items to Be Translated
Thanks to the Items to be Translated view mode, appTranslator displays only the items that needs to be translated. This includes items that are not translated yet and translated items whose source contents was modified.
Tracking of Changes in Your Application
You don't have to freeze your app while translations are being performed. When appTranslator builds a translated executable, it will first re-load the source executable file and take all modifications into account on-the-fly. This way, you can modify both the code and the resources of your application without breaking the appTranslator project. When you modify the code, just re-run appTranslator to generate the updated translations (or add a custom build step to your Visual Studio project !). When you modify the resources, appTranslator automatically detect the changes and modifies the translated resources accordingly.
The Update Source function is used to tell appTranslator that it's now time to incorporate the resources modifications into the appTranslator project. Use the Items to be Translated view mode to easily find what is new and/or modified.
WYSIWYG Translation Editor
Includes Auto-resize of text labels and buttons in dialogs, Dialog Layout Mode allowing manual fine-tuning of controls sizes and positions, Items to be Translated mode that clearly identifies the items yet to be translated, support for proprietary MFC extensions of resources, translation of icons, cursors, bitmaps and non standard resources.
A Version for Developers and a Version for Translators
Translators use a somewhat locked version of appTranslator giving them less rights. Think of it as Admin rights for developers and User rights for translators. This way, translators don't inadvertently break the appTranslator project.
Also, the project manager can easily merge translations into a central repository, thanks to the Import from Translator Edition function (Professional Edition only).
XLIFF Support for Better Collaboration with Professional Translators
The translation agency you work with doesn't want to switch to appTranslator? No problem: Use the XLIFF export and import to produce files their tools can read (Professional Edition only).
Import Existing Translations
If you don't start from scratch, appTranslator can import your existing translated executables.
Don't wait until every single text is translated before you can produce translated versions of your applications. If an item is not translated, appTranslator uses the source language text to produce the output.
Do No Translate Flag
Each translatable item and resource can be marked as 'Do Not Translate'. Using this flag, translators cannot inadvertently modify contents that will be replaced at run-time or contents that the program expects to remain untranslated.
Generating satellite DLLs (a.k.a. resource-only DLLs) using appTranslator is as easy as filling a checkbox !
Satellite DLLs are commonly accepted as the best practice to distribute multi-languages applications. The resources are separated from the EXE and stored in a dedicated DLL. There is one DLL for each translation. Your application loads one of the resource DLLs during start-up according to the user's language preferences.