- Posted by Stephen Whiteley
- On 11/08/2012
- Quality, Speed, translation memory
Most projects are “urgent”. Sometimes this is entirely justified, as in the case of an imminent trade fair, client presentation, website launch, or contract signing. By contrast, some deadlines are entirely unjustified, often because they have been randomly set by an unrealistic boss, or because someone has left it till the last minute. Either way, urgency is bad for any type of project, not least translation and documentation. Rushing to get something finished increases the probability of stress, errors, and, most importantly, less-than-optimal results.
Generally speaking, the earlier in the documentation process you think about translation, the better. Typically, people think about translation only when the source language is complete and finalised. At this point, we have probably thrown away the possibility of saving considerable amounts of time and money. This is particularly applicable in projects with non-standard formatting requirements – basically, anything other than Office applications, such as HTML and other web formats, QuarkXpress, Adobe InDesign, Adobe FrameMaker, etc.
QuickSilver goes above and beyond the call of duty and foresees your future needs. For example, if we know that you update your catalogue every quarter, we will create a project-specific process which will automatically flag the segments that need to be translated every time, instead of having to re-translate the entire document. This process not only saves time and money but builds in consistency across the board and eliminates the possibility of errors.