We ask for a few basic details so we can send you the requested report and occasionally share relevant insights, resources, or updates related to translation and language technology. Your information helps us provide content that is more relevant to your interests. We respect your privacy and will always handle your data securely. You can read more in our Privacy Policy.
Possibly. From time to time, we may share additional resources, insights, or updates that could be helpful for your multilingual communication or localization needs. You can unsubscribe from these communications at any time.
Free report · Updated November 2026
A two-page brief on the step most translation projects skip: getting source files ready before translation starts. It lists the problems to look for, shows how the workflow changes with the type of file you have, and explains why clean files save money in every language.
Better segmentation in translation tools, better output and less layout work after translation.
Fonts, images and links, master pages, broken sentences, paragraph formats, hyphenation, cross-references and page breaks.
Non-editable text inside images, and how to extract it for translation.
Double spaces, spaces before punctuation and tabs used as indents, cleaned up according to language rules.
PDF-only files, native files from Word to InDesign, FrameMaker and AutoCAD, and texts for sworn translation in Italy.
Problems caught once instead of in every language, and a cleaner translation memory for the next project.
Technical writers, marketing and documentation managers, and DTP teams who send manuals, catalogues or brochures for translation.
It is most useful before a large or recurring project, or when translations keep coming back with layout problems that have to be fixed by hand.
Checking and cleaning the source file before it enters a translation tool: fixing broken sentences, paragraph and table formatting, hyphenation, cross-references and typos, and extracting any text locked in images.
Often, yes. Manual line breaks, tabs used for spacing and inconsistent styles are common in Word files and cause broken segments and layout issues after translation.
A PDF with live text can be converted to Word or InDesign; a scanned PDF needs OCR first. Either way, the converted file is cleaned before translation so that the result can be laid out again efficiently.
It usually does over time. Clean segments match your translation memory more often, and fewer layout fixes are needed after translation, a saving that multiplies with every language.
Get the free report
Fill in the short form at the top of this page to download the PDF.