Developer Tools

The Hidden Cost of Manual File Extraction Rules

Before you can translate a file, you have to extract the translatable content from it. This sounds simple until you encounter the reality of enterprise file diversity.

A single client project might include Word documents with tracked changes, Excel spreadsheets with formulas in some cells and translatable content in others, InDesign files with locked layers, XML exports from a CMS with custom namespaces, JSON files with mixed translatable and code elements, and PowerPoint decks with content in text boxes, notes, and embedded charts.

Beyond DeepL: Why LLM Translation Changes Everything

DeepL is good. So is Google Translate. So is Microsoft Translator. The neural machine translation revolution of the mid-2010s genuinely improved translation quality, and these engines handle straightforward content remarkably well.

But they all share a fundamental limitation: they translate text. You give them source content, they give you target content, and that’s the entire interaction.

Large language models do something different. They understand context, follow instructions, and adapt their output to requirements. The distinction sounds subtle until you see it in practice.

Why Your Translation Files Keep Breaking Mid-Project

The email lands mid-project: “The translated files won’t open properly.” Or worse: “All the formatting is gone.”

File handling failures are among the most frustrating problems in localization. The translation might be perfect, but if the final files don’t work—if they won’t open in the original application, or they’ve lost their formatting, or the content appears corrupted—the project has failed.

These failures aren’t random. They follow predictable patterns, and understanding those patterns reveals how to prevent them.

XLIFF: The Universal Translation Standard Your Team Should Know

Every translation tool has its own internal format. Phrase uses one structure, Lokalise another, MemoQ another still. When you need to move content between tools—or work with external translators who use different tools—these incompatibilities create friction.

XLIFF exists to solve this problem.

What XLIFF actually is

XLIFF—XML Localization Interchange File Format—is an OASIS standard designed specifically for exchanging localization data between tools. Think of it as the PDF of translation: a format that preserves content and structure regardless of what tool created it or what tool will use it.

Stop Losing Formatting in Translation: The Placeholder Revolution

The translated document arrives. You open it. Immediately you see the problems: bold text that’s no longer bold, links that point nowhere, bullet lists that became plain paragraphs.

The translator didn’t make these mistakes. The translation itself is fine. What failed was format handling—the tags and codes that carry formatting got stripped or corrupted somewhere in the process.

This happens constantly in localization workflows, and it’s almost always preventable.

Why formatting breaks

Modern documents store formatting as codes embedded in the text. A bolded word isn’t just “stored as bold”—it’s wrapped in tags:

From Scanned PDFs to Translated Docs in Minutes

The document arrives as a scanned PDF. The text you need to translate is locked in images of pages, not extractable text. In a traditional workflow, someone would need to retype the entire document before translation could even begin.

This scenario plays out constantly. Legacy documents, signed contracts, historical records, printed materials that were never digital—all exist only as scans. The need to translate them doesn’t go away because they’re inconveniently formatted.