Technology Review and Architecting the Workflow

In beginning a new project, identification of the appropriate localization technologies to be used and creation of a workflow that clearly illustrates when and where those technologies will be brought to bear form a key driver of the project's success.

File Type Review

We will examine what file types we can expect to receive from different parts of the enterprise. For example, Quark files may come from Marketing, XML or database files from the Web group, MS Word files from the legal department, etc. Based on the nature of the content, we will then decide on the best method for content delivery. Often a GMS product, or custom portal can facilitate and automate the necessary exchange.

Translation Memory Selection

Translations.com has extensive experience working with all major translation memory software and can integrate with an existing tool or offer advice on which tool would be the most appropriate to use given the client's needs. Additionally, Translations.com can help creating translation memories from an already translated copy.

Define Client Review Parameters

We will then work with clients to define review parameters, which establish a feedback loop. That said, we also appreciate that our client's most important asset is their time. With that in mind, we will find a solution involving minimized client involvement, but maximized information flow to ensure client satisfaction.

Define Localization QA Parameters

Localization QA is essential to a project's success and, if performed successfully, dramatically reduces the number of bugs found during final testing, where detecting and fixing bugs takes longer. At Translations.com, using our "Transposition" QA process we able to do just that, guaranteeing the delivery of error free well formed files. In addition to this, we also need to take into account any client-specific parameters such as file encoding, character escaping, line break format, naming conventions or Unicode BOMs. These, and other such parameters are normally defined upfront during a technical kick-off call for any given project.

Once we have defined all of the above, we will document the workflow and clearly outline each step in the localization process. The end result is that both Translations.com and the client have a clear visualization of each step in the localization process, where accountability lies for that step, and the technology being used to make that step as seamless and automated as possible.