Saltar al contenido

Guía de traducción al español

This document combines the glossary of standardized terms and language-specific translation notes for Spanish translations of Onetime Secret. It serves as a comprehensive reference for translators working on the Spanish locale to ensure consistency, accuracy, and natural phrasing.

The Spanish translation aims to:

  • Maintain consistency across all application interfaces
  • Use clear, natural phrasing for Spanish-speaking audiences
  • Follow technical accuracy for security-related terminology
  • Apply appropriate voice and tone for different contexts
  • Distinguish between neutral Spanish where possible while remaining accessible

EnglishEspañol (ES)ContextNotes
secret (noun)secretoCentral application conceptEmphasizes the confidential item being shared
secret (adj)secreto/seguroDescriptive use
passphrasefrase de contraseñaAuthentication method for secretsCompound term distinguishing from account password
passwordcontraseñaAccount login credentialStandard term for account passwords
burndestruirAction to delete a secret before viewingConsistently use verb/past participle forms
view/revealver/mostrarAction to access a secret
linkenlaceURL providing access to a secret
encrypt/encryptedcifrar/cifradoSecurity method
secureseguroProtection state
EnglishEspañol (ES)ContextNotes
Share a secretCompartir un secretoPrimary action
Create AccountCrear una cuentaRegistration
Sign InIniciar sesiónAuthenticationVery common term for logging in
DashboardPanelUser’s main pageMore accurate than “Cuenta” for this context
SettingsConfiguraciónConfiguration page
Privacy OptionsOpciones de privacidadSecret configuration
FeedbackComentariosUser feedback
EnglishEspañol (ES)ContextNotes
receivedrecibidoSecret has been viewed
burneddestruidoSecret was deleted before viewingStandardized form
expiredexpiradoSecret no longer available due to time
createdcreadoSecret has been generated
activeactivoSecret is available
inactiveinactivoSecret is not available
EnglishEspañol (ES)Context
expires inexpira enTime until secret becomes unavailable
day/daysdía/díasTime unit
hour/hourshora/horasTime unit
minute/minutesminuto/minutosTime unit
second/secondssegundo/segundosTime unit
EnglishEspañol (ES)Context
one-time accessacceso únicoCore security feature
passphrase protectionprotección mediante frase de contraseñaAdditional security
encrypted in transitcifrado en tránsitoData protection method
encrypted at restcifrado en reposoStorage protection
EnglishEspañol (ES)Context
emailcorreo electrónicoUser identifier
passwordcontraseñaAccount authentication
accountcuentaUser profile
subscriptionsuscripciónPaid service
customerclientePaying user
EnglishEspañol (ES)Context
custom domaindominio personalizadoPremium feature
domain verificationverificación del dominioSetup process
DNS recordregistro DNSConfiguration
CNAME recordregistro CNAMEDNS configuration
EnglishEspañol (ES)Context
errorerrorProblem notification
warningadvertenciaCaution notification
oopsupsFriendly error introduction
EnglishEspañol (ES)ContextNotes
submitenviarForm action
cancelcancelarNegative action
confirmconfirmarPositive action
copy to clipboardcopiar al portapapelesUtility actionStandard Spanish phrase
continuecontinuarNavigation
backatrásNavigation
EnglishEspañol (ES)Context
secure linksenlaces segurosProduct feature
privacy-first designdiseño que prioriza la privacidadDesign philosophy
custom brandingmarca personalizadaPremium feature

  • Use the same translation for a term throughout the application
  • Maintain standardized terminology from the glossary above
  • Key distinctions to preserve:
    • contraseña for account passwords
    • frase de contraseña for secret protection
    • secreto as the core concept
  • Consider how the term is used in the application
  • Account for surrounding UI elements and user flow
  • Ensure translations make sense in their specific context
  • Adapt terms to local conventions when necessary
  • Aim for neutral Spanish that works across regions
  • Use standard technical terms familiar to Spanish-speaking users
  • Security-related terms must be translated accurately
  • Prioritize precision over localization for technical terminology
  • Use established Spanish technical vocabulary

Use imperative voice for buttons, links, and user actions:

  • Generar Contraseña (Generate Password)
  • Copiar al portapapeles (Copy to clipboard)
  • Crear una cuenta (Create Account)

Use passive or declarative voice for informational text, status messages, and descriptions:

  • Tu mensaje seguro se muestra a continuación. (Your secure message is shown below.)
  • El enlace secreto ha sido creado... (The secret link has been created…)
  • El secreto fue destruido manualmente... (The secret was manually destroyed…)
  • Estás viendo... (You are viewing…)
  • Use informal “tú” form consistently when addressing users
  • Examples:
    • Introduce tu contraseña (Enter your password)
    • Tu mensaje seguro (Your secure message)
    • Estás viendo... (You are viewing…)
  • When direct address can be avoided, use 3rd person passive:
    • Se notificará... (Will be notified…)
  • Prioritize natural Spanish expressions over literal translations
  • Use standard phrases familiar to Spanish speakers:
    • Preguntas Frecuentes instead of F.A.Q.
    • Cargando... for loading states
    • Recuérdame for “Remember me” checkboxes
  • Ensure all user-facing strings are translated
  • Avoid leaving English text in the interface
  • Translate help text, descriptions, and metadata

Use imperative or infinitive forms:

  • Introduce tu contraseña (Enter your password)
  • Copiar al portapapeles (Copy to clipboard)

Use passive voice or past participles:

  • Copiado al portapapeles (Copied to clipboard)
  • El secreto ha sido creado (The secret has been created)

Use declarative sentences in 2nd person informal:

  • Estás viendo el contenido secreto (You are viewing the secret content)
  • Este contenido se muestra solo una vez (This content is shown only once)

Use clear, direct language:

  • Frase de contraseña incorrecta (Incorrect passphrase)
  • Ha ocurrido un error (An error has occurred)

  • Fundamental to the application - translate consistently as secreto
  • Emphasizes the confidential nature of the shared item
  • Distinguishes from personal secrets or confidential information in general

Critical distinction:

  • contraseña - for user account login credentials
  • frase de contraseña - for protecting individual secrets

This distinction must be maintained throughout the application to avoid confusion.

  • Follow platform conventions for the target language
  • Use standard Spanish terminology for common UI elements
  • Maintain consistency with other Spanish applications
  • Prioritize accuracy over casual localization
  • Use established Spanish technical vocabulary
  • Examples:
    • cifrado (encrypted)
    • cifrar (to encrypt)
    • verificación (verification)
    • autenticación (authentication)

The Spanish translation maintains:

  1. Terminology Consistency - Standardized key terms throughout the application
  2. Appropriate Voice - Imperative for actions, passive/declarative for information
  3. Natural Phrasing - Standard Spanish expressions and idioms
  4. Consistent Address - Informal “tú” form when addressing users
  5. Complete Coverage - All user-facing strings translated
  6. Technical Accuracy - Precise terminology for security concepts
  7. Clear Distinctions - Especially between account passwords and secret passphrases

By following these guidelines, translators can ensure that the Spanish version of Onetime Secret is accurate, consistent, and provides a natural user experience for Spanish-speaking audiences.