The prompt
Score 10 of 10, Excellent
Use it when You need a text in another language that reads as if it was written there, without losing facts, conditions or your product terms.
- {{source_text}}
- {{glossary}}
- {{source_language}}
- {{target_language}}
- {{target_region}}
- {{register}}
- {{audience}}
Full prompt and why it works
Prompt
<source_text> {{source_text}} </source_text> <glossary> {{glossary}} </glossary> <constraints> - The source is in {{source_language}}. Translate the meaning, not word by word: sentences should read naturally to a native speaker of {{target_language}} in {{target_region}}. - Keep every fact, number, date, condition and exception. Do not add, drop or soften anything. - Use the glossary terms exactly. Leave product names, code, URLs and text in square brackets untranslated. - Change date formats, decimal separators and number formats to local conventions. Do not convert currencies, prices or units of measure, because those are business decisions; flag them instead. - Match this register: {{register}}. </constraints> <format> 1. The full translation, keeping the original headings, lists and paragraph breaks. 2. A table with the columns Original phrase, Translation, Note, listing up to 10 places where you made a choice a reviewer should check, such as an idiom with no direct equivalent, a term missing from the glossary, or a currency or unit left as it was. </format> <task> Translate the source text above into {{target_language}} for {{audience}} in {{target_region}}. A native-speaking reviewer should be able to approve it with only small edits. If a passage is ambiguous in the original, do not guess: translate the most literal reading and flag it in the table. </task>
Variables
- {{source_text}}
- The text to translate.
- {{glossary}}
- Terms with fixed translations, one per line, such as product names or legal terms. Write "none" if you have none.
- {{source_language}}
- The language the text is written in.
- {{target_language}}
- The language to translate into.
- {{target_region}}
- Where the readers are, for example Mexico, Quebec or Brazil, since vocabulary and conventions differ by region.
- {{register}}
- How formal it should be, for example "formal, like a letter from a bank" or "friendly, like an app's help pages".
- {{audience}}
- Who will read the translation, for example "customers" or "warehouse staff".
Why it works
- What to avoid. Facts, conditions and glossary terms stay fixed while date and number formats are localized, which keeps the meaning and terminology the same in every language.
- If unsure. Currencies, units and ambiguous passages are flagged in a table rather than converted or interpreted, because those are decisions for a person.
- Layout. Material first, rules and format in XML-style tags, and the task at the end: the order Google recommends for Gemini.