Windows 16-bit binary files
All 16-bit binary files (*.exe, *.dll, *.ocx, *.ini) that have been created using a Microsoft™ compiler (e.g. Visual C, Visual Basic) or Watcom™ compiler. This allows the localization of older Windows software applications.
Windows 32-bit binary files
All 32-bit binary files (*.exe, *.dll, *.ocx,) that have been created using a Microsoft™ compiler (e.g. Visual C++) or Watcom™ compiler. Visual Localize also supports the substitution of bitmap graphics without the need for the source code!
Windows Ressource files
All resource files (*.rc,) that have been created using a Microsoft™ compiler (e.g. Visual C++) compiler. Visual Localize also supports the translation of .NET Ressource files (*.resx, *.resources) created using C# or VB.NET.
Visual Basic binary files
Binary files that have been created in the Visual Basic development environment. Here, all the texts that are to be translated have to be stored in a string table (with a unique ID for each text phrase to be localized) using the resource editor, which is a component of the development environment.
Binary files for Pocket PC and Windows CE
Allows the localization of mobile applications, e.g. for PDAs or mobile phones.
.NET base assemblies
Visual Localize (NET and PREMIUM Edition) is suitable for translating .NET base assemblies (*.exe, *.dll). The corresponding .NET satellite assembly (*.resources.dll) can also be generated in the associated language directory of your software at the click of a button. The implementation of different languages has never been so easy!
.NET strong named assemblies
Signed assemblies are assigned a delay sign when they are being translated so that the responsible developer can immediately sign the translated version of his software. It is also possible to sign assemblies directly in Visual Localize using the necessary private key (if available to the translator).
DOTNET Framework 1.0, 1.1, 2.0, 3.0 and 3.5
Visual Localize supports DOTNET Framework 1.0, 1.1, 2.0, 3.0 and 3.5, as well as the localization of inherited forms that have been directly derived from the “Windows.forms” class.
.NET WPF Files *** NEW ***
Visual Localize supports the localization of Windows Presentation Foundation WPF files containing binary XAML resources.
Key pair files
Visual Localize allows the translation of key pair files (e.g. TXT, INI or CSV files) with the following syntax:
[unique identifier][separator][text for translation]
Java resource files (*.java, *.properties)
Java resource files are help texts in which the translation phrases from a Java application have been pooled.
Online help files (*.chm compiled help files)
Visual Localize allows the translation of compiled online help files (*.chm) that have been created using RoboHelp X5, for example. The compiled help file is loaded into Visloc together with the associated project file (*.hhp), and the individual topics are then translated in an HTML editor, which features an additional preview function.
HTM files (*.htm, *.html)
Visual Localize allows the translation of HTM files without the corresponding stylesheet file. The files are translated in the familiar WYSIWYG environment, but without any of the formatting.
Trolltech™ QT Language Files (*.ts)
Visual Localize allows the comfortable translation of Trolltech™ QT Language files (*.ts). All known translations will be automatically reused to minimize the translation effort. In addition to this you will be very flexible to reuse all your translation for different source files or translation memory tools.
Any XML tags or attributes can be translated. To take individual structures into consideration, the XML structure that is to be translated can be freely configured in an easy-to-use wizard.
MS database engine
The following Microsoft™ databases can be translated using Visual Localize:
- MS Access databases
- MS SQL Server
Texts for translation are extracted from the database and then reimported. This eliminates any risk of unintentionally corrupting the database structure.
across® & Trados® Connector (included in PREMIUM Edition)
Using the across® or Trados® Connector, Visual Localize can be connected to the translation memory of the across® Language Server or the Trados® Workbench. As a result a simultaneous translation with several translators can be done. Further the translation memory can be reused in a later step to translate all additional product materials (like manuals, product sheets,..)