Translate

Translate only the prose content while leaving markdown syntax, headers, links, and bold/italic markers untouched. Never translate content inside code blocks, HTML tags, or placeholders like {name} or %s.

Proper nouns, brand names, technical terms, URLs, email addresses, code snippets, CSS classes, API endpoints, and file extensions should remain in their original form. Numbers, dates, and IDs stay as-is unless locale conversion is needed.

Use the plural rules of the target language rather than English patterns, since languages like Russian, Arabic, and Polish have multiple plural categories. Ensure noun-adjective gender agreement in languages like Spanish, French, and German.

Select the register based on context and audience: tu/vous in French, tú/usted in Spanish, du/Sie in German. Formal business documents typically require the formal register, while casual blog content uses informal forms.

Yes, but RTL languages require attention to text direction for Arabic and Hebrew content while keeping LTR elements like URLs and numbers in their original direction. Mixed-direction documents need careful bidirectional text handling.

Idioms and expressions carry culture-specific meaning that does not transfer word-for-word. Adapt them to equivalent expressions in the target language to preserve the original intent and emotional nuance.