Language support

Every engine scans text in any language: its core detection applies regardless of what language the input is in. The Multilingual engine builds on that with per-language detection tuned for the identified language, for apps whose traffic spans many languages. It is rolling out now: it appears on your dashboard's Detection Engine page and becomes selectable when it goes live for your workspace.

Detection model coverage

The Multilingual engine routes each scan to a detection model set trained for the identified language. Coverage at launch:

Coverage grows over time; languages are added as their model sets pass the same evaluation bar as the English models.

Language identification

Identification currently covers 20 languages:

ar, bg, de, el, en, es, fr, hi, it, ja, nl, pl, pt, ru, sw, th, tr, ur, vi, zh

Two details worth knowing:

• Hints win. If your SDK call supplies a language hint, it is used for routing directly, including for languages the identifier doesn't cover (Swedish and Norwegian, for example). The scan result still records whether the detected language agreed with the hint.
• Low-signal input abstains. Very short prompts often carry too little signal to identify reliably. Rather than guess, identification abstains and the scan falls back to the default model set.

The outcome is surfaced on the language field of every scan result (see How Tawa works); it is null while language features are disabled for your app.

Everything else

A language outside the supported set is still scanned. It routes to the nearest supported model set (same language family first, same script second, then the default set) and the response is flagged as degraded so you can act on the reduced confidence.