HighTech Passport

Internationalization and Localization

How we do it! Process and Tools

"I appreciate everyone’s efforts all the way down the chain: from working on getting billing streamlined, great PM support, talented translation and engineering teams. Thanks so much. "

Trish O' Grady, Localization Project Manager, JMP


The Process

1) Preparation

When a new request reaches us, the dedicated project manager assigned to the client is immediately notified. The project files are analyzed in detail to see if all the translatable material is included, and to provide the data for an itemized and accurate cost and time estimate.
After approval of the estimate by the client, the most qualified linguistic team in the project domain is put together by the project manager. Linguists are informed of the project specifics, and a detailed step-by-step schedule is created and communicated to the client.

The project starts with the preparation of “translation kits” for the translation teams.
A language engineer analyzes the provided source files, determines the translatable strings, isolates and prepares them for translation (by adding comments, setting warnings, protecting strings that should not be localized, among other similar tasks). The prepared files are then imported into a translation memory tool and provided to the project manager for distribution to the linguists.

2) Glossary creation, terminology management, style guides

Did you know? Glossaries and Style Guides are the most important reference documents that make it possible to capture and render the specific meaning, style and tone needed to reach the target audience.

Glossaries define the meaning of product-specific terminology for different markets, including locale-specific subtleties.

The lead linguist extracts key terms from the material to translate, create and translate a unique glossary including industry, company, and platform specific terminology.
The glossary is then used to translate the complete software, and may still evolve significantly in the process. Generally, the glossary is stable at completion of the main user interface translation process.
It is submitted to the designated customer reviewer together with a draft of the translated software. After approval by the client, the glossary is used by all members of the linguistic team for the translation of the online help system, of the documentation, and other project components.

With each project, the project-specific glossary is electronically updated, to give linguists access to the latest terminology. This process increases consistency between translations and reduces the terminology research and review time.

Style Guides define the grammar, syntax, tone and other language specifics that translators should use to convey a company’s brand to a specific target audience. The end user should feel that the product was developed for him/her in his/her own language, as opposed to translated or adapted from another culture.

Style guides are used by most companies to create their contents in the source language. They need to be adapted to the different locales. Having worked across many cultures we can efficiently help you create style guides or adapt your exiting ones.

If the expected tone and style are proactively outlined in the style guides, translators and reviewers know up front what conventions they should use. Using the style guide as a reference, reviewers clearly understand what they should focus on when reviewing contents. It will make them less likely to request changes according to personal preference. This approach saves precious time and effort at the critical end of the publishing cycle, and ultimately significantly reduces costs and time-to-market.

3) Processing of localized software files

After completion of the translation and of the editing process (comparison by a second linguist of the source and translated files), the translated files are exported from the translation memory tool, restored to the original format, and validated. The afferent code and the character set are checked. If necessary, the user interface elements are resized, and the shortcut keys are determined for the localized version. Before delivery, the files are again subjected to a technical verification.
The customer and/or HTP will create a localized build based on the localized software resources.

4) Linguistic testing (LQA)

During this step, the localization engineer reviews the localized build with the lead translator of the respective language.Thanks to his/her knowledge of the target audience, the linguist can verify that all details and examples have been adequately adapted to the local culture. This step also allows to verify if everything displays properly on screen.
More details: Testing

5) Draft review and final delivery

The tested software is then submitted to the client for review. The changes suggested by the reviewer are implemented before delivery of the final localized version.


The tools of the trade

To optimize our capabilities to deliver quality localized material, we make use of the latest technology available in the industry. We leverage carefully selected CAT and engineering tools with the expertise and skills of our staff and resources to offer streamlined solutions that reduce overall project time and cost.

1) Platforms

We work on all industry available platforms including:

  • Windows 98, Me, NT, 2000, XP, 2003, Vista, 7
  • Mac OS X 10.0 +
  • OS/2
  • DOS
  • UNIX & Linux

2) File formats

Our software localization engineers use state-of-the-art software tools to process software resources in various formats including:

  • Windows resources (both RC and .NET)
  • Macintosh resources (both classic and OS X)
  • UNIX and Linux message catalogs
  • Java ResourceBundle (.properties)
  • XML, HTML
  • XLIFF
  • RESX
  • PHP
  • .strings
  • Javascript
  • FLA
  • PO
  • Transit PXF
  • Idiom XLZ, WPZ
  • Any proprietary format (like JSL)

3) Localization tools

For the localization of software, help systems, documentation (online and printed), and multimedia components, localization tools help to:
- increase consistency and accuracy in the localized product
- lower the translation costs by leveraging previous translations through the use of translation memory tools
- significantly reduce the cost and the time needed for future updates of a product and for the localization of other related products

  • Trados, SDLX, Passolo (SDL Trados Studio 2007, 2009, 2011)
  • Transit NXT, Transit XV
  • Alchemy Catalyst
  • Wordfast
  • Idiom
  • Systran
  • ProMT
  • POEdit
  • Adobe Dreamweaver
  • Adobe Flash Professional
  • Adobe InDesign
  • Adobe Illustrator
  • Adobe Photoshop
  • Adobe Robohelp
  • Help & Manual
  • WebWorks ePublisher
  • Visual Studio
(C) 1992-2017 HighTech Passport, Ltd.