Software Localization
Should you localize RC files or Binary files?

If you’re a developer or manager of a long-established software company, chances are that you’re working with a development process that was established long ago — long before the release of modern translation tools. That traditional process of localizing Windows RC files is very complex, comprises many steps, and thus increases translation costs.

Why not change?

The reasons for perpetuating this cumbersome process can range from a well-established version control process that people are used to, to not wanting to release the binary file to a translation company for security reasons.

But when you consider that the cost and time savings through translating the binary files may be as high as 40%, there’s a strong case for finding solutions to the stated problems, whatever they may be.

The Current Method of Localizing RC files

The project files that contain translatable text need to be identified and prepared by developers before being sent to a translation company. Quite often the practice is to extract the strings into an Excel file (by manual copy/paste or some automated process) and to send that extract to the translation company.

After translation, the RC files must be integrated by the developers and compiled to enable a review of the translation in the context of the Graphical User Interface (GUI). For each user interface bug found during this process, the corresponding RC file must be found, fixed, and included in a new compile. This process then has to be repeated until the final localized build is produced.

The localization of RC files also requires a strict adherence to the directory structure of the files by the translators. If a file is misplaced or corrupted during translation, many hours may be spent trying to pinpoint the exact source of the problem and correcting it.

When there are thousands of files in question, this can be a very painful process.

Additional time is also spent in finding translators who would be comfortable with the technicalities of dealing with RC files that contain the code and translatable text side by side. This need for a technically proficient translator may lead to a compromise in the quality of the translation if a technician is chosen over a more experienced linguist.

The Case for Localizing the Binary Files

With a binary localization process, the translator works with the compiled modules of the application (.exe, .dll etc) rather than the source files that go into the compilation process. This is possible because modern translation tools (such as SDL Passolo) used by reputable translation companies are able to make all of the text-based strings of the application available for localization while protecting the application code itself from inadvertent change by translators.

This means there are far fewer files involved in the process, and preparation time by developers is dramatically reduced.

After translation, an extra compile is not necessary since the translation and visual editing of UI elements such as dialogs and menus is done by translators directly on the working binary file.

Learn more about reducing your
Localization costs.

How To Reduce Your Localization Cost By Up To 40% - 30-minute Speed-Primer for Translation Buyers

Just complete the form for INSTANT ACCESS to our free report: How to reduce your Localization Cost by up to 40%

Name:
Email:


Top Ten Reasons why to Localize Binary and not RC Files
  • Working with binaries means your changes can be checked instantly
  • No more compiling to see if bug fixes worked
  • No more idle time while QA teams wait for a compile to complete
  • Extra compiler licenses are no longer needed
  • No more explaining build environments to people around the globe
  • No more sending thousands of files to the localization vendor
  • Those annoying phone calls saying you forgot to include a file are finished with
  • .CPP, .C, .H, .RC, .LIBs are all a thing of the past. Now you just need the compiled binary (.DLL, .EXE or .NET, for example).
  • The fear of critical code in the .RC file being changed is gone
  • Dealing with updates is a simple matter of comparing two DLLs, not thousands of text files

Why Use Us

At Academy Translations our people are the key to our success.

All our translators have premium technical qualifications and experience using the new specialized software (such as SDL Passolo).

We translate all text elements of the user interface and ensure that the interface as a whole is adjusted to expanded translated text, and conforms to the target locale’s linguistic, cultural and social conventions as well as standard Microsoft terminology if required.

Of course we also translate software-related content such as printed documentation, on-line content and Help files.

Every localization project is planned and executed by a team consisting of a project manager, localization engineer(s) and localizer(s) possessing native language skills and sound technical knowledge.

Learn more about reducing your
Localization costs.

How To Reduce Your Localization Cost By Up To 40% - 30-minute Speed-Primer for Translation Buyers

Just complete the form for INSTANT ACCESS to our free report: How to reduce your Localization Cost by up to 40%

Name:
Email: