What should I consider when prompting across languages?

Specify locale, formality, and cultural references to use or avoid. Provide glossaries and tone examples per market. Ask for a local review checklist (units, dates, idioms) and forbid literal translations for slogans. Validate placeholders and lengths for UI texts. For low-resource languages, expect to iterate more and consider human review.

In practice

Ask for ‘local pitfalls’ before drafting—models often surface helpful warnings.

Where to start

1Create locale cards with do/don’t notes.
2Add a per-market glossary and tone sample.
3Run a localization QA checklist step.
4Pilot with human review in new markets.

i18n promptsmultilingual promptingglobal AI content

Build it properly

Promptise Foundry treats prompts as software — typed blocks, versioning, guards and an inspector that shows you every assembly decision.

Prompt engineering in Foundry Read the guides

What should I consider when prompting across languages?

Where to start

Related questions

Build it properly

What should I consider when prompting across languages?

Where to start

Related questions

Build it properly