# Translation style guide

> A comprehensive guide for translators working on Onetime Secret localization, covering brand voice, terminology standards, and language-specific requirements to ensure high-quality and consistent translations

## Translation style guide English, Canada (en-CA)

![Translation Style Guide](/socialcards/onetime-socialcard-20250226-1.png)

This style guide provides instruction for translating to the Canadian English locale.

\| *This Style Guide is based on content from [Mozilla L10N Styleguides](https://github.com/mozilla-l10n/styleguides/) by Mozilla Contributors, licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).* | | |

## Target audience

Our English-speaking audience includes:

### Customers

* Professional background: IT professionals, agency teams (design, development, marketing), and corporate support teams (HR, provisioning, logistics, finance)
* Audience: Professionals ages 20-60 with some tech proficiency. These individuals have chosen or work for a company that has chosen to incorporate Onetime Secret into their workflow.
* Location: North America, UK, Ireland, New Zealand, Australia, Netherlands, Germany
* Writing approach: Use clear, accessible language with professional tone

### Recipients

* Audience: Diverse age range (18-80) including students, seniors, parents, clients, coworkers. These individuals may have never heard of Onetime Secret and generally have less context around how it works/
* Writing approach: Clear, accessible language with an empathetic tone

**Translation Note:** These audience descriptions provide context about how the product is used by different groups and should inform translation tone and style. They are not intended to define or limit how we view our customers.

## Brand voice

About the brand voice and tone.

### Core values

* Authentic and transparent

* Patient and focused

* Efficient without sacrificing quality

* Professional yet approachable

### Communication principles

* Adapt tone to match user expertise, from beginners to security professionals

* Balance friendliness with reliability

* Prioritize clarity over casual language

* Provide delightful experiences through thoughtful interactions

### Writing guidelines

* Use clear, direct language that respects users’ time

* Maintain a helpful, patient tone even when explaining complex concepts

* Write with warmth while keeping focus on the task

* Scale technical detail based on user context

* Casual language should not be used at the expense of clarity, regardless of the context.

## Language preferences

*Guidance: This involves determining language-specific preferences, such as spelling variations, punctuation rules, and date and time formats, which resonate with your target audience. — Remember, adhering closely to your audience’s language preferences can significantly reduce barriers to communication and enhance their experience with the brand.*

* Use American English. However for date formats use yyyy-mm-dd and times use 24h. Distances in km, weights in lbs.
* Translations should sound as natural as possible. Whether a borrowed word, such as an English technical term, sounds natural depends on the language, so follow the conventions of your locale. The [universal translation guidance](/en/translations/universal/) has examples from several languages.
* Our english speaking audience is 50% english as a first language and 50% as a second/third/professional language. We need to keep this in mind when choosing terms and phrases to avoid inappropriate or confusing translations.

## Grammar and style guidelines

*Guidance: Pinpoint rules for grammar, style, and punctuation to maintain consistency throughout all your translated content.*

* Use oxford commas, periods, and question marks. Avoid exclamations, contractions, and semi-colons.
* Use active, imperative voice where users take action. Use passive or declarative voice when informing users.
* Sentence fragments are ok on their own. Otherwise full sentences with proper business grammar.
* Divide lengthy information into multiple sentences, if needed.
* In general, use the second person (`you`) to address the user.
* Avoid using the first person (`my`, `I`) as it can create confusion about who is being addressed.

### UI text: when to use active vs passive voice

#### Active, imperative voice (“Do something”)

Buttons ✓ Save changes ✓ Delete file ✓ Send message

Menu items ✓ View settings ✓ Create new folder

#### Passive or declarative voice (“Something happened”)

Status messages ✓ Changes saved ✓ File deleted ✓ Payment declined

Notifications ✓ 3 new messages ✓ Download complete ✓ Server unavailable

System states ✓ Upload in progress ✓ Connection lost ✓ Email address not found

#### Examples in context

Form submission ✓ Save changes (button->active) ✓ Changes saved successfully (status->passive)

File upload ✓ Upload file (button) ✓ Upload complete (status)

## Terminology consistency

*Create a glossary of key terms, along with their approved translations, to ensure consistent usage across all content.*

### Brand terms (do not translate)

* Onetime Secret
* OTS (when used as product abbreviation)
* Identity Plus (product name)
* Global Elite (product name)
* Custom Install (product name)

### About the brand name

In “Onetime Secret”, “Onetime” functions as a compound adjective (also called a attributive adjective) that modifies the noun “Secret”. It describes a key characteristic of the secret - that it can only be accessed once. Note the spelling choice. There are actually three common variants of this term:

* “one-time” (hyphenated)
* “one time” (two words)
* “onetime” (compound)

The hyphenated form “one-time” is considered the standard spelling when the term functions as an adjective before a noun, as in “one-time password” or “one-time code”. This follows the general English rule that compound modifiers before nouns are often hyphenated.

The compound form is the canonical spelling for the brand and company name: Onetime Secret.

### Core concepts

#### Secret management

* **secret** (n.) - The confidential information being shared

  * Translations must maintain the context of confidentiality
  * In English, preferred over terms like “message” or “content”
  * Example: “Create a new secret” not “Create a new message”
  * Some languages use their word for “message” or “content” because their word for “secret” suggests personal or hidden matters. See [Translating “Secret”](/en/translations/universal/secret-concept).

* **one-time** (adj.) - Describing the single-use nature of the service

  * Must emphasize the temporary, single-use aspect
  * Hyphenated when used as adjective
  * Example: “This is a one-time secret” not “This is a single secret”

* **Onetime** (compound adj.) - Part of the brand name Onetime Secret.

  * Must not be used on its own; always paired with “Secret”
  * Example: “Onetime Secret”

* **burn** (v.) - The act of destroying a secret before it’s viewed

  * Technical term for destruction of a secret message
  * Translations should maintain the permanence implied
  * Example: “The secret was burned and no longer available”

#### Security terms

* **encryption** (n.) - The process of encoding secrets

  * Technical term that should remain consistent
  * Distinguish from “encoding” or “hashing”

* **rate limiting** (n.) - System to prevent abuse

  * Technical term for request restriction
  * Keep hyphenation in English
  * Example: “Rate limiting prevents abuse”

* **secure**

* **private**

* **password / passphrase**

* **expiration / expiry / time-to-live**

### Translating key terms

For detailed guidance on translating core concepts, see the universal translation resources:

* **[Translating “Secret”](/en/translations/universal/secret-concept)** - How to handle the word “secret” across different language contexts, with examples from Danish, Dutch, Italian, Chinese, and more. Includes decision process for when to use the “message” exception.

* **[Password vs. Passphrase](/en/translations/universal/password-passphrase)** - Critical distinction between account passwords and secret passphrases, with language-specific examples and translation strategies.

* **[Voice and Tone](/en/translations/universal/voice-and-tone)** - Patterns for active vs. passive voice, formality levels, and cultural adaptations.

* **[Brand Terms](/en/translations/universal/brand-terms)** - Terms that should not be translated (product names, tier names) and guidance on brand name usage.

#### User management

* **colonel** (n.) - Administrator role

  * Project-specific term, rhymes with “kernel” which is a technical term and central component of an operating system. No other project uses this term in this way. It can be confusing even in North America.
  * Translate to the common term for an “administrator” in the context of software permissions. The account with the highest level of privileges.
  * Example: “Only colonels can access this feature” (i.e. “Only admins can access this feature”).

* **plan** (n.) - Subscription level

  * Use consistently for service tiers
  * Prefer over “tier” or “level”
  * Example: “Upgrade to a paid plan”

## Formatting and layout

*Set standards for formatting, layout, and typography to maintain visual and design consistency across different languages.*

* Use consistent header styles to improve readability and content flow. For example H1 for main headings, H2, H3, etc for sub-headings

* Write headings in sentence case unless the heading is a punctuated sentence:

  * Good example: How localization drives growth for fintech firms
  * Good example: Localization made easy. Why wait?
  * Bad example: How Localization Drives Growth for Fintech Firms
  * Bad example: Localization made easy. why wait?

### Time format

Generally, a 12-hour clock is used in the United States. 24-hour clocks are used in aviation and other logistical contexts.

### Numerals

| Symbol Purpose | Character Name | Symbol | Example |
| -------------- | -------------- | ------ | ------- |
| Decimal        | Period         | `.`    | 1.23    |
| Thousands      | Comma          | `,`    | 1,234   |
| Percentage     | Percent sign   | `%`    | 99.95%  |

### Currency

The currency of the Canada is the Canadian Dollar (CAD). The monetary symbols are `$` and rarely `¢`.

### Units of measurement

The imperial system is used for everyday weights in Canada. Everything else including distances, quantities, are in metric. Primarily m, Km, cm, mm (“deci” is used rarely).

### Address and postal code format

```plaintext
[addressee]
[street number and name][building and suite numbers]
[district][city][state/province][postal code]
[Country]


British Columbia Sugar Refinery Ltd.
123 Rogers Street
Vancouver, BC. V6A 3N2
CANADA
```

## Clear, respectful communication

Our goal: We want our writing to connect effectively with all readers while being clear, accurate, and respectful.

To verify your writing achieves these goals, ask:

* Is my language clear and specific?
* Am I addressing my readers directly and respectfully?
* Have I avoided assumptions about my readers?

## Translation style

* Use literal translation for legal or technical texts
* Translate with cultural context when translating content for marketing or advertising
* Use transcreation where you adapt the message so it resonates culturally and emotively with the audience, for creative content including blog posts and marketing copy.

## Related resources

### Universal translation guidance

These resources apply across all languages:

* **[Universal Guidance Overview](/en/translations/universal/)** - Cross-language translation standards
* **[Translating “Secret”](/en/translations/universal/secret-concept)** - Handling the word “secret” in different contexts
* **[Password vs. Passphrase](/en/translations/universal/password-passphrase)** - Maintaining this critical distinction
* **[Voice and Tone](/en/translations/universal/voice-and-tone)** - Voice patterns and formality guidelines
* **[Brand Terms](/en/translations/universal/brand-terms)** - Terms that should not be translated
* **[Quality Checklist](/en/translations/universal/quality-checklist)** - Pre-submission review checklist

### Language-specific resources

* **[Translation Overview](/en/translations/)** - Introduction and available languages
* **[Terminology Glossary](/en/translations/glossary)** - Standardized translations for key terms across languages

### Submission guidelines

* Use the [Translation PR Template](https://github.com/onetimesecret/docs.onetimesecret.com/blob/main/.github/PULL_REQUEST_TEMPLATE/translation.md) when submitting translations
* Review the [Quality Checklist](/en/translations/universal/quality-checklist) before creating your pull request
* Tag language-specific reviewers if known

### Getting help

* Open a [Translation Request Issue](https://github.com/onetimesecret/docs.onetimesecret.com/issues/new?template=translation-request.md) for questions or coordination
* Watch the [GitHub repository](https://github.com/onetimesecret/docs.onetimesecret.com) to follow translation activity
* [Contact the team](https://onetimesecret.com/feedback) for translation support