It is also possible to open and translate text-only resource code files directly in a resource editor, such as the one included in Microsoft Visual Studio, which has all the advantages of translating directly in binary program files. The only risk is using different resource editors or different versions of the same editor may change the structure of the resource files. So, if .rc files are delivered from the publisher which have been created using Microsoft Visual C++ version 4, never open or edit them in Visual C++ 6 or later versions!

It is now more common for translators to work directly on the program files when translating. These .dll files or .exe files can be edited by the translator without the need for compilation.

16-bit applications, .dll and .exe files can be edited using the Microsoft App Studio (included in Microsoft Visual C++ 1.x) or Borland Resource Workshop resource editor. 32-bit program files can be translated in Microsoft Developer Studio (Visual C++ 4.x) or Microsoft Visual Studio (Visual C++ 5.x and later versions), Borland Resource Workshop, or in a software localization tool.

Tip: It is impossible to edit and save 32-bit program files using Visual C++ in a Windows 9x environment. The resource editor needs to be run under Window sNT or 2000.

2. TERMINOLOGY

A software application that runs on a Microsoft Windows platform will probably contain many terms or options which are also available in the Windows operating system or other Microsoft applications. Some examples are standard commands or options such as File, Save, Edit, and Exit or buttons such as Cancel and Apply.

The translation of these terms should be consistent with the operating system which will be used to run the application. To ensure the translations are consistent with the localized Microsoft operating systems and applications, refer to Microsoft's product glossaries, which are available in many languages from the following ftp site: ftp.microsoft.com/developr/MSDN/NewUp/Glossary.

责任编辑：admin