Spring til indhold

Oversættelsesvejledning til dansk

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

The Danish translation aims to:

  • Maintain consistency across all application interfaces
  • Use clear, natural phrasing for Danish-speaking audiences
  • Follow technical accuracy for security-related terminology
  • Apply appropriate voice and tone for different contexts
  • Avoid inappropriate connotations through careful word choice

EnglishDansk (DA)ContextNotes
secret (noun)beskedCentral application conceptUse “besked” (message) instead of “hemmelighed” to avoid childish/personal connotations
secret (adj)hemmelig/sikkerDescriptive use
passphraseadgangssætningAuthentication method for secretsDistinct compound term for secret protection
passwordadgangskodeAccount login credentialStandard term for account passwords only
burnødelægAction to delete a secret before viewingPermanent deletion action
view/revealvis/åbenAction to access a secretDisplay/show content
linklinkURL providing access to a secret
encrypt/encryptedkrypter/krypteretSecurity method
securesikkerProtection state
EnglishDansk (DA)ContextNotes
Share a secretDel en beskedPrimary action
Create AccountOpret kontoRegistration
Sign InLog indAuthentication
DashboardOversigtUser’s main page
SettingsIndstillingerConfiguration page
Privacy OptionsPrivatlivsindstillingerSecret configuration
FeedbackFeedbackUser feedback
EnglishDansk (DA)ContextNotes
receivedmodtagetSecret has been viewedPast participle for status
burnedødelagtSecret was deleted before viewingPast participle for status
expiredudløbetSecret no longer available due to timePast participle for status
createdoprettetSecret has been generatedPast participle for status
activeaktivSecret is available
inactiveinaktivSecret is not available
EnglishDansk (DA)Context
expires inudløber omTime until secret becomes unavailable
day/daysdag/dageTime unit
hour/hourstime/timerTime unit
minute/minutesminut/minutterTime unit
second/secondssekund/sekunderTime unit
EnglishDansk (DA)Context
one-time accessengangsadgangCore security feature
passphrase protectionadgangssætningsbeskyttelseAdditional security
encrypted in transitkrypteret under overførselData protection method
encrypted at restkrypteret under lagringStorage protection
EnglishDansk (DA)Context
emaile-mailUser identifier
passwordadgangskodeAccount authentication
accountkontoUser profile
subscriptionabonnementPaid service
customerkundePaying user
EnglishDansk (DA)Context
custom domainbrugerdefineret domænePremium feature
domain verificationdomænebekræftelseSetup process
DNS recordDNS-postConfiguration
CNAME recordCNAME-postDNS configuration
EnglishDansk (DA)Context
errorfejlProblem notification
warningadvarselCaution notification
oopsupsFriendly error introduction
EnglishDansk (DA)ContextNotes
submitsendForm actionImperative form
cancelannullerNegative actionImperative form
confirmbekræftPositive actionImperative form
copy to clipboardkopier til udklipsholderUtility actionImperative form
continuefortsætNavigationImperative form
backtilbageNavigation
createopretImperative form for buttons
savegemImperative form for buttons
savedgemtPast participle for status
sharedelShare/distributeImperative form
EnglishDansk (DA)Context
secure linkssikre linksProduct feature
privacy-first designprivatlivs-først designDesign philosophy
custom brandingbrugerdefineret brandingPremium feature

  • Use the same translation for a term throughout the application
  • Maintain standardized terminology from the glossary above
  • Key distinctions to preserve:
    • adgangskode for account passwords
    • adgangssætning for secret protection
    • besked as the core concept (not “hemmelighed”)
  • 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
  • Use standard Danish that works across regions
  • Use standard technical terms familiar to Danish-speaking users
  • Security-related terms must be translated accurately
  • Prioritize precision over localization for technical terminology
  • Use established Danish technical vocabulary

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

  • Opret besked (Create secret)
  • Kopier til udklipsholder (Copy to clipboard)
  • Opret konto (Create account)
  • Gem (Save)
  • Del (Share)

Passive/Declarative Voice (for Information)

Sektion kaldt “Passive/Declarative Voice (for Information)”

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

  • Besked oprettet (Secret created - status)
  • Din sikre besked vises nedenfor. (Your secure message is shown below.)
  • Beskeden blev ødelagt manuelt... (The secret was manually destroyed…)
  • Gemt (Saved - status message)
  • Use informal address consistently when addressing users
  • Examples:
    • Indtast din adgangskode (Enter your password)
    • Din sikre besked (Your secure message)
  • Danish naturally flows with direct address in most contexts
  • Prioritize natural Danish expressions over literal translations
  • Use standard phrases familiar to Danish speakers
  • Avoid literal translations that sound awkward in Danish
  • Ensure all user-facing strings are translated
  • Avoid leaving English text in the interface
  • Translate help text, descriptions, and metadata

9. Compound Words with English Loanwords

Sektion kaldt “9. Compound Words with English Loanwords”

When creating compound words that include English loanwords, use hyphens:

  • besked-apps (hyphenated)
  • besked apps (separate words)
  • API-nøgle (hyphenated)
  • API nøgle (separate words)

Use imperative forms:

  • Indtast din adgangskode (Enter your password)
  • Kopier til udklipsholder (Copy to clipboard)
  • Indtast adgangssætningen her (Enter the passphrase here)

Use passive voice or past participles:

  • Kopieret til udklipsholder (Copied to clipboard)
  • Besked oprettet (Secret created)
  • Gemt (Saved)
  • Oprettet (Created)

Use declarative sentences:

  • Du ser det sikre indhold (You are viewing the secure content)
  • Dette indhold vises kun én gang (This content is shown only once)

Use clear, direct language:

  • Forkert adgangssætning (Incorrect passphrase)
  • Der opstod en fejl (An error occurred)

ALWAYS use “besked” (message), NEVER use “hemmelighed” (secret)

The Danish word “hemmelighed” carries inappropriate connotations:

  • Personal or private secrets (gossip, hidden information)
  • Childish or trivial usage
  • Meanings that sound unprofessional in a business context

Native speaker feedback confirms that “hemmelighed” evokes associations with personal secrets rather than business security.

Examples:

  • Du har 3 nye beskeder (You have 3 new messages)
  • Du har 3 nye hemmeligheder (You have 3 new secrets)
  • Opret en besked (Create a secret)
  • Opret en hemmelighed (Create a secret)

Critical distinction that must be maintained:

  • adgangskode - for user account login credentials ONLY
  • adgangssætning - for protecting individual secrets

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

Examples:

  • Indtast din adgangskode (Enter your password - account login)
  • Indtast din adgangssætning (Enter your passphrase - account login)
  • Beskyt med adgangssætning (Protect with passphrase - secret protection)
  • Beskyt med adgangskode (Protect with password - secret protection)

Consistently translated as ødelæg (verb) / ødelagt (past participle):

  • Conveys the permanent, irreversible nature of deletion
  • Examples:
    • Ødelæg denne besked (Burn this secret - button)
    • Beskeden er ødelagt (The secret is burned - status)
  • Follow platform conventions for the target language
  • Use standard Danish terminology for common UI elements
  • Maintain consistency with other Danish applications
  • Prioritize accuracy over casual localization
  • Use established Danish technical vocabulary
  • Examples:
    • krypteret (encrypted)
    • krypter (to encrypt)
    • bekræftelse (verification)
    • godkendelse (authentication)

RuleCorrectIncorrectExample
”Secret” → “Besked” (NOT “Hemmelighed”)beskedhemmelighed✓ Du har 3 nye beskeder; ✗ Du har 3 nye hemmeligheder
Password vs. Passphraseadgangskode (login), adgangssætning (secret)Mixed usage✓ Indtast din adgangskode (login); ✗ Indtast din adgangssætning (login)
Buttons: ImperativeOpret, Del, GemNoun forms✓ Opret besked (button); ✗ Oprettelse af besked (button)
Status: Passive formOprettet, GemtImperative in status✓ Besked oprettet (status); ✗ Opret besked (status)
Compound words with English loanwordsbesked-apps, API-nøglebesked apps, API nøgle✓ besked-apps (hyphenated); ✗ besked apps (separate words)

Rationale for Danish-Specific Adjustments

Sektion kaldt “Rationale for Danish-Specific Adjustments”

The Danish translation requires special attention to:

  1. “Besked” instead of “Hemmelighed”: The word “hemmelighed” has childish/personal connotations in everyday Danish that undermine the professional/security context. Using “besked” maintains a business-appropriate tone.

  2. Clear Password/Passphrase Distinction: Using “adgangskode” for account login and “adgangssætning” for secret protection ensures users understand the different security contexts.

  3. Imperative for Actions, Passive for Status: Danish UI conventions strongly favor imperative forms for buttons and passive/past participle forms for status messages.

  4. Compound Word Hyphenation: When combining Danish words with English loanwords, hyphens are necessary for proper Danish orthography.


The Danish translation maintains:

  1. Terminology Consistency - Standardized key terms throughout the application
  2. Appropriate Voice - Imperative for actions, passive/past participles for information
  3. Natural Phrasing - Standard Danish expressions and sentence structures
  4. Consistent Address - Direct address when addressing users
  5. Complete Coverage - All user-facing strings translated
  6. Technical Accuracy - Precise terminology for security concepts
  7. Clear Distinctions - Especially:
    • Account passwords (adgangskode) and secret passphrases (adgangssætning)
    • Using besked (message) instead of hemmelighed (secret)
    • Action verbs (imperative) and status messages (passive/past participle)
  8. Proper Orthography - Hyphenated compound words with English loanwords

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