Start with the Native files for Translation Projects
Posted on Tue, Dec 22, 2009
BLOG POST BY: Vanny, Quote Manager, Translation Division
____________________________________________________________________________________________________________
As Quote Manager for the translation services division, I talk to many customers throughout the day about their new document or website translation and localization projects. I educate our clients and prospects on the process and consult with them to provide the most cost effective solutions. In some cases for those who are new to working with languages, it may be a bit daunting how involved the process can be.
Based on my experience working at CTS LanguageLink, it is commonly assumed by those new to translation that it is simply a task of translating text in a given file and turning around a foreign copy. As I've learned in my time here, there is much more to the process of translation then simply translating the written text.
There are so many variables to consider such as text expansion, context, formatting, font issues, file format (Portable Document Format file versus native file), etc., all of which has to be taken into consideration when putting together an accurate translation quote.
All of this brings me to today's topic, why native files are needed (and preferred) for translation and are much more time and cost efficient to work with from the get go.
Oftentimes I receive a Portable Document Format (PDF) file for a quote request, which will suffice for the purpose of quoting. But in order to complete the translation project, the native file is required before any translation can begin. Simply put, Portable Document Format (PDF) files are viewable and printable on any platform and are not "live" files, which makes it very limiting to complete any text and formatting modifications, edits or changes. With that said, PDF files are not feasible for translation; however, the native "live" file, that the PDF file was created from, will allow for text and formatting modifications, edits or changes. Therefore, it is always best, and will at some point be required, to work with the source or native files for translation.
Here are my Top 5 cost benefits for providing native files from the start:
1) Providing native files will save time and budget from having to recreate the English template for translation.
2) It makes it easier to tackle the formatting challenges that text expansion, double-byte languages, left-to-right languages, embedded graphics may pose. Without seeing how files and graphics have been created and built in the source layout program (In Design, Quark, Pagemaker, Illustrator etc. ), we are not able to accurately quote the formatting time required.
3) An accurate word count performed by our translation memory TM software program can only be done with native files. Our TM will identify repetitive text within a document, which a discounted leverage text rate can be applied to.
4) The TM will develop a "memory" of units of text already translated for subsequent or updates projects. This translates (no pun intended) into minor revision costs and leverage text rates.
5) Time savings can be significant. Often we are waiting on files to get a project started. When native files are actually made available, the project scope may have changed significantly compared to the "ballpark" estimate.
These are only a few cost saving tips to help you maximize your budget. Stay tuned for more cost saving tips for your translation projects! Just remember that the native files are the best format for quoting and translation, with the PDF just for reference. ~ Vanny
More questions? Email me at blog@ctslanguagelink.com
For more information about our Translation process, visit: http://www.ctslanguagelink.com/translation_process.php