Subtitle Workspace

Subtitle work is about preserving context, not just editing lines

In DreamCreator, subtitle work does not treat subtitle files as isolated artifacts. Subtitles stay connected to source video, task history, language assets, style assets, and final exports inside one project context.

That matters because creators rarely care only about “is this line fixed.” They also care about:

• which video version the subtitle belongs to
• whether terminology and tone match the publishing target
• whether translation, proofreading, burn-in, and export still need to happen next

Common ways into the subtitle workspace

You usually enter the subtitle workspace through one of these paths:

• a download result that already includes subtitle tracks
• a manually imported subtitle file
• an existing project that still needs more subtitle work

So the workspace is not a detached editor. It usually receives the output of an earlier task and keeps the story moving.

QA checks are part of the workflow itself

The current product structure makes subtitle QA part of the workflow rather than an optional extra. Common checks include:

• text
• timing
• layout
• cps
• cpl

This keeps translation, proofreading, and delivery judgment inside one operational surface instead of splitting them apart.

Language assets and style assets are meant to be reused

The refactored product is not only about translating one subtitle file. It also lets you keep reusable assets around the workflow:

• glossary profiles
• prompt profiles
• runtime settings for translation and proofreading
• mono and bilingual subtitle styles
• subtitle export presets

Once those become stable, later projects stop starting from zero.

Why this connects naturally to transcoding and burn-in

In DreamCreator, subtitles are part of delivery, not an afterthought. That is why subtitle work naturally connects to preview, transcoding, subtitle burn-in, and export instead of ending at plain text editing.