Created
November 3, 2025 16:21
-
-
Save eevmanu/0d0f34d4ea80ead653ddaa62b775d1fd to your computer and use it in GitHub Desktop.
recent optimized prompt to translate a text from spanish into english
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Translate the provided Spanish text into fluent, idiomatic American English—prioritizing clarity, natural phrasing, and cultural appropriateness for native US speakers. Unless specified otherwise, default to standard American English conventions. | |
| If the input includes sections already in English, focus first on improving, translating, and explaining the parts written in Spanish. Only rework or refine the existing English portions if doing so clearly enhances context, cohesion, or the overall output quality—particularly in cases where mixing English and Spanish in the source text meaningfully enriches the final English result. Apply this in a nuanced way: prioritize Spanish-to-English translation, but apply careful judgment when integrating or rewriting English and Spanish segments together based on semantic intent. This approach should remain narrowly scoped to this use case to avoid reducing the output's precision or quality. | |
| When explaining optimizations or improvements made, provide a precise account of your rationale—detailing not only translation choices but also any bilingual composition logic you applied, and why, for this specific scenario. Be thorough but avoid generalizing to broader cases: keep explanations tightly focused on this niche situation. | |
| Begin with a concise checklist (3-7 bullets) of what you will do; keep items conceptual, not implementation-level. | |
| ## Output Instructions | |
| 1. Present the full translated text within a single block delimited by triple backticks (```), with each set of backticks on its own line, and a blank line before and after. | |
| 2. Below the code block, add a line with three hyphens (---) on its own line to separate sections. | |
| 3. Provide a detailed explanation of each significant improvement or adaptation compared to a literal translation: | |
| - Quote the relevant Spanish phrase, machine-translated segment, or its less idiomatic English translation. | |
| - Explain your chosen US English phrasing, with clarity and authenticity. | |
| - For mixed-language or rewriting scenarios, clarify the reasoning for integrating, revising, or combining English/Spanish segments, and how this serves the user's overall intended meaning. | |
| - Give examples if useful, and group explanations logically (by paragraph, block, or prominent sentence) using clear hierarchical bullets. | |
| 4. If the source text is malformed, ambiguous, contains slang, or its meaning is unclear, address this in your explanation. Offer your best interpretation or, if necessary, request clarification. | |
| 5. Assume the input is Latin American Spanish unless otherwise noted. | |
| 6. The text to translate follows this prompt, separated by a single blank line—do not require triple backticks in the input. | |
| ### Multi-turn Conversation Rule | |
| - In multi-turn conversations, always base your translation and explanations solely on the latest or most recent input received from the user, rather than reprocessing previous user messages or outputs. Optimize for efficient use of output and tokens by only addressing the most recent prompt. | |
| - However, if information, context, or clarification from previous conversation turns is essential for enriching or improving the latest translation attempt (such as resolving ambiguities or contextualizing idioms), you may draw on that context. Do so only when it directly benefits the accuracy or quality of the current output. | |
| - Unless there is obvious contextual need, avoid regenerating or referencing previous user prompts and instead focus entirely on the final, latest user input. | |
| After completing your translation and explanations, briefly validate that your choices maximize clarity, idiomatic accuracy, and fit for US English. Self-correct if any instructions or conventions are unmet. | |
| ## Output Format | |
| Example Output: | |
| ``` | |
| [Your translated American English text here] | |
| ``` | |
| --- | |
| - Original: "la computadora se prendió sola." | |
| - Improvement: Translated as "The computer turned on by itself." | |
| - Rationale: Selected the standard American English phrase; "turned on by itself" is the common idiom. | |
| - Original: "estoy hecho leña." | |
| - Improvement: Rendered as "I'm exhausted." | |
| - Rationale: "hecho leña" is an idiom in Spanish for being very tired—so provided the equivalent English idiom instead of a literal translation. | |
| If the input is unclear: | |
| - Note any ambiguity, e.g., "The phrase 'qué onda' could mean 'what's up' or 'what's happening,' depending on regional context." | |
| Structure explanations by logical content units—by paragraph, or by splitting multi-sentence content for greatest clarity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment