Languages
Specify the language, region, and script your readers need, then configure and check that translation pair.
Lingo.dev uses multilingual language models to translate across languages. A localization engine combines that language capability with your product terminology, instructions, and voice. The useful question is which language version your readers need and how the chosen configuration performs on their content.
Language support involves several parts: the caller must accept the locale, the localization engine must have an applicable model configuration, and the model must produce useful text for the requested pair. An accepted language code establishes where the request should go; quality measurement and review establish what its result means.
Identify the intended language version #
A locale identifies a language and can specify its region or script. Use a more specific tag when that distinction affects the audience or writing:
| Locale | What it identifies |
|---|---|
fr | French, without an explicit region. |
en-GB | English for the United Kingdom, where regional spelling or terminology may matter. |
pt-BR | Brazilian Portuguese. |
zh-Hans | Chinese written in the Simplified script. |
zh-Hant | Chinese written in the Traditional script. |
These examples illustrate BCP-47 language tags, not a complete language catalog. Keep the intended locale consistent across the request, translation guidance, target files, and application. A format may represent the same locale differently in its paths, so follow the relevant format reference instead of assuming the request spelling is also the directory name.
Use sourceLocale for the language of the supplied content and the target locale for the version to produce. A wildcard such as * expresses configuration coverage where the interface supports it; it is not a destination language for a translation request.
Configure the pair that will be used #
A localization engine created in the web app starts with recommended primary and fallback models covering all locale pairs. That broad configuration lets you begin without creating a model entry for each target. It does not establish equal quality across every language or content type.
Use Models and fallbacks to configure a particular pair when it needs a different model. Check the applicable glossary terms, instructions, and brand voice as well. They use different selection rules: matching instructions can accumulate, while one voice variation is selected. Locale resolution explains regional matching, script safety, and precedence.
A bare language tag leaves some choices implicit. If the content is intended for a particular region or script, request it explicitly rather than expecting the localization engine to infer the audience from the source.
Check language and presentation together #
Try representative text, including product terms, conditions, and messages that use variables. Inspect the wording with a qualified reviewer or a measurement that addresses the requirement. A successful request proves execution for that case, not general quality for a language.
The application also needs to present the language correctly. Right-to-left text can require a direction setting and layout changes. Dates, numbers, and plural forms depend on locale-aware formatting and message logic. Translating the words does not implement those behaviors. Plurals, dates, and numbers develops that part of the work.
To expand an existing workflow, Add a language without retranslating everything explains how to introduce the new target while preserving accepted work in the languages already in use.