AreaAudit

Which languages each generator says it supports, and where

Working document: what a crew reads rather than what an audience sees

A working document is anything a generated pipeline produces for a person to act on: an outline, a breakdown, a character description, a shot list. Its language decides whether a crew can work, and one vendor in this register publishes what that language is. As of 2026-09-22.

Four artefacts, four readers, four different costsA script analysis goes to a writer, an outline to a director, a shot description to a designer or operator, a character description to a designer. In the wrong language each of them pushes translation work onto somebody less equipped for it.Script analysisRead by a writer or producerTranslated firstA delay before anythingstartsEpisode outlineRead by a directorTranslated underdeadlineDecisions from a roughversionShot descriptionRead by a designer or operatorOften not translatedErrors enter the pictureThe work a generated document hands to a personWhat each reader is left holding
Fig. 1 The translation step does not disappear when a tool generates these; it moves downstream to whoever has to act on them.
Who reads each artefact, and what happens if it is in the wrong language. Recorded 2026-09-22.
ArtefactRead byIf it arrives in the wrong language
Script analysisA writer or producerThe analysis has to be translated
Episode outlineA directorThe translation step moves downstream
Shot descriptionA designer or operatorErrors enter the picture
Character descriptionA designerConsistency work becomes guesswork

Inclusion rule. The artefacts a generated pipeline hands to people, with the consequence of each arriving in a language the room does not read. Order. Earliest artefact in a pipeline first.

1The translation step does not disappear, it moves

If these documents arrive in a language the room does not read, the tool has not removed the translation work. It has moved it to a director or a designer, who is less equipped for it and is working under a deadline.

That is the argument for treating this as a column of its own rather than as a detail of the interface. It is a working condition, and for a non-English production it can decide whether a tool is usable at all.

2Almost nobody publishes it

One vendor in this register states that its generated documents follow the interface language and names the document types. Every other vendor read here publishes nothing in this column.

Including every vendor with a long voice list. Documenting a voice inventory and documenting what language the paperwork arrives in turn out to be entirely separate decisions.

3A rule answers it better than a list would

A published list of output languages would have to be maintained separately from the interface list and could drift out of step with it. A rule saying output follows the interface setting cannot.

It is also checkable by anyone who can change the setting, which is more than can be said for most claims in this register. The one filled cell in this column is of that shape.

A definition, not a measurement: no vendor figure appears here that is not also in the register. The document column and its single entry are read on their own column page.

Nearby terms: Interface string, Market version. The whole vocabulary is at terms; nothing on this page is a claim about a named product.