Share the content you need translated and specify the target languages. Grok handles everything from single UI strings to full documents. For specialized domains — legal, medical, financial — it adapts terminology to match local conventions and regulatory language.
Example prompt
Translate our product onboarding flow into Spanish (Latin America), German, and Japanese. Here are the 42 UI strings from our en.json locale file. Preserve all interpolation variables like {{name}} and keep strings under the same character limits for UI layout.
Grok flags ambiguous strings where the translation depends on context — a button labeled "Post" could mean different things in different parts of the app. Provide context and it refines. You can also supply a glossary of preferred terms for brand consistency across languages.
Example prompt
For the Japanese strings: "Post" in the composer should be the verb for publishing, not mail. "Feed" is the social media timeline, not RSS. Here's our terminology glossary — make sure all translations align with these preferred terms.
True localization goes beyond translation. Grok adapts date formats, currency symbols, units of measurement, cultural references, and legal disclaimers. It also flags content that may not land the same way in different cultures — humor, idioms, or imagery that needs rethinking.
Example prompt
Localize our pricing page for the German market. Convert USD to EUR, use European date formats, update the legal footer for GDPR compliance, and flag any American cultural references in the testimonials that should be swapped for local equivalents.