AI Prompts for Translation

Translate the following document from {{source_language}} to {{target_language}} ({{regional_variant}}).

Document type: {{document_type}} (e.g., business proposal, user manual, marketing copy, legal brief)
Subject domain: {{domain}}
Target audience: {{target_audience}}

Translation guidelines:
- Formality register: {{formality}} (e.g., formal/usted, informal/tu, neutral)
- Priority: {{priority}} (choose one: literal accuracy OR natural fluency)
- Preserve all formatting, headings, bullet points, and paragraph structure
- Keep proper nouns, brand names, and product names in their original form unless an established localized version exists
- For technical terms with no standard translation in {{target_language}}, keep the original term in parentheses after your translation on first use

After the translation, provide a brief "Translator's Notes" section listing:
- Any passages where you made a judgment call between accuracy and fluency
- Terms you left untranslated and why
- Cultural references that may need adaptation for the target audience

Document:
"""
{{document}}
"""

Localize the following content from {{source_language}} ({{source_market}}) to {{target_language}} ({{target_market}}). This is not a direct translation — adapt the content so it feels native to the target market.

Content type: {{content_type}} (e.g., website copy, app UI strings, email campaign)

Adapt the following elements:
- **Date formats**: Convert to the standard format used in {{target_market}}
- **Currency**: Convert {{source_currency}} amounts to {{target_currency}} using approximate current rates
- **Units of measurement**: Convert if the target market uses a different system (metric/imperial)
- **Cultural references**: Replace idioms, metaphors, and cultural references with equivalents that resonate in {{target_market}}
- **Examples and scenarios**: Adjust names, locations, and contexts to feel local
- **Humor and tone**: Adapt humor style to what works in the target culture — remove jokes that do not translate
- **Legal/regulatory**: Flag any claims, disclaimers, or CTAs that may need legal review for {{target_market}}

Preserve the original intent, emotional impact, and call-to-action effectiveness.

Output format: Provide the localized content followed by a "Localization Changelog" listing every adaptation you made and why.

Source content:
"""
{{content}}
"""

Translate the following text from {{source_language}} to {{target_language}}, matching the exact tone and style of the original.

Original tone: {{tone_description}} (e.g., witty and irreverent, warm and empathetic, authoritative and technical)

To calibrate the tone, here is an example of the desired writing style in {{target_language}}:
"""
{{tone_sample}}
"""

Translation requirements:
- The translated text should feel like it was originally written in {{target_language}} by someone with the same voice
- Preserve sentence rhythm and paragraph pacing — if the original uses short punchy sentences, do not merge them into long compound sentences
- Maintain the same level of colloquialism or formality
- If the original uses wordplay, create equivalent wordplay in {{target_language}} rather than translating literally (note the adaptation in your output)
- Preserve emphasis patterns (bold, italics, capitalization for effect)

After the translation, rate your confidence (High/Medium/Low) on how well the tone transferred, and flag any passages where the tone was difficult to match.

Text to translate:
"""
{{text}}
"""

Translate the following technical document from {{source_language}} to {{target_language}}.

Domain: {{technical_domain}} (e.g., software engineering, mechanical engineering, medical devices, pharmaceutical)
Document type: {{document_type}} (e.g., API documentation, user manual, patent filing, clinical protocol)

Terminology glossary — use these approved translations consistently:
{{glossary}}

Rules:
- Use the glossary terms exactly as specified — do not paraphrase or use synonyms
- For technical terms NOT in the glossary that have no established translation in {{target_language}}, leave the original term and add a translation in parentheses on first use. Example: "Load balancer (repartidor de carga)"
- Preserve all code snippets, variable names, file paths, and command-line examples exactly as-is
- Keep all numbers, units, and measurements in their original format unless instructed otherwise
- Maintain the exact structure of tables, lists, and numbered steps
- Do not simplify or explain technical concepts — assume the reader has the same expertise as the original audience

After translation, provide:
1. A list of terms you encountered that were not in the glossary, with your suggested translations
2. Any inconsistencies you noticed in the source text

Document:
"""
{{document}}
"""

Adapt the following {{content_type}} from {{source_culture}} to {{target_culture}}. The goal is not word-for-word translation but cultural resonance — the adapted version should evoke the same emotional response and achieve the same business objective in the target culture.

Original language: {{source_language}}
Target language: {{target_language}}
Business objective: {{objective}} (e.g., drive sign-ups, build brand trust, educate users)

Cultural dimensions to consider:
- **Communication style**: Is the target culture high-context or low-context? Adjust directness accordingly
- **Visual metaphors**: Replace imagery references that are culture-specific (e.g., baseball metaphors for a non-US audience)
- **Social proof**: Adapt testimonials, statistics, and authority references to sources the target culture trusts
- **Color and symbolism**: Flag any color references or symbols that carry different connotations in {{target_culture}}
- **Humor**: Adapt or remove humor that relies on cultural knowledge the target audience lacks
- **Values emphasis**: Shift emphasis between individualism/collectivism, risk/security, innovation/tradition as appropriate

Output the adapted content, followed by a "Cultural Adaptation Report" that explains each significant change you made and the cultural reasoning behind it.

Source content:
"""
{{content}}
"""

Create a bilingual glossary for {{domain}} terminology, translating from {{source_language}} to {{target_language}} ({{regional_variant}}).

Purpose: This glossary will be used by {{glossary_users}} (e.g., translators, content writers, support agents, developers) to ensure consistent terminology across all {{target_language}} content.

For each term, provide:

| {{source_language}} Term | {{target_language}} Translation | Definition | Usage Notes | Avoid |
|---|---|---|---|---|

Include the following categories:
{{term_categories}}

For each entry:
- **Translation**: The approved translation for our context
- **Definition**: A brief, plain-language explanation (1 sentence)
- **Usage Notes**: When to use this term, formality level, any regional variations
- **Avoid**: Common mistranslations or terms that should NOT be used (and why)

Generate at least {{term_count}} terms. Prioritize terms that are frequently mistranslated or have multiple valid translations where consistency matters.

If a term should remain untranslated (common in technical fields), list it with a note explaining why.

Additional context about our usage:
{{context}}