Language tracks
Localization fails when it starts after the master is accepted.
By then the voice was cast for one language, the claims were written for one market, and the lip-sync tolerance was set by a treatment nobody chose with a second track in mind. Tracks are declared at greenlight for that reason.
02 / Inside the workflow
One character, several languages, one identity
The hardest part of a multilingual track is not translation. It is that the same character has to feel like the same person in a language the original voice was not cast for.
Tosheo handles this by making the track a brief-level decision. If Tamil is declared at greenlight, the voice reference is chosen against both languages before it is approved, rather than a Tamil voice being sourced afterwards to match a Hindi performance it was never going to match.
- 01Tracks are declared in the brief
Which languages, which markets, and who reviews each one natively. A track added later is a scope change that reopens gates.
- 02Voice is cast against every declared track
An identity that only works in one language has failed the test before production starts.
- 03Pronunciation guidance becomes canon
Names, places and regional phrasing are recorded, approved, and checked in QA rather than re-decided by whoever is in the session.
- 04Each track is reviewed natively
Recorded as its own gate. A primary-track approver cannot sign for a language they do not speak.
- 05Delivery packages per market
Each track produces its own captions, disclosures and platform versions, bound by the rights that apply in that territory.
03 / Inside the workflow
What we are not claiming yet
Questions
Before you bring it into production
Which languages does Tosheo support?
At launch, a Hindi primary track with two additional Indian-language tracks, decided per production during validation. We are not publishing a longer list until production quality and economics for each track are proven, because a language on a marketing page that does not work in production is a refund conversation.
Is this dubbing?
It is closer to producing the episode in that language than dubbing it afterwards. The track shares the picture, the canon and the story state, but the voice, phrasing, captions and review belong to the track. Lip-sync tolerance is a treatment decision made with every declared track in mind.
Can I add a language after the season is done?
Yes, and it costs more than declaring it at greenlight would have. The voice was cast without it, the treatment was set without it, and the claims were written without it. The system handles the scope change honestly; it just cannot undo the earlier decisions for free.
How are translated brand claims handled?
As claims, not as text. A substantiated claim in one market may not be substantiated in another, and translating it does not carry the substantiation across. Each track holds its own approved claims and its own brand and legal sign-off.
Does a blocked track delay the whole production?
No. Rights, review and delivery are tracked per track. If one market variant is blocked on an unresolved grant, that variant blocks and the others ship.