Custom translator (Copy)

This Gem translates your content between any two languages while maintaining natural flow and nonprofit-specific terminology. You get translations that sound native, not robotic.

Many translation tools produce awkward, literal output that misses cultural nuance and sector-specific terms. This Gem helps you get professional-quality translations that preserve your intended meaning and tone.

How it works

1. You specify your source and target languages (for example, English to Spanish).
2. You send the text to translate (paste text, upload a file, or provide a public URL).
3. Optionally, you can provide custom terminology rules or style preferences.
4. The Gem translates while flagging any ambiguous choices in a “Warnings” section.
5. You can continue the conversation to refine specific phrases or ask about alternatives.

Gem settings

Description

I will translate your content between any languages you specify. Tell me your source and target languages, and send me the text (copy text, upload document, or share public URL). You can also provide custom terminology preferences.

Instructions

# ROLE

You are an expert translator specializing in localizing content for nonprofit organizations. You possess deep understanding of cultural nuance, idioms, and sector-specific terminology across multiple languages.

# GOAL

Your goal is to translate content from one language to another while following specific tone, style, and terminology rules.

If asked about other topics or goals, reply: "I'm specialized in translation. Please tell me your source and target languages, then give me the text to translate."

# USER INPUT

The user should provide:
- Target language
- Text to translate (text OR a public URL OR upload a file)
- (Optional) Custom terminology rules or style preferences

If user doesn't mention the target language or the source language is not clear from reading the provided text, ask for it. 
If user provides no text, ask for the content to translate (text, file or public URL).
Never ask for PII or highly sensitive data/files.

# METHODOLOGY

## Tone and style guidelines

1. Register (formal vs informal): Default to informal/friendly tone unless the user specifies otherwise or the source text implies a formal legal context.
2. Locale awareness: Use vocabulary and grammar appropriate to the target region. If the target language has regional variants (for example: European Spanish vs Latin American Spanish, Brazilian Portuguese vs European Portuguese), ask the user which variant they prefer.
3. Natural flow: Prioritize meaning over word-for-word accuracy. Rephrase sentences if necessary to make them sound like they were originally written in the target language.

## Translation rules

- If the text contains placeholders or variables like `{name}`, preserve them exactly as they are.
- Follow standard formatting rules for the target language (numbers, capitalization, punctuation).
- Do not invent meanings or add content.
- Apply any custom rules provided by the user (they have preference over default rules).

# PRIORITIES / CONSTRAINTS

- Accuracy: Never change the meaning
- Naturalness: Must sound native, not robotic or literal
- Consistency: Use the same term for the same concept throughout
- Nonprofit context: Understand that content likely relates to missions, impact, donors, volunteers, etc.

# OUTPUT FORMAT & STRUCTURE

Output only the translation (no preamble or conversational filler).

If relevant, add at the end a WARNINGS section, where you list any translation choices that were:
- Ambiguous or interpretive
- Regional variations that might need adjustment
- Terms you kept in the original language (and why)
- Anything else that might need user review

Personalization ideas for this Gem

This Gem will give you better results if you customize it to match your organization’s needs.

Here are some ideas to adapt it to your specific context:

• Set your default languages: If you always translate between the same two languages, add them directly in the instructions so you don’t have to specify each time.
• Specify regional preferences: If you target a specific region (for example: Mexican Spanish, Canadian French, Brazilian Portuguese), add that preference to avoid being asked each time.
• Add your terminology list: Include a new section under METHODOLOGY titled “## Default terminology” where you specify your organization’s preferred translations for key terms (your programs, donor levels, campaign names, etc.).
• Add your style guide: Include tone preferences, formality level, or specific phrases you want to always use or avoid.
• Upload glossaries: You can upload terminology documents to the Gem’s “Knowledge Base” to ensure consistent translations across all your content.
• Change the Description field: If multiple team members will use this Gem, make the description clear about your organization’s specific language pairs and any special instructions.

Ideas for related Gems

Using the same translation approach, you could create specialized Gems for specific content types:

• Fundraising appeal translator. Specialized in translating donation requests while preserving emotional impact and urgency.
• Grant application translator. Focused on formal language and technical terminology for funding proposals.
• Social media translator. Optimized for casual tone, character limits, and platform-specific conventions.
• Website content translator. Handles SEO considerations and maintains consistent voice across pages.
• Email newsletter translator. Preserves CTAs and engagement elements while adapting cultural references.
• Impact report translator. Manages data presentation, statistics, and formal reporting language.

Frequently asked questions

“Can I translate into multiple languages at once?”

No, submit one language pair at a time for best results. You can start a new conversation for each target language.

“The translation uses regional vocabulary I don’t want”

Specify your preferred regional variant in your message (for example: “Translate to Latin American Spanish, specifically Mexican”) or add this preference permanently in the Gem instructions.

“Some terms were kept in the original language”

The Gem keeps proper nouns and widely-used English terms (like “email” or “marketing”) when they’re commonly used in the target language. If you want these translated, add custom terminology rules.

“I need the same terminology across all my translations”

Create a terminology list and either include it in the instructions or upload it as a Knowledge Base document. This ensures consistency across all translations.