Troubleshooting XLIFF 1.2 Issues with DeepL in Pairaphrase
If you're translating an XLIFF 1.2 file in Pairaphrase and seeing missing tags, skipped segments, or formatting errors -especially when DeepL is selected as the engine - here’s what’s going on and how to fix it.
What’s the Issue?
While Pairaphrase supports XLIFF 1.2 and 2.0, the DeepL engine works best with XLIFF 2.1 or higher.
When you upload an XLIFF 1.2 file and use DeepL, you may notice:
- Tags or formatting (like links or bold text) are missing in the output
- Some segments are skipped or untranslated
- Segments are out of order or merged together
- Translations fail to match the original layout
These issues happen because DeepL doesn’t fully support the older XLIFF 1.2 structure.
What You Can Do
1. Switch to a Different Engine
To preserve tags and formatting, try using:
- Google Translate
- Microsoft Translator
These engines offer broader support for XLIFF 1.2 in Pairaphrase.
2. Convert Your File (If Possible)
If you're committed to using DeepL:
- Convert your XLIFF 1.2 file to XLIFF 2.0 or 2.1 using a CAT tool like Trados, OmegaT, or Memsource/Phrase.
3. Re-upload with Clean Tags
Make sure your XLIFF file:
- Is encoded in UTF-8
- Has matching <source> and <target> segments
- Does not contain broken or raw HTML inside text segments
Pro Tip:
Pairaphrase’s translation editor automatically validates tags and helps you post-edit safely—so if something looks off, you can fix it before exporting.
Still Need Help?
Reach out to the Pairaphrase team. We’re happy to help review your XLIFF file and guide you through a better workflow.