Global Translation Context

Brand & Terminology

• "Tuist" is a proper noun and should never be translated.
• Technical terms should remain in English: Xcode, Swift, Gradle, API, CLI, SDK, CI/CD, PR, Git, GitHub, S3, CDN, SSO, SAML, OIDC, OAuth, JWT, MFA, TOTP.
• Product feature names should remain in English: Binary Caching, Previews, Registry, Dashboard.

Formatting Rules

• Preserve all HTML tags exactly as they appear in the source.
• Preserve all Elixir string interpolation variables (%{variable_name}) exactly as-is.
• Preserve all markdown formatting.
• Do not translate URLs or email addresses.
• Currency symbols and monetary amounts (e.g., "0EUR", "$9.99") must remain unchanged.
• Numbers like "10K+", "1400+", "300+" should use locale-appropriate formatting only when a clear convention exists, otherwise keep as-is.
• Do not use em dashes (—). Use regular dashes (-) or rephrase instead.

Tone

• Marketing copy: engaging, confident, developer-friendly.
• Dashboard UI: concise, clear, action-oriented.
• Error messages: helpful, non-blaming.
• Documentation: precise, instructional.