AreaAudit

Which languages each generator says it supports, and where

What the document-language column holds

The document-language column records what a tool says about the language of the working documents it produces: outlines, episode breakdowns, storyboard scripts, character descriptions. It is filled from a published rule or a named list. One vendor in the register has published either, and the rest of the column is blank. As of 2026-09-12.

Three vendor wordings about output, three different cellsA vendor naming the languages its breakdowns come out in fills this column with a list. A vendor tying output to a setting fills it with a rule a reader can apply. A vendor saying only that it supports languages fills nothing, because the same word covers a translated help centre.What the vendor says about the documents it generatesNames the languagesRecorded as a listEach name can be checkedagainst one market onits own.Ties output to a settingRecorded as a ruleA reader applies it toany language in thatsetting.Only that it supportsNothing recordedThe word covers menus asoften as generated text.The same word, read three ways
Fig. 1 The third branch is where most of the register sits, and it is the reason the column is mostly blank rather than mostly wrong.
What would fill the document-language column, and what the register does with each kind of vendor statement. Recorded 2026-09-12.
What the vendor publishesHow it is recordedWhy it is handled that way
A rule tying output to a settingRecorded as a rule, with the setting it followsA reader can apply it to any language in that setting without guessing
A named list of output languagesRecorded as a list, language by languageEach name can be checked against a market on its own
A sentence about supporting languagesNot recorded in this columnThe word covers menus as often as it covers generated text
Nothing addressing output at allRecorded as no list publishedSilence is not a refusal, and is not filled in from the site column

Inclusion rule. Statements a vendor could make about the language of its generated documents. The last row is the common case and is kept in the table for that reason. Order. Strongest published evidence first, silence last.

1A document is not a subtitle and not a menu

The documents in question are the ones a production actually edits: the breakdown of a script into episodes, the per-shot text a generator works from, the descriptions that keep a character looking the same across a series. They are read by people, rewritten by people, and passed between a writer and a producer who may not share a language with the vendor.

That makes their language a staffing question rather than a comfort one. A team working in Portuguese with an English breakdown is translating twice a day, every day of the production, and no amount of interface translation removes that work. It is the column a buyer feels first and the one vendors describe least.

2What counts as an answer, and why a sentence usually is not one

Two shapes fill this column. A list names the languages the documents come out in. A rule says which setting the language follows, so a reader can work out the answer for any language in that setting. One vendor in the register publishes such a rule, tying the generated working documents to the interface language the user has chosen.

A marketing sentence about supported languages fills nothing. The same word is used on the same sites for a translated help centre, and a reader cannot tell which claim is being made. Recording it would turn the column into a restatement of the site column, which is exactly the merge this register refuses.

3Why the blank cells are not inferred from the site column

It would be easy, and wrong, to assume that a tool offering its interface in twenty languages writes its breakdowns in twenty languages. Interface strings are content work done once. Generated prose is the model writing, and its quality and availability by language are set by training data and by the instructions the vendor sends with each call.

So a vendor with a wide site and no published output rule is recorded here as publishing no list, with its site count still standing in the column next door. The two numbers are allowed to disagree, because on most vendor sites they do.

4Where this column sits in the register

Columns, and who names a list in eachDocument language is the column this page is about, and one of the two the register mostly finds empty. Counted from named lists only. Recorded 2026-09-12.Columns, and who names a list in eachTools naming a listTools naming alistDialogue languageDialogue language — Tools naming a list: 1 of 2 toolsDocument languageDocument language — Tools naming a list: 1 of 2 toolsSite languageSite language — Tools naming a list: 2 of 2 tools
Fig. 2 Document language is the column this page is about, and one of the two the register mostly finds empty. Counted from named lists only. Recorded 2026-09-12.
The three columns the register keeps, and how many of the two fully read tools name a list in each. Recorded 2026-09-12.
ColumnTools naming a list
Dialogue language1 of 2 tools
Document language1 of 2 tools
Site language2 of 2 tools

Inclusion rule. The three columns this register keeps apart. A column stays listed even where neither tool names a list, because an empty column is a finding about disclosure. Order. Alphabetical by column name.

  • Output languages
    Script analysis, episode outlines, storyboard scripts and character descriptions follow the interface language, across the same 15tied to the interface settingSceneMixer, languages guide / recorded 2026-09-12
  • Output languages
    No public list (as of 2026-09-12)no list publishedkling.ai / recorded 2026-09-12

5Sources

Every entry in this column is read from the vendor page named beside it and carries the day it was read; the current state of all three columns is in the register, and the rule that lets a claim into a cell is on how counted. The other columns: Dialogue language, Site language. All three: the columns of the register.