v0.5.0

Pre-release. SDKs and integration guide: README.

What's in 0.5.0

New: translation files, an alternative to the API for integrations. Nothing changes for existing API use.

Added

• Translation files (all five SDKs, spec/translation-file.json, integration guide → Translation files: XLIFF and HTML): export an item's segments as XLIFF 1.2 (exportXliff(jobs), one <file> per job, formatting as <bpt>/<ept>/<ph> inline codes) or HTML (exportHtml(job), the API's document with the job's metadata in its head), translate them outside the API (a CAT tool, a translator, Supertext's web app), then read(content) the file and importTranslations(file, currentSegments): per segment ok, source_changed (checksum differs from the export), untranslated, invalid_markup or missing. Imported files are treated as untrusted: size limit, no DTDs, markup only from the current source (XLIFF codes replaced by the source's tags; HTML only with the source's tags and attributes and safe links). Not versioned with the API: TypeScript TranslationFiles from supertext-sdk, PHP Supertext\Sdk\Files\TranslationFiles, Python supertext.files, .NET Supertext.Sdk.Files.TranslationFiles, Java com.supertext.sdk.files.TranslationFiles; errors invalid_job, invalid_file, missing_metadata, too_large.