How to Handle XLIFF Files in Pairaphrase
If you’re experiencing problems with your XLIFF file in Pairaphrase—such as missing tags, broken formatting, or jumbled segments—here’s how to resolve them quickly.
Common Issues:
- Tags missing or moved in translated output
- Segments appear out of order or are skipped
- Formatting like line breaks or links isn’t preserved
- File won’t import or translate at all
Quick Fixes for Pairaphrase Users:
1. Use a Supported XLIFF Version
Pairaphrase supports:
- XLIFF 1.2
- XLIFF 2.0
Files using other versions or custom formats may not import correctly.
2. Validate Your XLIFF File
Before uploading:
- Make sure your file is UTF-8 encoded
- Check that every <source> has a <target>
- All tags must be properly opened/closed
Malformed tags or unsupported elements can cause issues during import or translation.
3. Preserve Inline Tags
Pairaphrase retains formatting (like <a>, <ph>, <br>)—but only if your file structure is standard.
If your file came from a tool that adds raw HTML inside segments, we recommend:
- Keeping HTML simple and clean
- Avoiding inline scripts or non-standard tags
4. Check for “Already Translated” Segments
Pairaphrase respects existing <target> content.
If your file already includes translations, Pairaphrase may skip updating them. To force retranslation:
- Clear the <target> fields or use the Overwrite Targets option.
Best Practices:
- Always upload validated, clean XLIFF 1.2 or 2.0 files
- Use UTF-8 encoding
- Let Pairaphrase manage your tags—don’t edit inline code unless necessary
NOTE: If you are using DeepL as your translation engine in Pairaphrase, please read: Troubleshooting XLIFF 1.2 Issues with DeepL in Pairaphrase
Need Help?
If you're unsure about your file structure or still experiencing issues, our team is here to help.
Contact Support