XSD
OASIS XLIFF TC · 2.0
XLIFF 2.0
XLIFF 2.0 translation file
XLIFF 2.0 translation files: units, segments and inline codes.
About
XLIFF 2.0 reorganised the format into units and segments with a smaller core and optional modules. Angular and many translation management systems can write it.
Good to know
- Only the core schema is applied; module elements (metadata, glossary and so on) are accepted as the core schema allows.
- The example is by xmlvalid.com.
Files
2 files · 25.1 KB-
xliff_core_2.0.xsd main
-
xml.xsd
The validator loads all of these with their folder structure, so includes and imports resolve as published.
Example document
messages.xlf · 669 B · valid against this schema
In CI and from code
The same schema by its name, xliff-2.0, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema xliff-2.0
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: xliff-2.0
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document={{ $schema->example ?? 'document.xml' }} -F schema=xliff-2.0
Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups