AreaAudit

Which languages each generator says it supports, and where

Per-job cap: how many languages one operation can produce

A per-job cap is the number of languages one operation can produce at once. It is a constraint on work rather than a statement of inventory, and it is published by one vendor among those read here. As of 2026-09-22.

The figure that shapes a schedule rather than a shortlistAn inventory figure tells a producer whether a market can be served. A limit on languages per operation tells them how many times the operation runs for a fifteen-language release, which is the number that appears in a budget.An inventory figureA limit per jobWhether a market can be servedPartlyNot at allOperations per episodeNothingDirectlyShape of a release scheduleNothingDirectlyPublished by vendors hereBy nine of themBy oneThe figure everybody publishes is not the one that plans work
Fig. 1 An unpublished limit is not an absent limit, and a hidden one surfaces after a project has started rather than before it is bought.
An inventory figure against a per-job cap, for a series. Recorded 2026-09-22.
What it tells a producerInventory figurePer-job cap
Whether a market can be servedPartlyNo
How many operations an episode needsNoYes
How a release schedule is shapedNoYes
How much review work there will beNoIndirectly

Inclusion rule. Two kinds of published language figure, compared on what each one lets a production plan. Order. Fixed order, the question inventory answers first.

1Inventory answers a market question, a cap answers a schedule question

Knowing a tool covers forty languages tells a producer their market is probably served. Knowing a single job covers ten tells them how many times they will run it for a fifteen-language release, which is the number that appears in a budget.

For a sixty-episode series those two figures produce very different plans. The inventory figure is the one every vendor publishes and the cap is the one almost nobody does.

2Caps exist even where they are not published

Any system producing several outputs from one input has a limit somewhere, whether it is stated, enforced by a queue, or implied by a price. A vendor publishing no cap has not necessarily got none.

So an empty cell here means the limit is undisclosed rather than absent. That is the same discipline this register applies to language lists, and it matters more here because a hidden cap surfaces only after a project has started.

3Why it belongs in a language register at all

Because it changes what a language list means in practice. Two vendors with identical inventories and different caps are selling different products to anyone releasing in more than a handful of languages.

It is recorded beside the list rather than inside it, since it is not a language and does not belong in a count. One vendor here publishes one, and the figure is printed with the page it came from.

A definition, not a measurement: no vendor figure appears here that is not also in the register. The one published cap in this register is recorded on that vendor cell.

Nearby terms: Printed total, Empty cell. The whole vocabulary is at terms; nothing on this page is a claim about a named product.