إنتقل إلى المحتوى الرئيسي

Automatic translation

Automatic translation creates missing language variants after source content exists. Teams can continue working while Scoutello prepares additional locales, and dashboard or guest surfaces show progress where waiting would otherwise be unclear.

When translation runs​

Two patterns coexist:

  1. Source-language completion — When new authored copy lacks an English version, Scoutello can prepare a starting English variant before broader localization proceeds.

  2. Scoped translation — Teams trigger translation for a specific area, such as a landing page, tour, tour step, event, or PDF. Scoutello translates the relevant fields together so the result stays consistent.

Background processing​

Translation work runs in the background. Scoutello:

  • Identifies source text eligible for translation.
  • Honors settings that skip machine translation entirely.
  • Avoid duplicate target locales when they already exist.
  • Groups related work into manageable batches.
  • Records progress as batches finish.

The durable outcome is updated translated content and optional audio, not the progress meter itself.

Translation providers​

Text is sent to managed translation services with conservative settings and automatic retries for temporary provider failures. Scoutello keeps enough status information to distinguish human-edited copy from machine-generated copy.

Specific vendor defaults can change between releases; quote capabilities—not vendor names—when speaking with customers.

Audio and narration​

Tour-heavy locales often pair translated copy with generated narration. Audio pipelines may lag behind text; separate progress messaging avoids implying silence equals failure.

Progress tracking​

Long jobs expose progress so dashboards and guest waiting screens can show percentages or staged statuses.

Progress records are temporary; only finished translations belong in publishing workflows.

Skipping translation​

Mark content that must remain untouched:

  • Brand names and proper nouns that should not drift across locales.
  • Codes, identifiers, or deliberately neutral tokens.
  • Legal clauses awaiting counsel review.
  • Mixed-language snippets already curated manually.

Operational notes​

  • Translation work should be safe to retry: existing locales must not duplicate endlessly.
  • Interfaces should show progress rather than leaving users waiting on a single long action.
  • Manual edits after automation become the canonical text for that locale.

Related concepts: How translations work, Tours multilingual audio, Languages and localization.