Chuyển tới nội dung chính

How translations work

Scoutello separates the structure of a feature from the language variants of its text. A tour, landing page, tile, event, or PDF keeps one stable object while its reader-facing text can exist in multiple languages.

That model lets teams author once and serve guests in many languages without duplicating entire experiences.

Content storage​

Translatable product content is managed as language-specific variants. Each variant carries:

  • The locale code.
  • The text value (when present).
  • Status information distinguishing manual authoring from generated translations.
  • Optional audio attachments where narration ships beside copy.
  • A setting indicating translation automation should leave the text unchanged when it must remain verbatim.

Related locales reference one another so Scoutello can treat them as a translation family for that paragraph or headline.

Authoring flow​

Dashboard forms keep translated fields consistent so blank noise is trimmed, duplicates are avoided, and new locales attach without breaking existing content.

The authoring flow is straightforward: save copy in the working language, optionally trigger automatic translation, then review variants before publishing broadly.

Runtime localization​

Guest and operator experiences typically receive the best text for the requested locale, such as one title or description, instead of exposing every language variant at once.

Scoutello prefers the guest's requested language, falls back through configured equivalents and broadly understood defaults, and respects do-not-translate markers.

Guest language selection​

Guest-facing surfaces choose a locale from the link, browser settings, saved preferences, or contextual defaults. The visible experience should read as ordinary localized copy, not as a technical fallback chain.

Operational expectations​

  • Include every locale you intend to market before launch-critical moments.
  • Treat automatic translations as draft-quality until a fluent reviewer approves them for high-trust surfaces.
  • Keep UI chrome copy separate from authored marketing copy—the former ships as keyed translations, the latter lives with the tour, tile, or document itself.

Related concepts: Automatic translation, UI strings and i18n, Languages and localization.