XLIFF 2.0
XLIFF 2.0 is a widely used XML-based format for the exchange of localization data. It is the successor of XLIFF 1.2.
It is used for Angular, Symfony and many other platforms.
If you use Angular, please check out our dedicated Angular documentation.
Features
- Multiple segments per unit
- Any nesting of groups
- Each
segmentis treated separately (independent of group/unit) - Description/meaning are used as context when provided
in
<note category="description">/<note category="meaning">
Usage
curl https://api.doloc.io -H "Authorization: Bearer $API_TOKEN" --data-binary "@input.xlf" -o output.xlfExample
For a detailed example of XLIFF 2.0 localization with doloc, including step-by-step instructions on using the API for translation, check out our XLIFF 2.0 Example Translated with doloc.
Options
Options are passed as query parameters in the URL.
The options untranslated and context can use any DNF combination of the described values.
I.e. a comma separated list of values for an OR combination and an underscore separated list of
values for an AND
combination.
For details check the options documentation.
| name | values | default | description |
|---|---|---|---|
untranslated | combination of XLIFF 2.0 states, no-state, target-equals-source, empty-target | initial,no-state_target-equals-source,no-state_empty-target | Translate all units that match this configuration. |
context | combination of XLIFF 2.0 states, no-state, target-not-equals-source, non-empty-target | translated,reviewed,final,no-state_target-not-equals-source | Use all units that match this configuration as translation context (glossary). |
newState | any XLIFF 2.0 state, or unchanged | translated | State of the (newly) translated units. unchanged: keep existing state. |
Limitations
none that we are aware of 🙂