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

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

TL;DR¶

• Polish translation across all spheres requires a warm, conversational, scannable register — formal officialese (urzędniczy język) feels alien in modern consumer-facing content.
• Avoid the formal calque trap: przez/za pomocą instead of via, użyć/skorzystać z instead of wykorzystać, można instead of istnieje możliwość, jednak/ale instead of jednakże/lecz.
• Gender-neutral writing means rewriting sentences (present tense, passive voice, imperative) rather than using clumsy on(a)/-ł(a) constructions — masculine grammatical form is still default-neutral in generic references (użytkownik, programista).
• Don’t copy English capitalization — Polish capitalizes only first word in titles, names, dialog boxes; days/months/languages are lowercase; Ty/Twój addressing the user are capitalized.
• Spelling reform takes effect 2026-01-01: demonyms (Krakowianin), brand-name products (Forda, Xbox), nie- with adjectives (niemilszy, niedalej), and configurable spacing for prefixes (super-/mega-/eko-).

Register and tone for modern Polish translation¶

Register is the level of formality, warmth, and conversational ease the target text projects. Modern Polish readers across consumer-facing spheres expect a register that feels human rather than bureaucratic — heavily formal officialese (urzędniczy język) signals distance and institutional indifference to most contemporary audiences.

Three principles define the modern Polish register for consumer-facing content:

• Warm and relaxed. Sounds like honest conversation, not a formal notice. Less institutional, more grounded — matching how Poles actually speak.
• Crisp and clear. Written for scanning first, reading second. Sentences short enough to parse on a phone screen. Simplicity is the default.
• Ready to help. Anticipates what the reader needs and offers it at the right moment, rather than burying it under qualifications.

Why this matters: Bureaucratic register damages outcomes across spheres. In marketing copy it kills conversion — readers bounce when text sounds like a tax form. In patient-facing medical materials it reduces comprehension and compliance. In software UI it creates friction at every interaction. In consumer-facing legal documents (terms of service, privacy notices) regulators increasingly demand plain language. Only sworn legal translation and pure technical specifications retain the older formal register.

Flexibility: when to translate literally vs. when to rewrite¶

Flexibility is the translator’s discretion to depart from literal source structure when the literal rendering produces unnatural Polish. The rule: understand the whole intention of the sentence, paragraph, or page, then rewrite as if composing it yourself for a Polish reader. This frequently means restructuring sentences, splitting them, omitting redundant qualifiers, or recasting verbal nouns as verbs.

Why this matters: Source-faithful translation produces translatorese — text that reads as translated. Required in sworn legal translation and certified document translation (birth certificates, court rulings, disputed contracts) where literal accuracy is mandated. Harmful in marketing translation (lost conversion), patient-facing healthcare materials (lost clarity), and software UX (lost engagement). Knowing where the boundary sits is core translator judgment.

Word choice: approved terminology and conversational vocabulary¶

Approved terminology is the project-specific bank of fixed translations for key terms, product names, technical concepts, and recurring phrases. Every serious translation project has one. Consistency within the bank matters more than the individual choice — switching between renderings of the same term across a document signals carelessness.

Generally, terms with short and long forms in English have only one form in Polish (doc, info, app). Polish audiences are reluctant to read long text with obscure words; modern Polish translation uses simple, short words.

Words and phrases to avoid (unnecessary formality)¶

Why this matters: These formal alternatives appear in legal templates and government forms out of institutional habit but feel alien in modern consumer products, patient-facing medical materials, brand-led marketing, and user-friendly software. A privacy policy opening with “Istnieje możliwość wykorzystania danych z wykorzystaniem…” reads as bureaucratic indifference; “Możesz użyć danych, aby…” reads as the product talking to its user.

Word-for-word translation: why direct mapping fails¶

To achieve fluent translation, avoid word-for-word translation. If text is translated literally without overall understanding of the paragraph or page, the tone sounds stiff and unnatural — sometimes ridiculous. Check source text in live pages so you don’t just translate strings without context. Text may be split into different sentences for simplification. Sometimes you can omit descriptors to make text snappier.

Why this matters: Word-to-word translation is the dominant failure mode of inexperienced translators and unedited machine output. In legal contracts it produces clauses that translate every term but obscure who owes what, creating dispute risk. In medical instructions it separates action from actor in ways that confuse patients. In marketing copy it produces headlines that read as foreign. In software UI it produces labels users hesitate over.

Sample voice: focusing on user action¶

Explanatory text and support¶

Promoting a feature¶

How-to guidelines¶

Inclusive language¶

General principles: comply with local language laws; use plain, concrete, familiar words; be mindful of regional/cultural/disputed references; represent diverse perspectives; don’t generalize/stereotype by region, culture, age, or gender; don’t use profane or derogatory terms; don’t use military or politically charged terms.

Term replacements¶

Avoiding gender bias¶

Use gender-neutral alternatives. The most effective way to avoid gender-related issues in Polish: write content in gender-neutral way without masculine or feminine verb endings — often involves switching to present tense or passive voice.

Occupations/functions in Polish: Most occupations have masculine and feminine versions (nauczyciel/nauczycielka, plural nauczyciele/nauczycielki). However, Polish grammatical gender allows masculine forms to refer to both sexes in general contexts. In technical texts, manuals, user guides, software — masculine forms (użytkownik, serwisant, programista) are grammatically masculine but semantically gender-neutral.

Gender-neutral possessive: The reflexive possessive swój can be used by all grammatical persons in both numbers if subject and possessor are the same:

• I open my document → Ja otwieram swój dokument.
• You open your document → Ty otwierasz swój dokument.
• He/she opens his/her document → On/Ona otwiera swój dokument.
• They open their document → Oni otwierają swój dokument.
• A user opens their document → Użytkownik otwiera swój dokument.
• An author opens their document → Autor otwiera swój dokument.

Formal forms of address: The English pronoun “you” is usually rendered as Pan(i) (Sir/Madam) with alternative (masculine and feminine) verb endings in past tense:

• Where did you buy this book? → Gdzie Pan(i) kupił(a) tę książkę?

Alternative endings cannot always be avoided in informal address either:

• Where did you buy this book? → Gdzie kupiłeś(-łaś) tę książkę?

Real people: Use the pronouns the person prefers (on, ona, ono, or another). Gendered pronouns are fine for real people who use them.

Note: Gender-neutral language for new content. Legacy material doesn’t need retroactive update.

Accessibility¶

Focus on people, not disabilities. Don’t use pity-implying words like dotknięty (chorobą) or cierpiący na. Preferred option: don’t mention disability unless relevant.

Spell out words like plus and około — screen readers misread + and ~.

Language-specific standards¶

2026 Polish spelling reform¶

Starting January 1, 2026, new rules for Polish spelling take effect, introduced by the Council for the Polish Language (Rada Języka Polskiego). The changes simplify and standardize spelling, reduce exceptions, reduce common errors.

Key changes:

1. Capitalization of demonyms. Names of inhabitants of cities, districts, villages are capitalized:

This brings consistency with existing capitalized forms (Polak, Francuzka).

2. Capitalization of product names. Names of individual industrial products that are also brand names are capitalized:

3. Hyphenation and spacing. Compound expressions and prefixes follow more consistent rules:

4. Spelling with nie-. The prefix nie- with adjectives and adverbs derived from adjectives is written as one word, regardless of degree of comparison (also comparative, superlative):

5. Pairs of similar-sounding words. Three forms permissible: tuż-tuż, tuż, tuż, and tuż tuż all acceptable.

6. Prefixes that can function as standalone words. Prefixes like super-, mega-, eko- may now be written conjoined or separately:

Impact on Microsoft products: Minimal. Practical adoption is expected to be gradual.

Full reform: https://rjp.pan.pl/zmiany-pisowni?view=article&id=2211 and the full Polish spelling and punctuation rules.

Abbreviations¶

You might need to abbreviate UI words (buttons, options) due to space:

1. An abbreviation of a single word ends with a consonant.
2. If the abbreviation ends with a soft consonant marked by “i” in the full form (e.g., godzina, osiedle), use the hard consonant only: godz., os. — not godź., oś.
3. A period follows abbreviated words except when the final letter of the abbreviation is the same as the final letter of the unabbreviated word.

Acronyms¶

Acronyms ending in vowels in pronunciation shouldn’t be inflected (GUI, SAA).

When acronym is all-caps ending with consonant, choose one method:

• Don’t inflect: “Po otrzymaniu wiadomości SMS.”
• Inflect with appropriate declination pattern, separate inflectional ending (lowercase) from stem with dash: “po otrzymaniu SMS-a.”

Localized acronyms:

Unlocalized acronyms kept in Polish text should be followed by full English and translation:

Adjectives¶

In Polish, adjectives usually precede the noun. However, technical terms (including IT terminology) should be written as noun+adjective:

Possessive adjectives: Avoid frequent use of possessives — common in English but unnatural in Polish.

Capitalization¶

Don’t copy English capitalization in Polish translation. In English, first characters of words in titles, names are often capitalized — this is an error for Polish.

• Days of the week, months, seasons, languages — not capitalized in Polish.
• Titles, names of programs, dialog boxes, check boxes — only the first word capitalized.
• The word web (synonym for World Wide Web) follows source: capitalized if source is.
• Distinctive product capitalization (ALL CAPS, all lowercase) — Polish should follow source for marketing design.

Example: Try Again → Spróbuj ponownie (not Spróbuj Ponownie).

Localizing colloquialism, idioms, metaphors¶

Three options:

1. Don’t replace source colloquialism with a Polish one unless it’s a perfect, natural fit.
2. Translate the intended meaning (not literally) if the colloquialism’s meaning is integral.
3. If the colloquialism can be omitted without affecting meaning, omit it.

Example: “Wow! Lots of things are happening here. Open (PRODUCTNAME) to see all notifications and issues.” → Sporo się tego nazbierało. Otwórz (PRODUCTNAME), aby wyświetlić wszystkie powiadomienia i problemy. (“Wow” can be skipped in Polish.)

Modifiers¶

In localized Polish text you often need to precede English terms with a respective modifier:

One of the most common errors: omitting a modifier before a product/object name, or trying to inflect the English name with a Polish ending. Avoid: “Wszystkie polecenia Worda”, “Inna prezentacja PowerPoint”, “Zamknij Windows”. Always add modifier before menu names, commands, dialog box elements, icons.

Nouns¶

Nonstandard declination patterns (Polish-specific noun forms for English loan terms):

Plural formation: Nouns like edytor, menedżer, projektant, konstruktor, instalator, kreator should be inflected like other impersonal nouns. Obligatory forms: edytory, kreatory, projektanty.

Note: If one of these nouns refers to an application (e.g., a wizard for creating tables), it should start with a capital letter.

Pronouns¶

In Polish, pronoun use is limited. General rules:

• Use pronouns less frequently than in English. If pronoun isn’t key to meaning, skip it. Too many pronouns sound odd.
• First-person singular when user tells program/wizard what to do.
• First-person plural when Microsoft product/service addresses user.
• Second-person forms (addressing user directly) when program/wizard tells user what to do.
• Avoid third-person references (“user”).

Personal and possessive pronouns referring to user (Ty, Twój, Twojego) always start with a capital letter.

Punctuation¶

Bulleted lists:

1. Numbered steps starting with capital letter, ending with period: ```
2. Wybierz kolor pierwszoplanowy.
3. Wybierz grubość linii.

4. Z przybornika wybierz polecenie Aerograf. ```

5. List items preceded by symbol: - Complete sentences → start with capital, end with period. - Continuations of intro sentence → start with small letter, end with comma; last item ends with period. - Items containing commas → all items end with semicolon except last (period). - Not complete sentences, not continuations (e.g., system requirements, sections) → start with capital (proper names) but no period. - Minor items → can start lowercase, no end punctuation.

Comma: Polish comma rules differ from English. In English commas precede or/and; in Polish, this is redundant unless separating parenthetical clauses.

Colon: Introduces lists, procedures. Use lowercase letter after colon.

Example: W programie można zmienić następujące elementy: motyw, czcionkę, rozmiar czcionki, tło i obramowanie okna.

Dashes and hyphens:

• Hyphen (łącznik): no space before/after. Used to join two words, add ending to acronym, join number with word, replace endings of multiple compound adjectives. Examples: Bielsko-Biała, w SMS-ie, 30-procentowy, 32- i 64-bitowe.
• En dash (–): as minus sign, with spaces; in ranges, no spaces. Examples: ZAROBKI – WYDATKI = 2 000 000; ss. 236–238; w latach 2017–2021.
• Em dash (—): to emphasize isolated element or introduce non-essential element. Example: Microsoft Excel — Pomoc.

Ellipsis (…): Three dots, no spaces between. No space between ellipsis and preceding word; space after ellipsis unless followed by closing bracket/quotation mark.

• Indicates intentional omission, pause in speech, unfinished thought.
• For quotation omissions: surrounded with square brackets or parentheses.
• For pause/interrupted speech: no parentheses; can be directly followed by punctuation without space.
• Always three dots, never four.

Period: Marks end of sentence; in Arabic numeral dates; after abbreviations (except when last letter of abbreviation matches last letter of full word). No period after main title, all-uppercase or all-lowercase titles.

Examples: 25.05.2021; prof.

Quotation marks: Polish convention is „lower-upper.” Single quotes nest inside double. Period goes outside quotation marks (unlike English). In US strings with English software references, technical/compilation reasons may require straight ” “.

Example: Wpisz “CHOICE /?”, aby wyświetlić sposób użycia.

Parentheses: No space between parentheses and text inside. Period goes outside parentheses (even when whole sentence is inside).

Examples: - Naciśnij przycisk Save (Zapisz). - W przypadku utraty hasła nie będzie można odzyskać danych. (Pamiętaj, że w hasłach jest rozróżniana wielkość liter).

Sentence fragments¶

Sentence fragments help convey conversational tone — used whenever possible.

Sentence fragments are particularly appropriate for questions — engage user directly.

Symbols and non-breaking spaces¶

Non-breaking spaces (CTRL+SHIFT+SPACE) used in Polish:

• Between numbers and units (60 ml, 100 km/h).
• As thousand separator (20 000).
• After one-letter words (w, z, i) to avoid them at line ends (w witrynie).

Ampersand (&): Always translate “&” as “and” when in running text. Don’t keep “&” in target unless it’s part of a tag, placeholder, shortcut, or code.

Localization considerations¶

Accessibility¶

Some accessible products may not be available in Polish-speaking markets. General accessibility info at https://www.microsoft.com/en-us/accessibility/.

Applications, products, features¶

Product names rarely translated. Names containing “Microsoft” or registered trademarks (Microsoft Classroom, Microsoft Cloud) are not translated. The preposition “for” is usually translated.

Feature names usually localized; occasionally trademarked (IntelliSense). Set correct translation early in localization process.

Version numbers always contain period (Version 4.2).

Version strings with copyright information should be translated using approved Microsoft Terminology translations.

Copilot predefined prompts¶

Best practices for translating Copilot predefined prompts:

• Be clear and specific. Polish prompts are typically questions or requests starting with action verb. Make sure target prompts are natural questions or requests.
• Keep it conversational. Consistent with voice principles. Use simple, natural language. Use informal tone and form of address.
• Be polite and professional. Use kind and respectful language. Don’t use slang or jargon.
• Use quotation marks. Helps Copilot know what to write, modify, replace.
• Pay attention to punctuation, grammar, capitalization.
• Pay attention to entity token placement. An entity token triggers a pop-up menu in UI for user to choose entity (file, contact, meeting). Position of entity token should make sense in target syntax. Entity tokens may be within tags (<entity type='file'>file</entity>) or ( ) / [ ]. The word within is translated, but not the entity type attribute value.
• Place ghost texts at end of sentence. Copilot provides hints/suggestions as “ghost texts” within placeholder tags. Should be placed at end of translated prompts so users don’t move cursor to add their own context.
• Be consistent. Similar English prompts should translate consistently.

Examples:

Trademarks¶

Don’t localize trademarked names unless local laws require. Reference list at https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks.

Software considerations¶

General guidelines: clarity and simplicity are key. Be as short as possible. Avoid unnecessary words. Keep in mind different devices, sizes, formats. Try for cross-platform consistency.

Error messages¶

Apply voice principles for natural, empathetic, non-robotic translations.

Polish error message style:

• Use abbreviated sentence structure for confirmation prompts (saves space). Example: The selection is too big. Continue without Undo? → Zaznaczenie jest za duże. Czy kontynuować bez możliwości cofnięcia?
• Polish error messages always end with a period.
• Exclamation points used as in English, but not every English ! needs to carry to Polish — omit when message is descriptive.
• Personification is acceptable in error messages (exception to general rule). Example: Word cannot open file → Program Word nie może otworzyć pliku.

Standard phrases:

• Avoid “przepraszam” / “przepraszamy” — use “niestety” instead. Example: We’re sorry, the service isn’t available right now. → Niestety, usługa jest w tej chwili niedostępna.
• “while -ing” → “podczas próby”. Example: An error occurred while attempting to create the folder. → Wystąpił błąd podczas próby utworzenia folderu.
• Questions translated as questions even if English uses affirmative with question mark. Use personal form: “Are you sure you want…” → “Czy na pewno chcesz…”, not “Czy chcesz…”
• Error messages with instructions → use imperative mood and personal form. Example: To skip creating your startup disk, click Cancel. → Aby pominąć tworzenie dysku startowego, kliknij przycisk Anuluj.

Error messages with placeholders: %d, %ld, %u, %lu → <number>; %c → <letter>; %s → <string>.

In English, numerals typically precede the noun; placeholder order also preserved in Polish — but check declension. Example: “%u groups” → “Grupy: %u” (if word order kept, Polish reads “5 grupy” which is incorrect for inflection).

Keys¶

References to key names appear in normal text and sentence-style capitalization (not small caps). In Polish, refer to key names preceded by word klawisz (e.g., “naciśnij klawisz CTRL”). English key names not translated, except: Spacebar (spacja), Windows key (klawisz systemu Windows), arrow keys.

Arrow keys¶

Don’t capitalize arrow key names in generic references (e.g., “Za pomocą klawisza strzałki w górę przejdź do następnego okna”).

Reference materials: authoritative Polish dictionaries¶

Use these references for orthography, grammar, terminology when this guide doesn’t specify.

Normative references (must adhere to):

1. Słownik poprawnej polszczyzny — PWN, latest edition. Authority on correct Polish usage.
2. Słownik języka polskiego — PWN, latest edition. General-language dictionary.
3. Nowy słownik ortograficzny języka polskiego — PWN, latest edition. Orthography.

Informative references (supplementary):

1. Słownik wyrazów bliskoznacznych — PWN. Synonyms.
2. Słownik frazeologiczny — PWN. Phraseology.
3. Słownik wyrazów obcych — PWN. Foreign-loan words.
4. Poradnia językowa PWN — https://sjp.pwn.pl/poradnia
5. Rada Języka Polskiego — https://rjp.pan.pl (authoritative on 2026 spelling reform).

FAQ¶

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

Warm, conversational, scannable — closer to everyday Polish than urzędniczy język (formal officialese). Applies to medical patient materials, marketing copy, software UI, consumer-facing legal documents. Sworn legal translation, contracts, technical specifications retain more formal register.

How do I handle gender in Polish translation?¶

Rewrite to avoid gender-revealing past-tense verb endings — use present tense (Nie pamiętasz hasła? not Zapomniałeś hasła?), passive voice (Wprowadzone hasło jest nieprawidłowe), or imperative (Zaloguj się). Generic professional terms (użytkownik, programista, autor) are grammatically masculine but semantically gender-neutral. Use swój as gender-neutral reflexive possessive.

How should I address users in Polish translation?¶

Skip pronouns when possible — second-person verb forms (zmień, kliknij) feel natural in Polish. Use first-person plural when product addresses user (zalecamy). Use first-person singular when user addresses product (Pamiętaj moje hasło). Capitalize Ty, Twój, Twojego when addressing user.

What’s the Polish capitalization rule for titles and product names?¶

Capitalize only the first word in titles, dialog boxes, menus, buttons (Spróbuj ponownie, not Try Again). Days of week, months, languages, nationalities (adjective) are lowercase. Demonyms (city inhabitants) like Krakowianin are uppercase from 2026. Microsoft product names remain unchanged.

Which Polish normative references should I follow?¶

PWN dictionaries: Słownik poprawnej polszczyzny (correct usage), Słownik języka polskiego (general), Nowy słownik ortograficzny języka polskiego (orthography). Online: Poradnia językowa PWN (sjp.pwn.pl/poradnia), Rada Języka Polskiego (rjp.pan.pl) — authoritative on the 2026 spelling reform.

How does Polish punctuation differ from English?¶

Comma rules differ: Polish doesn’t use comma before or/and unless separating parenthetical clauses. Quotation marks are „lower-upper” (period outside). Parentheses period outside. Ellipsis exactly three dots, never four. Non-breaking spaces required after one-letter words (w, z, i) to prevent them at line ends.

What changes in 2026 due to the Polish spelling reform?¶

Demonyms capitalized (krakowianin → Krakowianin). Brand-name products capitalized (Kupił Forda). Compound prefixes joined (półżartem). nie- with adjectives written together (niemilszy, niedalej) regardless of degree of comparison. Prefixes super-/mega-/eko- can be joined or separate.

Sources¶

• Microsoft Localization Style Guide for Polish (PDF)
• Microsoft Globalization Style Guides hub
• Poradnia językowa PWN
• Rada Języka Polskiego
• 2026 Polish spelling reform — official document
• Microsoft Accessibility