Skip to content

Руководство по переводу на русский язык

Translation Guidance for Russian (Русский)

Section titled “Translation Guidance for Russian (Русский)”

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

The Russian translation aims to:

  • Maintain consistency across all application interfaces
  • Use clear, natural phrasing for Russian-speaking audiences
  • Follow technical accuracy for security-related terminology
  • Apply appropriate voice and tone for different contexts
  • Properly handle Russian grammatical cases, genders, and plural forms

EnglishРусский (RU)ContextNotes
secret (noun)секретCentral application conceptMasculine gender; appropriate for professional contexts
secret (adj)секретный/безопасныйDescriptive use
passphraseкодовая фразаAuthentication method for secretsCompound term distinguishing from account password
passwordпарольAccount login credentialStandard term for account passwords
burnокончательное удалениеAction to delete a secret before viewingPermanent deletion
view/revealпросмотр/раскрытиеAction to access a secret
linkссылкаURL providing access to a secretFeminine gender
encrypt/encryptedшифрование/зашифрованныйSecurity method
secureбезопасныйProtection state
EnglishРусский (RU)ContextNotes
Share a secretПоделиться секретомPrimary action
Create AccountСоздать учётную записьRegistration
Sign InВойтиAuthentication
DashboardПанель управленияUser’s main page
SettingsНастройкиConfiguration page
Privacy OptionsПараметры конфиденциальностиSecret configuration
FeedbackОбратная связьUser feedback
EnglishРусский (RU)ContextNotes
receivedполученоSecret has been viewed
burnedокончательно удаленоSecret was deleted before viewing
expiredистёкSecret no longer available due to time
createdсозданоSecret has been generated
activeактивныйSecret is available
inactiveнеактивныйSecret is not available
EnglishРусский (RU)ContextNotes
expires inистекает черезTime until secret becomes unavailable
day/daysдень/дня/днейTime unit1 день, 2-4 дня, 5+ дней
hour/hoursчас/часа/часовTime unit1 час, 2-4 часа, 5+ часов
minute/minutesминута/минуты/минутTime unit1 минута, 2-4 минуты, 5+ минут
second/secondsсекунда/секунды/секундTime unit1 секунда, 2-4 секунды, 5+ секунд
EnglishРусский (RU)Context
one-time accessодноразовый доступCore security feature
passphrase protectionзащита кодовой фразойAdditional security
encrypted in transitзашифровано при передачеData protection method
encrypted at restзашифровано при храненииStorage protection
EnglishРусский (RU)Context
emailэлектронная почтаUser identifier
passwordпарольAccount authentication
accountучётная записьUser profile
subscriptionподпискаPaid service
customerклиентPaying user
EnglishРусский (RU)Context
custom domainпользовательский доменPremium feature
domain verificationпроверка доменаSetup process
DNS recordDNS-записьConfiguration
CNAME recordCNAME-записьDNS configuration
EnglishРусский (RU)Context
errorошибкаProblem notification
warningпредупреждениеCaution notification
oopsупсFriendly error introduction
EnglishРусский (RU)ContextNotes
submitотправитьForm action
cancelотменитьNegative action
confirmподтвердитьPositive action
copy to clipboardкопировать в буфер обменаUtility action
continueпродолжитьNavigation
backназадNavigation
EnglishРусский (RU)Context
secure linksбезопасные ссылкиProduct feature
privacy-first designдизайн, ориентированный на конфиденциальностьDesign philosophy
custom brandingперсонализированный брендингPremium feature

  • Use the same translation for a term throughout the application
  • Maintain standardized terminology from the glossary above
  • Key distinctions to preserve:
    • пароль for account passwords
    • кодовая фраза for secret protection
    • секрет 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
  • Use modern Russian suitable for digital interfaces
  • Use standard technical terms familiar to Russian-speaking users
  • Security-related terms must be translated accurately
  • Prioritize precision over localization for technical terminology
  • Use established Russian technical vocabulary
  • Use polite вы forms for professional tone
  • Maintain professional but approachable language
  • Ensure consistency in formality level across all interfaces
  • Russian uses Cyrillic alphabet with 33 letters
  • Essential: use Ё where needed for clarity (not just Е)
  • Never substitute Cyrillic with Latin look-alikes
  • Russian has 6 cases (именительный, родительный, дательный, винительный, творительный, предложный)
  • Apply correct case declension based on context
  • Examples of important gender assignments:
    • секрет (masculine)
    • ссылка (feminine)
    • шифрование (neuter)
  • Masculine, feminine, and neuter
  • Ensure proper gender agreement with adjectives and past participles
  • Important genders to remember:
    • секрет (masculine) - создан
    • ссылка (feminine) - создана
    • шифрование (neuter) - создано

Russian requires three plural forms based on quantity:

  • 1: singular (день, час, минута, секунда)
  • 2-4: first plural form (дня, часа, минуты, секунды)
  • 5+: second plural form (дней, часов, минут, секунд)

This applies to all countable nouns and must be implemented correctly.

  • Russian verbs have perfective and imperfective aspects
  • Perfective: completed action (создать - to create, once)
  • Imperfective: ongoing/repeated action (создавать - to be creating)
  • Choose appropriate aspect based on context
  • Prioritize natural Russian expressions over literal translations
  • Use standard phrases familiar to Russian speakers
  • Ensure terminology is accessible and professional
  • Ensure all user-facing strings are translated
  • Avoid leaving English text in the interface
  • Translate help text, descriptions, and metadata

Use infinitive or imperative forms with polite вы

Use past participles with correct gender agreement

Use declarative sentences with polite second person (вы)

Use clear, direct language with professional tone


  • Fundamental to the application - translate consistently as секрет
  • Masculine gender
  • Appropriate for professional contexts
  • Emphasizes the confidential nature of the shared item

Critical distinction:

  • пароль - for user account login credentials
  • кодовая фраза - for protecting individual secrets

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

  • Translated as окончательное удаление (permanent deletion)
  • More natural in digital Russian context than literal translation
  • Clearly conveys permanent deletion concept
  • Always use Ё where needed, not just Е
  • Omitting Ё can cause confusion or misreading
  • Example: всё (everything) vs все (all/everyone)
  • Essential for clarity and proper pronunciation
  • Adjectives and past participles must agree with noun gender
  • Incorrect gender agreement sounds unnatural
  • Examples:
    • секрет создан (masculine - the secret was created)
    • ссылка создана (feminine - the link was created)
    • сообщение создано (neuter - the message was created)
  • Three-form plural system is mandatory
  • Native speakers immediately notice errors
  • Must implement correct form based on number:
    • 1 день, 21 день, 101 день (singular)
    • 2 дня, 3 дня, 4 дня, 22 дня (2-4 form)
    • 5 дней, 10 дней, 25 дней (5+ form)
  • Follow platform conventions for Russian interfaces
  • Use standard Russian terminology for common UI elements
  • Maintain consistency with other Russian applications
  • Prioritize accuracy over casual localization
  • Use established Russian technical vocabulary
  • Examples:
    • шифрование (encryption)
    • зашифрованный (encrypted)
    • проверка (verification)
    • аутентификация (authentication)
  • Use perfective aspect for completed actions (results)
  • Use imperfective aspect for processes or repeated actions
  • Examples:
    • создать секрет (create a secret - one action, perfective)
    • создавать секреты (create secrets - repeated, imperfective)

The Russian translation maintains:

  1. Terminology Consistency - Standardized key terms throughout the application
  2. Grammatical Accuracy - Proper use of 6 cases, 3 genders, and plural forms
  3. Natural Phrasing - Standard Russian expressions and idioms
  4. Cyrillic Integrity - Correct use of all Cyrillic letters including Ё
  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
  8. Professional Tone - Polite вы form for respectful communication
  9. Aspect Awareness - Proper use of perfective/imperfective verb aspects

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