![]() The tool that creates these useful glossaries helps the localizers look up the translation of English strings within the glossaries, thus providing a consistent translation. (For more information on localization glossaries, see "Localization Outsourcing" in " Establishing Localization Guidelines".) The localization team needs to choose the appropriate localization tool in accordance with the resource-file format used in the project.Īnother requirement of a good localization tool involves its handling of localization glossaries. The localization tool should be able to extract and edit a software project's different resource-file formats, which can include INF, Microsoft Win32 resource files, Extensible Markup Language (XML), and many other file formats. These types of statistics and the percentage of localization work completed help the localization manager track and plan the activities of the localization team. On the other hand, it is also useful for a tool to track resources that have been localized, as well as who did the localization, and other pertinent information. This change can involve a string resource, a font size, or a new icon that has been added to the original product files. Replace graphics and icons with localized ones.Ī tool's ability to track changes that are made to the original resource from build to build is another very useful feature for localizers, since they can see what is updated between builds. ![]() Resize, move, and hide controls as necessary.Change the names, sizes, and styles of the user interface fonts.There are many good localization tools that are commercially available.īefore choosing one, be aware of the various criteria that a localization tool should meet.īesides the ability to translate the string resources within the localization tool, a few other tasks the tool should perform are to: ![]() This original file can be a resource file or a compiled file, depending on the localization team's choice of tools and localization process. Regardless of the localization method you choose, using the proper resource editor tools can make the localization of product resources quick and easy.Įffective localization tools should also be able to create the localized version of the corresponding original file. Most localization tools are capable of handling either or both of these methods. One method is to edit the original resource files before the compilation process takes place.Ī second method is to localize the final compiled binaries of the product, and then to either save the localized resources into the same binaries or into a separate localization database. There are several ways to localize software product files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |