This guide adapts rules and examples from Microsoft’s 44-page Belarusian Localization Style Guide (originally written for software/UI localization). The underlying linguistic rules apply universally — to legal contracts, medical documents, marketing copy, and any Belarusian translation work. Restructured and reformatted as a general Belarusian translator reference by ChatsControl.

Belarusian Translation Style Guide — Voice, Word Choice & Common Pitfalls (Legal, Medical, Marketing, IT)¶

TL;DR¶

• Avoid masculine-default gender constructions (Я згодны → Я прымаю); the linking verb ёсць/быць is usually omitted in present tense.
• Pronouns ваш/вашага not capitalized in documentation; minimize вы/ваш — prefer neutral structures and impersonal constructions (для малявання кругоў выкарыстоўвайце мыш not вашу мыш).
• Use chevrons «» in documentation (with straight quotes inside if needed); avoid title-style capitalization completely — title case is non-existent in Belarusian.
• Replace formal Soviet-era forms: у гэты момант → цяпер; вывесці на друк → раздрукаваць; з’яўляцца → быць (often omitted); ніжэйпералічаныя → наступныя; выканаць спробу → паспрабаваць.
• Use imperative verbs for user actions (not infinitives, not nouns); avoid three or more genitive nouns in a row.

Register and tone¶

Three principles: warm and relaxed; crisp and clear; ready to lend a hand.

Avoid passive voice — difficult to read and understand quickly. Write short, easy-to-read sentences. Avoid slang.

Why this matters: Soviet-era formal register damages marketing copy conversion, medical patient material comprehension, software UI friction, and consumer-facing legal text clarity. Sworn legal translation retains formal register.

Word choice¶

Words and phrases to avoid¶

Why this matters: Soviet bureaucratic register feels alien in modern consumer-facing text across all spheres.

Sample voice usage¶

Addressing the user¶

Promoting a feature¶

How-to guidelines¶

Explanatory text and support¶

Language-specific standards¶

Abbreviations¶

Measurement units:

For “day” with variables, use суткі (sut), not дзень (which has forms дзень, дзён, дні that complicate abbreviation).

Don’t abbreviate напрыклад, таму што. Consider бо as a short alternative to таму што.

Acronyms¶

Localized acronyms¶

Don’t use ПК for PC unless space-restricted; use камп’ютар.

Unlocalized acronyms¶

Acronyms without established translation stay in English. No ending is added. Gender determined by main word in full translation. Use descriptor word for declination (or neutral constructions). Descriptor can be omitted in length-restricted contexts (UI) or where the text sounds awkward — but not if grammatical form would be ambiguous.

Position of acronym with noun¶

Capitalization¶

Use sparingly — capitalize only when you have to.

What to capitalize¶

• Names of UI elements (commands, menus, dialog box titles), program names — only the first word: Вышыня і шырыня ячэйкі
• Names of UI elements should have bold/italic formatting, or be in quotes with a descriptor when referenced.

What not to capitalize¶

• Names of week days, months, nationalities, languages: аўторак, чэрвень, іспанцы, польская мова
• Term “web”: выкарыстоўвайце вэб-старонку
• Names of modes, wizards when descriptive: выхад з рэжыму канструктара
• Adjectives derived from country names: японскі камп’ютар
• In multi-word names, only the first word: Дыспетчар кантактаў (not Дыспетчар Кантактаў)
• Word “chapter” and structural units: Дадатковыя звесткі гл. у раздзеле 25.
• “Internet” in compound words: інтэрнэт-суполка, інтэрнэт-крама

The word вэб can only be used in compounds. In simple words, use Інтэрнэт: - (+) Пошук у Інтэрнэце - (-) Пошук у Вэбе

“All caps” or “no caps” English styles are inappropriate for Belarusian. Title-style capitalization is never used.

Conjunctions¶

Avoid formal conjunctions.

Gender¶

Avoid masculine or feminine gender when referring to the user. Use neutral structures.

Localizing colloquialism, idioms, and metaphors¶

• Don’t substitute Belarusian colloquialism unless perfect natural fit.
• Translate intended meaning (not literal) if essential.
• Omit if meaning isn’t affected.

Nouns¶

Grammatical animation of program components¶

All program components and applications (wizards, agents, clients, browsers) are treated as inanimate nouns.

Examples: - выкарыстоўваць (што?) майстар — not выкарыстоўваць (каго?) майстра - усталяваць (што?) кліент — not усталяваць (каго?) кліента

Sequences of nouns in genitive case¶

Avoid three or more nouns in genitive case in a row.

• (+) Каб паскорыць актывацыю праграмнага забеспячэння, патэлефануйце ў службу падтрымкі.
• (-) Для паскарэння актывацыі праграмнага забеспячэння патэлефануйце ў службу падтрымкі.

Prepositions¶

Pay attention to correct preposition use.

Pronouns¶

Capitalization of ваш/вашага¶

Not capitalized in documentation, software, or materials addressed to users in general. Capitalized only in private and business letters to specific people.

Avoiding ваш forms¶

In English “you/your” is used more often than in Belarusian. Avoid forms вы, ваш, вашага, вам whenever possible. Use neutral structures and passive voice.

When “you/your” is necessary to indicate direction, use it:

Punctuation¶

Punctuation must fully comply with Belarusian grammar. Don’t copy source punctuation. Avoid long clumsy sentences and literal translation.

Commas with напрыклад¶

Use commas before and after напрыклад:

• (+) Напрыклад, гэта можа адбыцца, калі ячэйка ўжо выдалена з ліста.
• (+) Сціск не атрымліваецца выканаць, напрыклад, пры перасылцы сціснутых файлаў.

If напрыклад is at the start or end of an unattached clause, no comma separator:

• (+) Задайце дапушчальныя адзінкі, напрыклад цалі альбо сантыметры.

Within parenthetic construction with brackets, use commas as usual:

• (+) Некаторыя элементы (напрыклад, спісы рассылкі) не атрымліваецца экспартаваць у vCard.

Commas with па змаўчанні¶

No commas around па змаўчанні (by default).

• (+) Па змаўчанні значэнне лічыцца роўным REG_SZ.
• (-) Па змаўчанні, значэнне лічыцца роўным REG_SZ.

Commas with дзякуючы¶

No comma after дзякуючы phrase at the start of a sentence.

• (+) Дзякуючы такой архітэктуры сеткі ўстойлівыя да атак звонку.
• (-) Дзякуючы такой архітэктуры, сеткі ўстойлівыя да атак звонку.

Colon¶

Colon after alerting words (“Attention”, “Warning”, “Caution”) should be replaced with exclamation mark.

Regular text may not be capitalized after a colon in Belarusian. Such capitalization is a language error. Exceptions: lists, direct speech, new paragraph.

Dashes and hyphens¶

Hyphen — divides words between syllables, links compound parts. No spaces before or after; not a dash substitute.

En dash — minus sign with spaces. No space for negative numbers.

Em dash — for dashes wherever technically possible. Separates words and has grammatical function. Don’t substitute with hyphens.

Notes and examples formatting¶

Single in-text notes/examples introduced by “Заўвага” or “Прыклад” followed by full stop. Full stop same formatting as preceding word.

Slash¶

Avoid slashes. Substitute with conjunctions альбо or і.

Slashes can be used in length-restricted contexts (UI).

Ellipses (suspension points)¶

Used to indicate omission, pause, or unfinished thought. Always written together with preceding word, no spaces.

Period¶

Missing trailing period is a language error in regular text. Sentence ends with period unless title, heading, table column/row titles, picture labels.

Quotation marks¶

Use straight quotation marks in software, product help, and web pages (same as English). Don’t use single quotation marks.

In documentation use chevrons «…» with straight quotes inside if needed: «кнопка “Гатова”».

Period stands outside the chevrons.

Workarounds for unsupported double quotes: use two sequenced single quote characters (‘’); use codes (&quot in HTML).

Parentheses¶

No space between parentheses and text inside. Period placement depends on what they enclose: outside the closing bracket if parentheses enclose part of sentence; inside if they enclose full sentence.

Sentence fragments¶

Symbols and non-breaking spaces¶

Use non-breaking spaces to avoid part of word/phrase moving to next line:

1. As thousands separator (10 000)
2. Before % in documentation (10 %)
3. Between number and following unit (5 кг, 5 °C)
4. Between person’s initials and last name (А. А. Сідараў)
5. In contractions (і г. д.)
6. Before a dash (Файл — гэта…)

Verbs¶

Use verbs in imperative mood to engage the user directly. Never use infinitives (style error). Avoid noun phrases and constructions with можна, вы можаце.

• (-) Адлюстроўваць дзеянні вашых сяброў у іншых сэрвісах і дзяліцца дадатковымі рэсурсамі з сябрамі ў сэрвісе Windows Services.
• (+) Вы зможаце бачыць дзеянні вашых сяброў у іншых сэрвісах і дзяліцца з сябрамі дадатковымі рэсурсамі ў службе Windows Services.

When describing actions, use imperative:

• (+) Перад тым як працягваць, усталюйце неабходныя кампаненты.
• (-) Перад тым як працягваць, трэба усталяваць неабходныя кампаненты.

Recommended to use verbs (not nouns) in purpose clauses. Exception: standard phrase Для атрымання дадатковых звестак.

• (+) Каб перамясціць ячэйкі паміж аркушамі, перацягніце вылучаны дыяпазон на ярлычок у ніжняй частцы аркуша.
• (-) Для перамяшчэння ячэек паміж аркушамі, перацягніце вылучаны дыяпазон на ярлычок у ніжняй частцы аркуша.

Localization considerations¶

Localized text must be accurate, correct, and clear. Avoid wordiness and word-by-word translation.

• Accuracy. As a rule, all English text needs to be translated. Text can be omitted/added with specific reason and project team checking.
• Localization. Adapt to local language, customs, and standards. In many cases use Belarusian names rather than English: Edward → Васіль, New York → Мінск.
• Consistency. Ensure terminology consistent within component and across components. Across products too. Consistent style, register, and translation of similar phrases.

Applications, products, and features¶

Product and application names often trademarked. Feature names occasionally trademarked (IntelliSense™).

Version numbers¶

Trademarks¶

Trademarked names and Microsoft Corporation should not be localized unless local laws require translation.

Geopolitical concerns¶

Maps, flags, country/region/city/language names, art and graphics, cultural content with historical or political references — verify currency. Maps and graphical representations of countries/regions should be checked for accuracy and political restrictions.

Software considerations¶

Error messages¶

Standard phrases in error messages¶

Keys¶

Most key names kept in English. Arrow keys, Spacebar translated.

FAQ¶

What’s the right register for Belarusian translation?¶

Clear, friendly, conversational. Avoid Soviet-era bureaucratic vocabulary (у гэты момант, з’яўляцца, ніжэйпералічаныя, выканаць спробу) and replace with modern equivalents (цяпер, быць, наступныя, паспрабаваць). Avoid the formal conjunctions з той прычыны, што / паколькі / з мэтай in favor of бо / таму што / каб.

How should I handle ваш / your in Belarusian?¶

Avoid forms вы / ваш / вашага / вам whenever possible. Use neutral structures and impersonal constructions instead. “Use your mouse” → Для малявання кругоў выкарыстоўвайце мыш (not вашу мыш). When direction is necessary (Вы далучаецеся да сходу), use it. The pronouns ваш/вашага are not capitalized in documentation or software addressed to general users.

What punctuation rules are Belarusian-specific?¶

Use chevrons «…» in documentation, straight quotes “…” in software and web. Period stands outside chevrons (Дадатковыя звесткі гл. ў раздзеле «Налады».). No comma after па змаўчанні (by default). No comma after дзякуючы at the start of a sentence. Use comma before and after напрыклад. Slash is to be avoided — use альбо or і instead.

How do I handle nouns and case forms?¶

All program components (wizards, agents, clients, browsers) treated as inanimate nouns — выкарыстоўваць (што?) майстар, not майстра (which would be animate). Avoid sequences of three or more nouns in genitive case — replace with verb-based constructions. Каб паскорыць актывацыю не Для паскарэння актывацыі.

Which key Belarusian-specific terms should be used?¶

ПК for personal computer (not персанальны камп’ютар); АС for OS (not аперацыйная сістэма); пошта for email (not электронная пошта); паведамленне or ліст for email message (not паведамленне электроннай пошты); CD-прывад for CD drive.

How are acronyms handled with case marking?¶

Position of acronym before or after the noun, and presence of dash, depends on the noun. With dash after acronym: IP-адрас, WINS-запіс, DHCP-запыт, DNS-імя, RAS-кліент, OSPF-маршрут, IP-пакет, IP-маршрутызацыя, DHCP-сервер, DOC-файл. Without dash before acronym: зона DNS, кліент UNIX, мадэль COM, пратакол IP, рэплікацыя WINS, сервер UNIX, сэрвіс RAS, том NTFS.

How is gender handled?¶

Avoid using masculine or feminine gender when referring to the user. Use neutral structures and select verbs that don’t discriminate either sex. “I accept” → Я прымаю (not Я згодны / Я згодная).

Sources¶

• Microsoft Localization Style Guides hub
• Microsoft Language Portal