This guide adapts rules and examples from Microsoft’s 71-page Serbian Localization Style Guide (originally written for software/UI localization). The underlying linguistic rules apply to both Cyrillic (ћирилица) and Latin (latinica) Serbian — Microsoft ships both. The guide applies universally to legal contracts, medical documents, marketing copy, and any English-to-Serbian translation. Restructured and reformatted as a general translator reference by ChatsControl. (Examples in this guide use the Latin form from the source style guide; Cyrillic equivalents apply directly via straightforward transliteration.)

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

TL;DR¶

• Serbian translation across all spheres requires rewriting source rather than literal mapping — English constructions like “to make something more X”, “you might want to”, and over-possessives produce stilted Serbian unless restructured.
• Avoid anglicisms (locirati → pronaći, butovati/startovati → pokrenuti, zahtevati → potrebno je da, takođe → i…), Soviet/bureaucratic Serbian (biti u mogućnosti → moći), and false friends (industrija when meaning branša).
• Possessive pronouns from English (‘your’) are usually omitted in Serbian — keep only when ownership truly matters; when subject and object match, use svoj (not vaš); never inflect product/trademark names (Microsoft, not Microsoft-a).
• Address users with lowercase formal 2nd-person plural vi/vaš — avoid third-person ‘korisnik’ references; lengthy genitive constructions (‘od strane’) signal literal translation and must be reworked.
• Authoritative references: Pravopis srpskoga jezika (Matica srpska 2010), Rečnik srpskoga jezika, Stevanović’s Savremeni srpski jezik, Piper/Klajn’s Normativna gramatika srpskog jezika (2014), Klajn’s Rečnik jezičkih nedoumica.

Register and tone for modern Serbian translation¶

Register is the level of formality, warmth, and conversational ease the target text projects. Modern Serbian readers across consumer-facing spheres expect a register that feels human rather than bureaucratic — formal Serbian carries administrative associations that signal distance.

Three principles:

• Warm and relaxed. Less formal, more grounded in honest conversation. Speak like a real person, not a system.
• Crisp and clear. Written for scanning first. Short sentences. Simplicity is the default.
• Ready to help. Anticipates what the reader needs.

Important caveat for Serbian: Heavy marketing phrases that work in English often sound aggressive in Serbian and produce the opposite effect from intended. Tone down promotional copy when translating.

Why this matters: Bureaucratic register damages outcomes across spheres. In marketing copy for the Serbian market it reduces conversion — readers sense the foreign tone immediately. In patient-facing medical materials it reduces comprehension and compliance. In software UI and IT documentation it creates friction at every interaction. In consumer-facing legal documents plain-language standards apply.

Audience targeting¶

Use technical terms for technical audiences; for consumers use common words. A clinical drug monograph for prescribers uses precise pharmacological terminology; the patient leaflet for the same drug uses everyday Serbian. A software API reference uses developer jargon; the end-user help article uses plain Serbian. Legal translation for corporate counsel uses procedural shorthand; consumer-facing versions need plain-Serbian framing.

Flexibility: rewrite, don’t translate word-for-word¶

Translators should modify or rewrite translated strings to be appropriate and natural for Serbian customers. Understand the whole intention of sentences, paragraphs, and pages, then rewrite as if composing the content yourself.

Rule of thumb: translate the message, not the sentence. If preserving the message requires changes, make them. Don’t make changes that would ruin the message itself.

This is especially important for idiomatic or humorous lines. If there is no way to keep subtle humor or a pun or cultural reference, rephrase it.

Phrases redundant in Serbian¶

Some English phrases sound redundant in Serbian — drop “please”, “to help do something”, “you might want to” and so on to achieve better fluency.

The “make something X” trap¶

English “to make something (more) X” often appears literally translated as “učiniti X-ijim” — this is artificial in Serbian since no native speaker uses it in daily speech. Rework using direct verbs.

Other idiomatic reworks¶

Why this matters: Source-faithful translation produces translatorese. Required in sworn legal translation where literal accuracy is mandated. Harmful in marketing translation (lost conversion), patient-facing healthcare (lost clarity), and software UX (lost engagement).

Word choice: short forms and everyday words¶

Where the word does not need to be inflected, feel free to omit the usual modifier.

Words and phrases to avoid¶

Microsoft voice avoids unnecessarily formal tone. Similar pairs apply in Serbian.

Don’t invent words or apply new meanings to standard words. Some terms (hacker, streaming, rooting) are already part of everyday speech.

Use everyday words¶

Imagine you’re looking over a friend’s shoulder explaining how to accomplish the task.

Why this matters: In legal translation anglicisms (lociranje, butovati) read as unprofessional and reduce document credibility. In medical translation they create ambiguity for patients. In marketing copy they signal poor localization. In software UI they make the product feel “translated by machine” — the perception Serbian localization must avoid.

Inclusive language and bias-free communication¶

Use plain, accessible language. Be mindful when referring to parts of the world — avoid politically disputed regions in examples. Represent diverse perspectives. Don’t generalize or stereotype people by region, culture, age, or gender, not even with positive stereotypes. Don’t use profane, derogatory, or slang terms.

Avoid gender bias¶

Use gender-neutral alternatives. Avoid compounds containing gender-specific terms. Serbian is more likely to need gendered nouns (predstavnik or predstavnica prodaje) — this can jeopardize comprehension and consumes space. Use neutral language as much as possible or rewrite in plural.

For generalizations, use plural noun forms (ljudi, osobe, pojedinci, lica).

In cases like personalized letters, use suffix /a:

Don’t use gendered pronouns (ona, nju/njoj, on, njega/njemu) in generic references. Instead:

• Rewrite to use second or third person plural (vi, oni, bezlično se).
• Rewrite with plural noun and pronoun.
• Use determiners instead of a pronoun (ovaj/dati dokument instead of njegov dokument).
• Refer to a person’s role (čitalac, zaposleni, kupac ili klijent). Avoid gender distinction where possible.
• Use osoba, pojedinac, lice.

Accessibility — people-first language¶

Focus on people, not disabilities. Don’t use words that imply pity (vezan/vezana za kolica, boluje od, ometen/ometena).

Use generic verbs (Izaberite, not Kliknite) that apply to all input methods. Keep paragraphs short — aim for one verb per sentence. Spell out words like i, plus, otprilike — screen readers can misread &, +, ~.

Grammar and orthography essentials¶

Abbreviations¶

Common Serbian abbreviations use truncation with a period: vidi → v.; na primer → npr.; i tako dalje → itd.; i slično → i sl.

Measurement units (no period, separated from value by space):

Units of information:

Time units (no period):

Don’t abbreviate words like Microsoft on your own.

Acronyms¶

Avoid declining acronyms — use a modifier (usually the main word from translation): RAM → RAM memorija. In rare cases when declension is unavoidable, case endings are hyphenated and written in Latin in Cyrillic context.

Unlocalized acronyms. Many are standardized and remain untranslated. Common acronyms (ANSI, ISO, ISDN) stand alone without spelling out — adding the full form only confuses users.

Adjectives¶

Serbian adjectives have gender and number, unlike English. When context requires multiple genders (often in menus), use the neuter adjective in singular as the most neutral form.

When an adjective refers to several nouns of different genders, formulate to cover all:

Possessive adjectives — usually omit “your”¶

The frequent use of possessives is an English feature. In Serbian, possessive determiners are handled differently — especially “your”, which is usually omitted. If omitting “your” doesn’t affect meaning, omit it.

Svoj vs. vaš — the critical rule¶

When the subject of the sentence matches the object, Serbian grammar requires svoj, not vaš.

Articles — usually omitted¶

English articles are normally omitted in translation but kept when they clarify meaning.

Unlocalized feature names¶

Microsoft product names and non-translated feature names take no articles or quotation marks:

Localized feature names¶

When parts of product and feature names are localized, the first word of the localized name should not be capitalized. When localized product names appear without the unlocalizable part, use quotation marks.

Capitalization¶

English capitalizes all first characters in titles and names; this is an error for Serbian. Names of days, months, languages, and adjectives derived from country names are not capitalized. Words Web and Internet are not capitalized in Serbian.

Compounds — preserve English word order with modifiers¶

Word order should be kept in compounds consisting of (1) adjectival noun in common collocations + headword, or (2) acronym + headword. Compounds with “Web” are written without hyphen: veb stranica, veb lokacija, veb aplikacije.

Conjunctions¶

Starting a sentence with a conjunction can convey informal tone. Sentences can start with i, ali, a in Serbian for relaxed tone, used carefully.

Contractions¶

Use contractions (e.g., Je l’) only in rare cases to emphasize a colloquialism.

Genitive — avoid long chains and “od strane”¶

Don’t transfer English compound noun chains into long Serbian genitive constructions. Three translation patterns:

1. Main word (noun) + supporting word(s) in genitive
2. Supporting word (noun translated as adjective) + main word in nominative
3. Main word + preposition (za, o, etc.) + supporting words in preposition-determined case

Avoid “od strane” constructions — they signal literal translation.

Convention: Don’t attach genitive “s” to trademarked product names — it could be interpreted as modification.

• (−) Microsoft’s products
• (+) Microsoft products
• (+) Products by Microsoft

Localizing colloquialisms, idioms, and metaphors¶

A little humor is OK, but use carefully. Use colloquialisms in specific situations (Getting Started, Product Tours, Setup screens). Avoid offensive or too-expressive colloquialisms. Be mindful of culture.

• Don’t replace source colloquialism with a Serbian one unless it’s a perfect natural fit.
• Translate the intended meaning (not literal) — only if essential to the text.
• If the colloquialism can be omitted without affecting meaning, omit it.

Modifiers for UI items and product names¶

When you need to decline an undeclinable term (UI items, unlocalizable product names), use a modifier.

UI element modifiers (using “Insert” as example):

Product name modifiers — choose based on what the product is. If installable locally via .exe, the correct modifier is usually program/aplikacija. If only usable via web, the modifier is usually usluga. Services usually don’t carry version labels.

Nouns¶

Common vs. proper noun distinction¶

Double-check context — this often happens with product names appearing without tags or unlocalizable parts.

Inflection of non-living vs. living nouns¶

Declination of nouns referring to non-alive things is different from declination of nouns referring to humans or alive beings.

Plural formation¶

English sometimes uses singular where Serbian needs plural — especially in genitive constructions.

Numbers¶

Writing smaller numbers as words is considered good style for descriptive texts, prose, news articles. In technical texts, dates, chapters, bulleted lists, version numbers — use numerals. Official orthography doesn’t strictly address this; follow source pattern. Don’t start a sentence with a numeral.

Prepositions¶

Pay attention to proper preposition use — many translators omit them or change word order under English influence.

Important: The preposition “for” in product names is always translated — Visual Basic for Applications → Visual Basic za aplikacije.

Pronouns¶

Avoid personal pronouns and possessive determiners whenever they don’t affect meaning, especially “you/your” which is frequent in English. When you must use it, use lowercase formal 2nd-person plural (vi/vaš).

The “me/my” exception applies to UI items: “My computer”, “My photos” — these keep the possessive.

Pronouns should replace a word that appears many times in a sentence/paragraph:

Avoid impersonal constructions for fluency and personal style. Don’t spell out pronouns unnecessarily (Preporučujemo da instalirate ovaj program, not Mi preporučujemo…).

Punctuation¶

Bulleted lists¶

A phrase preceding a bulleted list can end with semicolon (A), comma (B), period (C), or no punctuation (D), depending on whether the bullets are complete sentences or continuations.

Example (C) — full sentences in bullets (initial capital, ending period):

Crtica se, za razliku od crte, uvek piše bez belina:
• U polusloženicama, u kojima je istovremeno i spojni i razdvojni znak ...
• U udvojenim prezimenima ...

Example (D) — non-sentence items (no ending punctuation):

Za sledeće engleske termine postoje ova rešenja:
• promotion mix – promotivna mešavina
• marketing mix – marketinška mešavina

Comma¶

Regular Serbian sentence order is main clause + subordinate clause — no comma after the main clause.

If subordinate clause precedes main clause, you must put comma after the subordinate clause.

Action sequence: word order should reflect order of user actions. No comma after those steps.

Colon¶

Double punctuation marks (colons, semicolons, exclamation marks, question marks) are not preceded by a space. When colon introduces enumeration within the same sentence, don’t use capital letters.

Dashes and hyphens¶

• Hyphen (-): divides words by syllables, links compound words. Examples: auto-servis, 25-godišnji, MMF-a, 322-88-63 (phone).
• En dash (–): used as minus sign, emphasizes a phrase, separates clauses. Spaces before and after. Used in number/page ranges (1999–2000, str. 11–23) without spaces unless one of the units consists of more than one word (Beograd–Jagodina vs. Beograd – Novi Sad).
• Em dash (—): Not used in Serbian. Replace with en dash or comma.

Ellipses¶

No space before ellipses. Use the ellipsis character (…) not three dots in a row.

Period¶

Serbian translations never end with a period unless they are complete sentences, regardless of source.

Quotation marks¶

Always use Serbian curly quotation marks (opening: „ ALT+0132; closing: ” ALT+0147), except for inner quotations where single marks are used (both: ’ ALT+0146).

Parentheses¶

No space between parentheses and text inside (same as English).

Sentence fragments¶

Subjunctive — use active voice¶

Use active voice and imperative or indicative mood — easier to understand than passive voice and subjunctive.

Symbols and non-breaking spaces¶

Use non-breaking spaces (Ctrl+Shift+Space or Alt+0160) between words that shouldn’t separate onto different lines. Ampersand (&): always translate as “i” in running text. Don’t keep “&” in target unless part of tag, placeholder, shortcut, or code.

Verbs and tense¶

Pay attention to perfect or imperfect form — English verbs can be translated in either depending on whether action is repeated or single.

Continuous operations (English gerund) translate via deverbative noun or reflexive/imperfect verb:

Pay attention to verb transition dictating noun (object) declination — especially with many English verbs in a row.

Verb tense: prefer present tense; minimize future tense by simplifying sentence flow.

Error messages and status messages¶

Error messages¶

Apply Microsoft voice principles to make messages natural and not robot-like.

Standard phrases in error messages¶

Status bar messages¶

In Serbian, menu and commands status bar messages should follow this format:

Standardization in error messages¶

US product often phrases the same meaning differently — avoid this in Serbian. Use one standard translation.

Error messages containing placeholders¶

%d, %ld, %u, %lu = <number>; %c = <letter>; %s = <string>. Identify what replaces the placeholder for grammatical correctness.

Frequent errors¶

Comma errors:

Context-dependent translation errors:

Recurring patterns¶

Standard title translations¶

Standard remarks/hints¶

Software UI considerations¶

General UI guidelines¶

• Clarity and simplicity are key.
• Be as short as possible. Avoid unnecessary words.
• Account for different devices, sizes, formats — UI must fit all.
• Aim for cross-platform consistency (desktop, mobile, cloud).

Messages¶

US messages sometimes contain abbreviated sentences with imperative verb. Translate as a question starting with “Želite li da…” (preferred), or only when space is limited, with infinitive (try to avoid).

Trademarks¶

Trademarked names and “Microsoft Corporation” should not be localized unless local laws require translation and an approved translated form is available. The word Microsoft is inflected as a noun and a possessive adjective form can be made, but it is never abbreviated to MS. The correct modifier is corporation, not in nominative case.

Copilot predefined prompts¶

Quality of these translations significantly influences Copilot responses. Apply:

• Clear and specific. Make target prompts natural questions/requests. Avoid vague language.
• Conversational. Simple, natural Serbian. Avoid machine-like tone. Use informal address.
• Polite and professional. Kind, respectful. No slang/jargon.
• Use quotation marks to help Copilot identify what to write/modify/replace.
• Entity tokens are placeholders triggering UI pop-ups. Token position should make sense in target syntax. Tokens are typically not localizable — but read Dev comments, sometimes the token text needs translation.
• Consistent. Translate similar English prompts consistently.

Keys, keyboard shortcuts, and shortcut conventions¶

Localized key names¶

In Serbian, unlocalized key names and combinations are written in initial capital letters. Localized key names (razmaknica, strelica nalevo, strelica nadesno) are not capitalized in running text.

Key combination KEY1+KEY2: keys connected with “+” — user presses, holds first key and presses second. Example: kombinacija tastera ALT+ESC.

Key sequence KEY1, KEY2: keys separated with comma and hard space — user presses and releases keys one after another. Example: niz tastera ALT, F.

Keyboard shortcut conventions¶

Standard shortcut keys¶

General Windows shortcut keys¶

File menu¶

Edit menu¶

Font and paragraph format¶

Voice and video considerations¶

A good voice video addresses one intent, is not too long, has high audio quality, has visuals that add information, and uses the right language variant in voiceover.

Successful techniques¶

• Focus on the intent. Show the best way to achieve the most common task.
• Show empathy.
• Use SEO. Include search phrases in title, description, headers.
• Talk to the customer as if next to you.
• Record a scratch audio file first.
• Keep translations as short as possible. Avoid semicolons — split into two sentences. Avoid bullets and partial sentences — they don’t read aloud well.
• Read translations aloud. If it sounds bad to your ear, it’ll sound worse in front of a microphone.
• Gain product experience before translating complex instructions.

Pacing for Serbian: moderate; recommended 140–160 words per minute.

English pronunciation in Serbian voiceover¶

English terms left unlocalized should be pronounced the English way with Serbian phonetic transcription — English “th” sounds (/ð/ and /θ/) pronounced as /t/. Microsoft is pronounced the Serbian way as Majkrosoft.

Acronyms — pronounced like real words when possible (Serbian way)¶

Other abbreviations pronounced letter by letter (no strict rules on English vs. Serbian way — depends on common usage):

URLs¶

“http://” should be left out; rest is read entirely.

Tone and pronunciation¶

Use a tone matching the target audience — informal, playful, inspiring for most products and games; formal, informative, factual for technical content.

Video voice checklist¶

Topic and script: single intent, clarity, everyday language, friendliness, relatable context.

Title: intent + keywords for search.

Intro (10 seconds): relatable context for the problem.

Action and sound: keep something happening visually and audibly, maintain appropriate pace, synchronize visuals with voiceover, alternate between first and second person, repetition of big points OK.

Visuals: smooth pointer motions, judicious callouts, motion graphics, branding-approved visuals.

Ending: recaps unnecessary.

Reference materials — authoritative Serbian references¶

Normative references¶

1. Rečnik srpskohrvatskog književnog i narodnog jezika, vol. I–XVI, Beograd, SANU, 1959–2001.
2. Rečnik srpskohrvatskoga književnog jezika, vol. 1–6, Novi Sad, Matica srpska, 1967–1976.
3. Pešikan, Mitar et al., Pravopis srpskoga jezika, Novi Sad, Matica srpska, 2010 or later edition.
4. Stevanović, Mihailo, Savremeni srpski jezik I, 3. izd., Beograd, Naučna knjiga, 1975 or later.
5. Stevanović, Mihailo, Savremeni srpski jezik II, 2. izd., Beograd, Naučna knjiga, 1974 or later.
6. Klajn, Ivan, Tvorba reči u savremenom srpskom jeziku I (Slaganje i prefiksacija), Beograd – Novi Sad, Zavod za udžbenike i nastavna sredstva – Institut za srpski jezik SANU – Matica srpska, 2002.
7. Stanojčić, Živojin / Popović, Ljubomir, Gramatika srpskoga jezika, Beograd, Zavod za udžbenike, 2002 or later edition.
8. Šipka, Milan, Pravopisni rečnik srpskog jezika sa pravopisno-gramatičkim savetnikom, Prometej, 2010.
9. Piper, Predrag and Klajn, Ivan, Normativna gramatika srpskog jezika, Novi Sad, Matica srpska, 2014.

Informative references¶

1. Klajn, Ivan, Rečnik jezičkih nedoumica, 3. izd., Beograd, Nolit, 1992 or later.
2. Ivić, Pavle et al., Jezički priručnik, Beograd, Radio-televizija Beograd, 1991.
3. Računarski rečnik, Beograd, CET, 1999.
4. Tasić, Vera / Bauer, Ivan, Rečnik kompjuterskih termina, 4. izd., Beograd, Mikro knjiga, 2001.

FAQ¶

What’s the modern register for Serbian translation across professional contexts?¶

Warm, conversational, scannable — but watch out: heavy marketing phrases that work in English often sound aggressive in Serbian and produce the opposite effect. Address users with lowercase formal vi/vaš. Drop “molimo vas” (please) — it sounds unnatural in Serbian. Sentences can start with conjunctions (i, ali, a) for relaxed tone, but use carefully.

How should I handle product names and trademarks in Serbian?¶

Microsoft product names stay unchanged with no genitive inflection or possessive ‘s’ — Microsoft products (not Microsoft’s products, not Microsoft-a). Use modifiers in Serbian word order to avoid declining trademarked names: RAM memorija (not Memorija RAM), Word dokument (not Dokument programa Word), veb stranica (not stranica na vebu), HTML datoteka. The word Microsoft is inflected as a noun and can take possessive adjective form but never abbreviated to MS.

Which anglicisms should I avoid in Serbian translation?¶

locirati → pronaći, butovati/startovati → pokrenuti, ugrupnjavati → grupisati, biti u mogućnosti → moći, zahtevati → potrebno je da, takođe → i, naredno → sledeće, uveriti se → proveriti, pogodno → zgodno, industrija (meaning sector/branch) → branša. Also avoid od strane constructions (Powered by → Obezbeđuje, not Obezbeđeno od strane).

How should I handle possessive pronouns in Serbian translation from English?¶

Omit them whenever the meaning is preserved — English overuses “your”, Serbian doesn’t. Click Discard to discard your changes → Kliknite na “Odbaci” da biste odbacili izmene (not vaše izmene). Critical rule: when the subject of the sentence matches the object, use svoj (not vaš) — Unesite svoje podatke (not Unesite vaše podatke). UI items keep possessives: My computer, My photos.

How does Serbian translation differ between Cyrillic and Latin scripts?¶

The same Serbian language uses two writing systems — Cyrillic (ћирилица) and Latin (latinica). Microsoft ships both variants. The linguistic rules (grammar, syntax, vocabulary choices) are identical. Only the script differs. For Serbian Cyrillic translation, all the rules in this guide apply but with output rendered in Cyrillic characters. Examples in this guide show the Latin form from the source style guide; Cyrillic equivalents apply directly. Quotation marks: use Serbian curly quotes (opening: „ / closing: “) in both scripts.

What authoritative Serbian language references should I use?¶

Pravopis srpskoga jezika (Pešikan et al., Matica srpska 2010), Rečnik srpskohrvatskog književnog i narodnog jezika (SANU 1959–2001), Rečnik srpskohrvatskoga književnog jezika (Matica srpska 1967–1976), Stevanović’s Savremeni srpski jezik I & II, Stanojčić/Popović’s Gramatika srpskoga jezika, Piper and Klajn’s Normativna gramatika srpskog jezika (Matica srpska 2014), and Klajn’s Rečnik jezičkih nedoumica for usage disputes.

How are continuous (-ing) English forms translated into Serbian?¶

English gerunds (Downloading…, Printing…) translate into Serbian as either a deverbative noun (Preuzimanje stranice) or as a reflexive/imperfect verb (Stranica se preuzima / Dokument se štampa). Do not translate as an active finite verb (Preuzima stranicu — wrong). Choose between deverbative noun and reflexive verb based on context — UI status messages often use the deverbative noun form for brevity.

Sources¶

• Microsoft Localization Style Guide for Serbian
• Matica srpska — Pravopis srpskoga jezika
• Microsoft Terminology — Globalization