The LDS approach to the localization process is twofold, detailed here for a typical English-to-Japanese software project.
Evaluation and Team Building
More about LDS translators »
- Development of the original software is generally well advanced by the time LDS is invited to collaborate on the development of a Japanese version. Clients provide us with a product kit for preliminary evaluation and estimate of costs.
- A comprehensive evaluation is cardinal at this early stage and lays the groundwork for a smooth, relatively bug-free localization process during the development phase—we work closely with our clients' engineers to test that the kit's binary architecture builds accurately to the double-byte character environment necessary for input and display of written Japanese. Any problems found are discussed with the client and the product kit is reengineered.
- Project schedule and cost estimates are finalized and project coordinators form a strategic team of LDS translators and support staff. A record of the entire evaluation and proposal phase is archived and all materials returned to the client.
Development and Production
More about project management »
- Initial development centers on generating a master glossary and deploying client-specific translation memory tools, content management tools and style guides. Once we have a complete glossary, it is translated and sent to the client for a terminology review.
- Initial translation focuses on the software's installer, interface, help files and product manual. We conduct a language consistency check on 10% of the translated content and, if satisfactory, a further check on 50% of the material.
- Software engineering and help file engineering begins, along with any DTP work on text graphics and interface. An alpha build of the localized product is then completed and subject to a standard QA* review—terminology and QA amendments are flagged in a database. We then begin a beta build of the product and conduct a language consistency check, a second QA review and an alpha bug regression test.
- Once we have client approval of the updated product build, we institute a rigorous QC** review and carry out final bug regression testing. The fully localized product is then released to the client.