01 What happened
SAP Translation Hub's Document Translation service introduced automatic post-editing for maximum translation length. Localization teams often face the problem of accurate translations that exceed the character limits of UI elements such as buttons, labels, or tooltips. With this new feature, length constraints defined in the XLIFF 2.0 file are handled automatically during the translation workflow.
02 Key details
- Add the slr:sizeRestriction attribute at the unit level in XLIFF 2.0 files, setting it to the maximum allowed characters per segment.
- Submitting the file as usual triggers the post-editing step automatically; no extra configuration is needed.
- The feature is compatible with both SAP MT and LLM-based translation, available on synchronous and asynchronous API endpoints, and supported via the Document Translation UI.
- No independent testing or performance benchmarks are reported; the behavior reflects SAP's documented intended behavior. Consult official documentation for version or licensing requirements.
03 Why it matters
This matters because teams can define space constraints upfront and let the service enforce them, eliminating manual trimming after translation. The impact applies wherever workflows use XLIFF 2.0, the Document Translation API (sync or async), or the Document Translation UI.
04 Who it matters to
Localization teams, developers and operators.
Original sourceSAP Community