Pre-localization engineering – Our localization engineers perform source build and source file analysis. The localizable file list is compiled. New or updated automation and build scripts are written, any early questions/concerns are addressed, any suggested changes needed from file type or content for localization/internationalization are also flagged at this time. Preliminary word counts for project costs are also calculated.
Localization kits – A kit for each language is created. Translatable files are placed in to the appropriate translation tool, previous translations are leveraged, non-localizable strings are identified and locked, and a word count analysis is performed. Client instructions are added to the kit and sent to our qualified translators.
Post-localization engineering – Our engineers perform verification and quality checks on completed translations to detect and fix localization issues that have been introduced to the translated files. We also update the client’s main translation memories with the latest translations.
Software building – We can also process files through our build pipeline to create software builds for testing and bug investigation/regression purposes. Build scripting can be used to automate the process as much as possible.
Bug fixing – We log, track and fix bugs and defects, our online bug tracking system to share the results with our clients.
Online help engineering – We’ve localized a variety of online help systems including HTML- or XML-based help by using a wide variety compilation tools such as Help Workshop, Webworks, RoboHelp & MadCap Flare.