Hindi, declared by one vendor out of eighteen
Hindi appears in Kling AI's declared list of 20 and in no other. No other South Asian language appears in any declared list here: not Bengali, not Tamil, not Telugu, not Urdu, across nine vendors that declare a site language and nine that declare none. As of 2026-09-22.
| Vendor | Codes declared | Note |
|---|---|---|
| Kling AI | hi | 20 alternates declared in all |
| Declared by no vendor here | bn, ta, te, ur | Absent from all nine declared lists |
Inclusion rule. Only languages declared as hreflang alternates on the host being read are listed. Coverage is not shown per language for the voice column, because the vendors that publish a list there are not the vendors that declare a site language here. Order. Vendors that declare any of these codes, in register order; then the codes no vendor declares.
1One language, one vendor, for a region of that size
South Asia is represented in this entire register by a single declared language on a single vendor. Whatever these lists are measuring, it is not audience size: the absent languages here have more speakers than several of the European entries that eight of the nine declare.
That is the clearest evidence in the register that declared site languages track commercial attention rather than market size, and it is worth stating plainly rather than leaving implied.
2The voice column is where a Tamil production should look instead
For Hindi there is one vendor with a declared site language and a published voice count of five that names nothing. For Tamil, Bengali, Telugu and Urdu the site column is empty across the board, and that is the wrong column to be reading: the vendors with named voice lists here declare no site alternates at all.
A production in these markets therefore has a genuine shortlist, and it is a shortlist of list-publishers rather than of site-translators. Whether any named list reaches these languages is a question a reader can settle in a search, which is exactly what a count cannot offer them.
3Why the absences get their own row
A table showing only Hindi would suggest the region is partly covered. Listing the absent languages in the same table shows the actual shape, which is one language out of many and one vendor out of 18.
The register does this everywhere it can: what is not declared is a row, not a silence, because a silence is invisible to a reader scanning for their own market.
- Site languages15 languages: ar, de, en, es, fr, id, it, ja, ko, nl, pt, ru, tr, uk, zh-Hantdeclared as same-domain alternates
- Site languages20 languages: ar, de, en, es, fil, fr, hi, id, it, ja, ko, ms, nl, pl, pt, ru, th, tr, uk, videclared as same-domain alternates
4From a multilingual pipeline
On the language side of “South Asia”, SceneMixer's published guides say the following:
SceneMixer separates the script language from the production language: the output (episode outlines, storyboards, on-screen text) follows your interface language, and target-region localization adapts character names, casting, and scenery for Western, East Asian, Southeast Asian, or Latin American audiences.
SceneMixer, Turn a Novel into a Video Series with AI — “Can I turn a Chinese web novel into an English-language drama?” (read 2026-10-13)
Scene order, dialogue and beats follow the script; what the pipeline adds is coverage — which shot sizes, who is in frame, how long each shot holds.
SceneMixer, Script to Video, End to End — “How faithful is the shot list to my script?” (read 2026-10-13)
5Sources
Every declared list is read from the vendor's own host and recorded in full on the register, checked 2026-09-22. The counting rule is on how counted; the spoken side is on dialogue languages. Nearby markets: East Asia, Southeast Asia.