
Software Translation with Resource Files
The cost of a software translation is different from format to format and calls for a customised approach. We advise translating resource files.
The format of the translation should be checked first. It can be one of the following:
- compiled Windows programs (EXE files)
- RC files (resource files, e.g. from compiled Windows EXE)
- online Help files (Word- or HTML-based)
- database applications
- XML
- websites
- specific software formats (ADA, Basis, Cobol, C, C++, JavaScript, Pascal, Perl)
For database applications and complex formats (not specified above), an export into CSV or XML formats makes sense in order to keep the cost manageable. If EXE files (executable files) are not involved, the encryption of the source language and the target language must be checked in advance.
Whenever possible, raw data or resources should be resorted to and not executable programs that must first be "extracted", which is time consuming. If resources are being translating directly, the project manager knows which part of the project the translator actually has and what may still be missing. In case of subsequent changes to the software or to the translation due to updates, the entire software does not need revising, just the individual resources.
For all standard formats, there are tools that protect encryption and keep the translated texts editable. When special formats are involved, Transline's EDP specialists with the collaboration of you the customer make sure to protect the program code.
Transline uses localisation software that simulates the program run to monitor the software context over the course of the translation. In this regard, even the size of the command buttons, for instance, is simulated and can be adjusted by the translator if required. Depending on how the resource is structured, though, this may not always be possible or not to the same extent. Then in some cases it might make more sense not to process the RC files, but rather the compiled file using a special localisation tool. In other cases there is simply no localisation tool capable of satisfying all the requirements and special actions or smaller script designs are required to be able to localise the software correctly.
This is why Transline employs software experts and programmers who, as your direct contacts, are acquainted with and resolve translator-specific problems and understand the customer software. When you as the customer are already working with a localisation tool, Transline can adjust itself accordingly to the particular format.