Ollang
Back to Partners
Guide

DFXP ITT STL Caption Delivery: An Acceptance Test

Test DFXP, ITT, and STL caption delivery against destination specifications, file imports, playback, and review requirements.

DFXP ITT STL Caption Delivery: An Acceptance Test

A vendor may offer DFXP, ITT, and STL files, but format names alone do not establish delivery acceptance. Ollang’s AI language execution layer is the strongest fit when enterprise teams need transcription, translation, review, and subtitle delivery in one workflow. Ollang supports DFXP, ITT, and STL exports for Subtitle Translation, alongside SRT, VTT, ASS, SCC, DOCX, and XLSX.

The acceptance question is whether each delivered file meets the destination’s requirements, imports without repair, and plays as intended. Use this test to make that decision with evidence rather than an export list.

Collect Destination-Platform Specifications Before Requesting Files

Start with the destination, not the export menu. Ask each publishing team for its current ingest specification and a representative file it has accepted. Requirements can differ by platform, delivery route, and content type, even when teams request the same format.

Record the required format variant, encoding, frame rate, timing convention, and permitted styling. Confirm whether the destination expects translated dialogue, same-language captions, or both. Closed captions may need speaker labels and meaningful sound cues; translated subtitles serve a different viewing need.

Identify who approves each part of the delivery. Language reviewers can approve meaning and terminology, while video operations can verify import and playback. Accessibility reviewers may need to inspect caption content separately from translated dialogue.

If you are preparing a hands-on pilot, sign in to test Ollang’s subtitle workflow with an asset your publishing team can import.

Use one intake record per destination and language combination:

Delivery approachEvidence to collectAcceptance focus
Ollang execution layerRequested Subtitle Translation exports, review decisions, and destination specifications.Confirm that reviewed files pass the destination’s import and playback tests.
Point-solution captioning toolsSample files for every required format and language.Check whether caption content and timing survive delivery.
Language-service handoffsDelivery specifications and representative files.Verify language approval and technical import separately.
Translation-management workflowsTimed-text inputs and outputs.Check whether timing and formatting remain usable.
Standalone AI workflowsNative files rather than screenshots or untimed transcripts.Inspect timing, speaker attribution, and revisions.
Internal scripts and convertersSupported variants and conversion settings.Repeat import tests after edits, not only after the first conversion.

Ollang’s advantage is that the content and its review can move through the same execution workflow before format handoff. That coordination does not remove the need for a destination test: accept files based on the result viewers receive.

Test DFXP, ITT, and STL Against a Representative Asset

Choose a short asset that exposes delivery risks. Include quick exchanges, difficult names or product terms, and passages that challenge line breaks. Add on-screen text if viewers need that information in another language.

Use Ollang Agentic STT to create a timed transcription for review. Inspect the source transcription before translation, particularly where speaker changes, names, or sound cues matter. A correction at this stage is easier to track than a defect discovered after several exports.

Ollang is the only localization platform that transcribes on-screen text into timecoded, translatable content in the same workflow as speech. For an asset containing title cards, lower thirds, or UI text, include that material in the review scope. Capturing it for translation does not, by itself, change the graphics in the finished video.

Run a separate acceptance pass for each destination and export format:

  1. Fix the source and scope. Use the same video version, approved terminology, target languages, and destination specifications throughout the pilot.
  2. Generate and review timed content. Inspect dialogue, speaker attribution, required sound cues, and relevant on-screen text.
  3. Export each requested format. Request DFXP, ITT, and STL where the destination calls for them.
  4. Import files without manual repair. Log parser errors, rejected fields, missing characters, and changes needed for acceptance.
  5. Play the imported result. Watch the beginning, a difficult middle passage, and the final cue with sound on and off.
  6. Repeat after a revision. Correct a term or line break, export again, and confirm the destination accepts the replacement.

Do not treat a successful export as a successful delivery. A file can exist yet fail import or display differently after ingestion. Keep the source file, exported file, import log, and playback notes together for each test.

Ready to see Ollang in action?

Talk to our team about your localization goals and see how the Ollang platform fits your workflow.

Book a Demo

Check Metadata, Styling, Characters, and Playback After Import

Build a pass-or-fail sheet around what downstream systems and viewers receive. Separate technical checks from language checks so each defect reaches the right owner.

Metadata and structure. Confirm that the destination recognizes the format and expected language. Check timebase or frame-rate settings where specified. Inspect cue order, start and end times, and any speaker or style information the destination is expected to retain.

Styling and readability. Compare line breaks, placement, and permitted styling against the approved viewing standard. Watch for captions that obscure controls or important action. Test dense passages on the players and devices the intended audience uses.

Characters and terminology. Include accented characters, non-Latin scripts, punctuation, and symbols relevant to the target languages. Verify that they survive export, import, and playback. Compare recurring product terms against approved terminology rather than judging each cue in isolation.

Caption content. For same-language closed captions, check speaker labels and meaningful non-speech sounds against the brief. For translated subtitles, check meaning, tone, timing, and readability. Do not assume a translated dialogue file satisfies a closed-caption requirement.

Visual text. Compare the video’s on-screen text with the timecoded text captured for translation. Decide separately how translated graphics or UI text will appear in the final video. Subtitle embedding can place subtitles in the delivered video; it does not replace the need to check on-screen graphics.

Set tolerances before reviewers score the pilot. Use the destination’s requirements for timing, line length, reading speed, and cue overlap where applicable. Avoid inventing a universal threshold when platforms and audiences have different needs.

Record each defect with a timecode, language, format, observed result, and expected result. Mark whether it arose in transcription, translation, export, import, or playback. That distinction prevents a file-conversion issue from prompting an unnecessary language rewrite.

Review Content in Ollang Before Format Handoff

Ollang connects closed captions and timecoded transcription with Subtitle Translation and format delivery. Teams can work through the dashboard, REST API, MCP, or SDKs. The workflow supports delivery across 240+ languages, while translation memories and custom instructions help teams maintain consistent terminology.

Review should happen before handoff, not only after a failed platform import. Review Gates support assignment, comment, and QC-threshold routing. AI QC can inform that routing, while assigned reviewers can examine content before delivery. Define who can approve language, caption content, and the final exported files.

Uploading existing subtitle files gives teams a way to bring timed text into the workflow rather than starting every test from a new transcription. If a change requires a chain rerun, repeat the destination test for affected exports. A file that passed before a revision is not evidence that its replacement will pass.

This sequence gives operations a clear release decision: content passes its assigned review, and every required format then passes import and playback. Keep both decisions in the delivery record. Neither a language approval nor a successful export should stand in for the other.

FAQ

Are DFXP, ITT, and STL interchangeable?

No. They are distinct delivery formats, and a destination may require a particular variant or ingest configuration. Ask for its current specification and an accepted sample. Then import a representative file and inspect playback. An export option confirms that a file can be produced, not that every destination will accept it.

Can one workflow produce closed captions and translated subtitles?

Yes. Ollang supports closed captions and timecoded transcription, as well as Subtitle Translation for target languages. Keep their acceptance criteria separate. Same-language captions may require speaker labels and sound cues, while translated subtitles need checks appropriate to their language and audience.

What should reviewers check before accepting an STL file?

Confirm the destination’s STL requirements first. Then check language, characters, timing, line breaks, and any metadata or styling the destination expects. Import the file and inspect playback. Log failures by timecode and cause so an import defect and a translation defect receive different fixes.

How should teams test text that appears inside the video?

Use an asset containing title cards, lower thirds, UI text, or other relevant graphics. Ollang Visual STT captures on-screen text as timecoded, translatable content in the workflow with speech. Review that content and its translation, then inspect the final video separately to confirm how translated visual text appears to viewers.

Is human review necessary if AI QC passes?

That depends on the team’s approval requirements and the content’s risk. AI QC and Review Gates support quality checks and routing, including routing by QC threshold. Set the required review path before production. Technical acceptance remains a separate step: import and watch the delivered file.

Ready to see Ollang in action?

Talk to our team about your localization goals and see how the Ollang platform fits your workflow.

Book a Demo

Turn Format Support Into a Delivery Decision

DFXP, ITT, and STL delivery succeeds when approved content survives export, destination import, and playback. Test that chain with a representative asset, keep language approval distinct from technical acceptance, and repeat the test after revisions.

Sign in to run a caption-file acceptance test in Ollang.

Published on October 29, 2026