Software Localization

You can translate binary files such as EXE, DLL, and Resource Script files more or less the same way you translate standard documents: The source document is displayed in the Source View and you do the translation in the Target Editor.

However, in addition to the text itself, EXE, DLL, and resource files may also contain information on shortcut keys that have been set and on the graphical display of dialog elements and buttons. In order to guarantee that the result of your translation is a localized file or application that completely reflects the content, graphical presentation, and format of the source document, you can take care of this from the outset in Across - and you will be working in the so-called WYSIWYG mode (What You See is What You Get). This means that you can see the graphical representation of the localized application while you're translating.

  • In the range of software localization, Across supports the following formats:
  • Standard Windows resources in binary format* (EXE, DLL, OCX, NLS, SCR, CPL)
  • Standard Windows resources in source text format* (RC, RC2 and DLG)
  • Microsoft .NET resources in binary format* (EXE, DLL (.NET assemblies) and RESOURCE)
  • Microsoft .NET resources in source text format* (RESX)
  • and other formats that can be a component of software localization (Java Properties, MSI, MC and PO as well as HTML and XML)

For resources/formats marked with an *, Across supports the processing in WYSIWYG mode.

Apart from the .NET localization of Windows Forms, Across also supports the localization of resources of the Windows Presentation Foundation (WPF) graphics framework. The respective resources are localized as RESOURCE.DLL files.

When projects with .NET files are created, Across will automatically recognize whether these are "conventional" files or files developed under .NET and process them accordingly.

A number of QM criteria assist you in carrying out a flawless localization.

crossView lists the elements to be edited by the type of segment to be translated: depending on the source document, shortcut keys, dialogs, menus, string tables, and version information are distinguished.

Templates help you to work more efficiently and at the same time, to ensure a high quality standard: you can determine in a template that strings, shortcut keys and version information, which are often not to be translated, are not displayed in crossDesk. This procedure saves time and eliminates a possible error source.

Software localization templates can be created under Tools > System Settings > Document Settings > Windows Resources or .NET Resources.