Translate
Master accurate translation that preserves meaning, formatting, and cultural context.
Formatting Preservation
- - Never translate content inside code blocks, HTML tags, or markdown syntax
- Preserve placeholders like
{name}, {{variable}}, %s, $1 exactly as-is - Keep markdown structure intact: headers, links, bold/italic formatting
- Maintain JSON/XML structure and keys — translate only values where appropriate
Content Rules
- - Don't translate: proper nouns, brand names, technical terms, URLs, email addresses
- Don't translate: code snippets, CSS classes, API endpoints, file extensions
- Preserve numbers, dates, and IDs in their original format unless locale conversion needed
- Keep consistent terminology throughout — create a glossary for repeated terms
Language-Specific Handling
- - Plurals: Use correct plural forms per target language rules (not English patterns)
- Gender: Ensure noun-adjective agreement in gendered languages (Spanish/French/German)
- Formality: Choose appropriate register (tu/vous, tú/usted, du/Sie) based on context
- RTL languages: Consider text direction for Arabic/Hebrew but keep LTR elements (URLs, numbers)
Cultural Adaptation
- - Adapt idioms and expressions rather than literal translation
- Convert units when culturally appropriate (miles↔km, Fahrenheit↔Celsius)
- Adjust date formats to locale standards (MM/DD vs DD/MM vs DD.MM)
- Use local currency symbols and number formatting (, vs . for decimals)
Context Awareness
- - Disambiguate based on context: "bank" (financial vs river), "mouse" (animal vs computer)
- Maintain document tone: formal business vs casual blog vs technical manual
- Consider target audience: children's content vs academic paper vs marketing copy
- Preserve original intent and emotional nuance, not just literal meaning
Quality Control
- - Read full context before translating to understand meaning
- Check that translated text flows naturally in target language
- Verify all formatting elements remain functional after translation
- Ensure consistent voice and terminology across the entire document
翻译
掌握精准翻译,保留原意、格式和文化背景。
格式保留
- - 绝不翻译代码块、HTML标签或Markdown语法中的内容
- 原样保留占位符,如{name}、{{variable}}、%s、$1
- 保持Markdown结构完整:标题、链接、粗体/斜体格式
- 维持JSON/XML结构和键名——仅在适当位置翻译值
内容规则
- - 不翻译:专有名词、品牌名称、技术术语、URL、电子邮件地址
- 不翻译:代码片段、CSS类名、API端点、文件扩展名
- 保留数字、日期和ID的原始格式,除非需要本地化转换
- 全文保持术语一致——为重复出现的术语创建词汇表
语言特定处理
- - 复数形式:根据目标语言规则使用正确的复数形式(而非英语模式)
- 性别:确保有性别语言(西班牙语/法语/德语)中的名词-形容词一致
- 正式程度:根据上下文选择合适的语域(tu/vous、tú/usted、du/Sie)
- 从右到左语言:考虑阿拉伯语/希伯来语的文字方向,但保留从左到右元素(URL、数字)
文化适应
- - 适应习语和表达方式,而非逐字翻译
- 在文化适当时转换单位(英里↔公里、华氏度↔摄氏度)
- 根据地区标准调整日期格式(MM/DD vs DD/MM vs DD.MM)
- 使用当地货币符号和数字格式(小数点用,还是.)
上下文感知
- - 根据上下文消除歧义:bank(银行 vs 河岸)、mouse(老鼠 vs 鼠标)
- 保持文档语气:正式商务 vs 休闲博客 vs 技术手册
- 考虑目标受众:儿童内容 vs 学术论文 vs 营销文案
- 保留原始意图和情感细微差别,而非仅字面意思
质量控制
- - 翻译前通读全文以理解含义
- 检查译文在目标语言中是否自然流畅
- 验证所有格式元素在翻译后仍保持功能
- 确保整篇文档的语气和术语保持一致