This guide adapts rules and examples from Microsoft’s Localization Style Guide for Dutch (originally written for software/UI localization). The underlying linguistic rules apply universally — to legal contracts, medical documents, marketing copy, and any Dutch translation work. Restructured and reformatted as a general Dutch translator reference by ChatsControl.
Dutch Translation Style Guide — Voice, Word Choice & Common Pitfalls (Legal, Medical, Marketing, IT)¶
TL;DR¶
- Modern Dutch translation across all spheres prioritizes a warm, conversational, scannable register — formal Dutch with archaic vocabulary feels distant and bureaucratic in consumer-facing content.
- Address with ‘u’ by default for business, legal and product documentation; ‘je/jij’ is increasingly common in marketing, consumer apps and informal Microsoft products.
- Dutch compounds are written as a single word (tekstobject, cirkeldiagram) — use a hyphen only for vowel clash, acronyms, brand names or readability; spaces between compound parts are an Anglicism.
- Avoid formal/archaic vocabulary (tevens, betreffende, met ingang van, aanbevelenswaardig) — prefer modern equivalents (ook, deze/de, vanaf, aan te raden).
- Reference Groene boekje (Woordenlijst Nederlandse taal), Van Dale, Schrijfwijzer, woordenlijst.org and taalunieversum.org for orthography, grammar and terminology decisions.
- TL;DR
- Register and tone for modern Dutch translation
- Flexibility: when to translate literally vs. when to rewrite
- Word choice: approved terminology and conversational vocabulary
- Word-to-word translation: why direct mapping fails
- Words and phrases to avoid in modern Dutch
- Address forms: ‘u’ versus ‘je/jij’
- Inclusive language and avoiding bias
- Language-specific standards
- Abbreviations
- Acronyms
- Adjectives
- Articles
- Capitalization
- Compounds (the single most important Dutch translation rule)
- Conjunctions
- Gender
- Genitive
- Localizing colloquialisms, idioms, and metaphors
- Nouns: prepositional alternatives to compounds
- Numbers
- Prepositions
- Punctuation
- Sentence fragments
- Split infinitive
- Symbols and special characters
- Verbs and tense
- Error messages and software UI
- Keyboard shortcuts and keys
- Copilot predefined prompts
- Voice and video considerations
- Trademarks
- Version strings
- Reference materials
- FAQ
- Should I use ‘u’ or ‘je’ when translating to Dutch?
- How are compound nouns written in Dutch?
- Which Dutch vocabulary should I avoid in modern translation?
- When should I use a hyphen versus concatenation in Dutch compounds?
- What authoritative Dutch references should I use?
- How do I handle English loan words in Dutch?
- Are em-dashes used in Dutch text?
- Sources
Register and tone for modern Dutch translation¶
Register is the level of formality, warmth, and conversational ease the target text projects. Dutch sits between English and German on the formality spectrum — readers expect direct, efficient text without excessive ceremony, but also without the casual register that works in American English consumer content. The modern Dutch register for consumer-facing content keeps three things in balance:
- Warm and relaxed. Sounds like an honest conversation rather than an official notice. Less institutional, more grounded — closer to how Dutch people actually speak.
- Crisp and clear. Written for scanning first, reading second. Short sentences, simple structure. 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 Dutch — heavy with passive voice, verbal nouns, and Latinate vocabulary inherited from legal templates — damages outcomes across spheres. In marketing copy it kills conversion (Dutch readers actively dislike text that sounds like a tax form). In patient-facing medical materials it reduces comprehension and compliance (the Netherlands has explicit B1-level readability standards for health communication). In software UI it creates friction at every interaction. In consumer-facing legal documents (privacy notices, terms of service) the AFM and other regulators have moved toward plain-Dutch requirements. Only sworn legal translation and pure technical specifications retain the older formal register intact.
Audience targeting: technical vs. consumer vocabulary¶
The same source text requires different vocabulary depending on who reads the translation. Use technical terms for technical audiences; for consumers use common words.
This applies in every sphere. Legal translation for corporate counsel uses Latinisms and procedural shorthand; consumer-facing versions need plain-Dutch framing. Medical translation for clinicians keeps Greek/Latin nomenclature; for patients it switches to common terms (use ‘hartaanval’ for the patient leaflet, ‘myocardinfarct’ for the clinical chart). IT translation uses developer jargon in engineer-facing docs (e.g. ‘API-eindpunt’, ‘webhook’), natural Dutch in end-user help (‘koppeling’, ‘melding’).
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 Dutch. The rule: understand the whole intention of the sentence, paragraph, or page, then rewrite as if composing it yourself for a Dutch reader. This frequently means restructuring sentences, splitting them, omitting redundant qualifiers, or recasting English noun clusters as Dutch compounds or prepositional phrases.
| English example | Dutch example |
|---|---|
| If you enjoyed these games in the past, you’ll like them even better now. | Als je deze games vroeger al leuk vond, vind je ze nu vast nog leuker. |
| This helps alert you to deceptive websites that try trick you with misleading addresses and can help reduce the chances of compromising your personal information. | Zo wordt u gewaarschuwd voor websites die u met misleidende adressen om de tuin proberen te leiden en wordt de kans kleiner dat uw persoonlijke gegevens in verkeerde handen vallen. |
| Developers can go to the application management site to find the apps they are looking for. | Ontwikkelaars kunnen op de site voor het beheren van toepassingen de apps vinden die ze nodig hebben. |
The Dutch versions don’t shadow English syntax — they reshape it. Note how “the application management site” expands into a prepositional construction (“de site voor het beheren van toepassingen”) because the literal compound “applicatiebeheerssite” would be awkward.
Why this matters: Source-faithful translation produces translatorese — text that reads as obviously 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 — the billable skill that distinguishes professional work from raw machine output.
Caveat for UI work: standard system messages and error strings should not be freely rephrased — they may be referenced in support docs and help pipelines that depend on exact wording. Outside that narrow category, flexibility is the norm.
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, explicit (glossary, termbase) or implicit (translator’s accumulated decisions). Consistency within the bank matters more than the individual choice — switching between ‘app’ and ‘toepassing’, or ‘kiezen’ and ‘selecteren’, within one document signals carelessness.
Short, everyday words are preferred over long formal ones wherever both exist and the audience is non-specialist. Shorter words are friendlier, save screen space, and parse faster.
| en-US source term | Dutch word | Dutch word usage |
|---|---|---|
| app | app | Use ‘app’ for “small” applications which might be part of Windows. For “big” applications such as Notepad or Office, use ‘toepassing’ or ‘programma’. |
| pick, choose | kiezen | Use ‘kiezen’ instead of ‘selecteren’ to express a choice between various options. |
| PC | pc | Use ‘pc’ for personal computing devices (use ‘computer’ for situations about PCs and Macs together). |
| you | u | Address the user as ‘u’, directly or indirectly. (For some products, ‘je’ is used — see Address forms below.) |
Why this matters: Terminology consistency is non-negotiable in legal translation (a defined term in a contract must render identically across all 200 pages — variant renderings create ambiguity opposing counsel will exploit), medical translation (drug names, dosage units, anatomical terms must be invariant — a synonym swap can produce a dispensing error), and IT/software translation (UI labels, menu items, error codes must match help documentation word-for-word or users can’t find what they need). Choosing short vs. formal forms is a separate decision from consistency — but once chosen, apply uniformly.
Word-to-word translation: why direct mapping fails¶
Word-to-word translation substitutes each source word with its dictionary equivalent while preserving source word order and syntax. In Dutch translation from English it produces stiff, unnatural text because Dutch and English distribute information differently. Dutch uses compound nouns and verb-final clauses where English uses noun phrases and SVO order. Mapping one onto the other without restructuring produces the “translated-from-English” feel.
The remedy: read for paragraph-level meaning, then compose Dutch sentences that carry the same meaning naturally. Split, simplify, or omit descriptors to make the text snappier.
| English text | Correct Dutch translation | Incorrect Dutch translation |
|---|---|---|
| Express your feelings with emoticons | Uit uw gevoelens met emoticons | Geef uitdrukking aan uw gevoelens met emoticons |
| When you have finished selecting your product, click the Next button. | Klik op de knop Volgende als u het product hebt geselecteerd. | Wanneer u het product geselecteerd hebt, klikt u op de knop Volgende. |
| You may also find it easier to write complex formulas if parts of those formulas contain named, shorter formulas. | Complexe formules zijn ook eenvoudiger samen te stellen als ze bestaan uit kleinere formules die een naam hebben. | U kunt het ook gemakkelijker vinden om complexe formules te schrijven als onderdelen van die formules benoemde, korte formules bevatten. |
Notice in the second example how the correct Dutch restructures the conditional (“if-then” becomes “main clause + als-clause”) because Dutch prefers the main idea up front, not buried behind a temporal subordinate.
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 — a known source of compliance errors. In marketing copy it produces headlines that read as foreign — technically Dutch but emotionally flat. In software UI it produces labels users hesitate over because the phrasing doesn’t match how they’d describe the action.
Words and phrases to avoid in modern Dutch¶
Two categories of vocabulary to avoid: archaic, formal register that survives in legal templates and government documents but feels alien in consumer-facing text; and overly heavy Latinate or compound prepositional phrases.
| en-US source | Dutch old word/phrase | Dutch new word/phrase |
|---|---|---|
| In addition | Tevens | ook |
| as well as | zowel … als … | … en … |
| refer to | betreffende | deze, de (or leave it out) |
| recommend | aanbevelenswaardig, raadzaam | aan te raden |
| from | met ingang van | vanaf |
| give/provide guidance, give/provide information | bovengenoemde / vorenvermeld / etc. | leave these references out if the context is clear enough |
| mine, yours | mijnerzijds / uwerzijds | van mij / van u |
| in conjunction with | ten aanzien van / met betrekking tot / in verband met | avoid these phrases, try to write the sentences differently while keeping the general meaning |
Why this matters: These forms 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 “Tevens delen wij…” signals bureaucratic indifference; “We delen ook…” reads as the product talking to its user. A patient leaflet saying “Ten aanzien van bijwerkingen…” lands differently than “Bij bijwerkingen…” — the second reduces missed reports. These substitutions are among the highest-leverage edits a translator can make.
Address forms: ‘u’ versus ‘je/jij’¶
Historically Dutch Microsoft products have addressed users using the formal second-person pronoun ‘u’. There is a growing trend in the Netherlands toward the informal ‘je’, and some Microsoft products have adopted this informal tone. The form depends on the product type and target audience.
- ‘u’ is the default for legal documents, business correspondence, formal product documentation, medical patient materials in clinical contexts, government communication, banking, insurance, and most professional B2B software.
- ‘je/jij’ fits marketing copy for younger consumers, gaming, social apps, fitness, lifestyle products, and Microsoft consumer products that explicitly target an informal tone (some Xbox content, some education products targeting students).
Pick one and stay consistent within a single product or document. Switching between ‘u’ and ‘je’ in the same UI signals editorial confusion. When in doubt, default to ‘u’ — it doesn’t offend formal-leaning readers, whereas ‘je’ can alienate them.
The Belgian Dutch market (Flanders) tends to be more conservative with ‘u’ than the Netherlands. If a project targets both, lean toward ‘u’ to avoid offending Flemish readers.
Possessive adjectives¶
The frequent use of possessives is a feature of English. In Dutch, possessive adjectives work similarly, but in product translations the use of the second-person possessive — “uw computer” — is generally avoided in favour of an article (“de computer”) where the meaning is clear without ownership marking.
Inclusive language and avoiding bias¶
Microsoft technology reaches every part of the globe, so it is critical that all communications are inclusive and diverse. These principles apply to any modern Dutch translation work, not just software.
General principles:
- Comply with local language laws.
- Use plain language. Use straightforward, concrete, familiar words. Plain language helps people of all learning levels and abilities. Choose a two-syllable word over a three-syllable word; use several clear words instead of one complicated term.
- Be mindful when referring to parts of the world. If you name cities, countries, or regions in examples, make sure they are not politically disputed. In examples that refer to several regions, use equivalent references — don’t mix countries with states or continents.
- Represent diverse perspectives and circumstances in text and images. Depict a variety of people from all walks of life participating fully in activities. Show people in a wide variety of professions, educational settings, locales, and economic settings.
- Don’t generalize or stereotype people by region, culture, age, or gender, not even if the stereotype is positive. For example, when representing job roles, choose names that reflect a variety of gender identities and cultural backgrounds.
- Don’t use profane or derogatory terms.
- Don’t use slang that could be considered cultural appropriation.
- Don’t use terms that may carry unconscious racial bias or terms associated with military actions, politics, or controversial historical events and eras.
| English use this | English not this | Dutch use this | Dutch not this |
|---|---|---|---|
| primary/subordinate | master/slave | leidinggevende / ondergeschikte | meester / slaaf |
| expert | guru | expert | goeroe |
| meeting | pow wow | vergadering | pow wow |
| colleagues; everyone; all | guys; ladies and gentlemen | collega’s; allemaal | dames en heren |
| parent | mother or father | ouder | moeder of vader |
| block list / allow list | black list / white list | blokkeringslijst / acceptatielijst (Geblokkeerd / Geaccepteerd) | zwarte lijst / witte lijst |
Avoid gender bias¶
Use gender-neutral alternatives for common terms. Avoid compounds containing gender-specific terms.
| Dutch use this | Dutch not this |
|---|---|
| gespreksleiding | voorzitter, voorzitster |
| personeel | medewerker, medewerkster |
| salespersoon | verkoper, vertegenwoordiger |
| door de mens gemaakt, kunstmatig | door mankracht gemaakt |
When presenting generalizations, use plural noun forms (personen, studenten, etc.).
Don’t use gendered pronouns (zij, hij, hem, haar) in generic references. Instead:
- Rewrite to use the second or third person (jij or jouw).
- Rewrite the sentence to have a plural noun and pronoun.
- Use articles instead of a pronoun (for example, ‘het document’ instead of ‘zijn document’).
- Refer to a person’s role (lezer, klant, persoon).
- Use ‘persoon’.
| Use this (English) | Not this (English) | Use this (Dutch) | Not this (Dutch) |
|---|---|---|---|
| If the user has the appropriate rights, they can set other users’ passwords. | A user with the appropriate rights can set other users’ passwords. | Als de gebruiker de juiste rechten bezit, kan deze de wachtwoorden van andere gebruikers instellen. | Als de gebruiker de juiste rechten bezit, kan hij de wachtwoorden van andere gebruikers instellen. |
| Developers need access to servers in their development environments, but they don’t need access to the servers in Azure. | A developer needs access to servers in his development environment, but he doesn’t need access to the servers In Azure. | Een ontwikkelaar heeft toegang tot servers in de ontwikkelingsomgeving nodig, maar heeft geen toegang nodig tot de servers in Azure. | Een ontwikkelaar heeft toegang tot servers in zijn ontwikkelingsomgeving nodig, maar hij heeft geen toegang nodig tot de servers in Azure. |
| When the author opens the document … | When the author opens her document … | Als de auteur het document opent… | Als de auteur haar document opent… |
| To call someone, select the person’s name, select Make a phone call, and then choose the number you’d like to dial. | To call someone, select his name, select Make a phone call, and then select his number. | Selecteer de naam van de persoon om deze te bellen, selecteer Een telefonische oproep doen, en vervolgens het nummer dat u wilt kiezen. | Selecteer de naam van deze persoon om hem te bellen, selecteer Een telefonische oproep doen, en vervolgens het nummer dat u wilt kiezen. |
In Dutch, if you can’t write around the problem, it is acceptable to use the demonstrative pronoun ‘deze’ in generic references to a single person. Don’t use constructions like ‘hij/zij’ or ‘hem/haar’.
When writing about a real person, use the pronouns the person prefers, whether ‘hij’, ‘zij’, or another pronoun. It is fine to use gendered pronouns when writing about real people who use those pronouns themselves.
Note: English ‘they/them’ in source content is often used as a gender-neutral 3rd person singular form. Check whether this is the case, and don’t translate as a 3rd person plural (‘zij’) in the translated content. Rewrite to a fitting target.
Accessibility¶
Microsoft devices and services empower everyone, including people with disabilities, to do the activities they value most.
Focus on people, not disabilities. Don’t use words that imply pity, such as ‘getroffen door’ or ‘leidend aan’. The preferred option is not to mention a disability unless it is relevant.
| Use this (English) | Not this (English) | Use this (Dutch) | Not this (Dutch) |
|---|---|---|---|
| person with a disability | handicapped | persoon met een beperking | gehandicapt, gehandicapte |
| person without a disability | normal person; healthy person | persoon zonder beperking | normaal persoon; gezond persoon |
Use generic verbs that apply to all input methods and devices. In procedures and instructions, avoid verbs that don’t make sense with alternative input methods used for accessibility.
| Use this | Not this | Dutch use this | Dutch not this |
|---|---|---|---|
| Select | Click | Selecteren, kiezen | Klikken, tikken |
Keep paragraphs short and sentence structure simple — aim for one verb per sentence. Read text aloud and imagine it spoken by a screen reader. Spell out words like ‘en’, ‘and’, ‘plus’ — screen readers can misread text that uses special characters like the ampersand (&) and plus sign (+).
Language-specific standards¶
Abbreviations¶
You may need to abbreviate some words in the UI (mainly buttons or options) due to lack of space, but the general Dutch rule is not to use abbreviations. Expressions such as “met betrekking tot” and “ten aanzien van” must be written in full rather than abbreviated to “m.b.t.” or “t.a.v.” (though as noted above, those phrases themselves should usually be rewritten).
Acronyms¶
Acronyms are words made up of the initial letters of major parts of a compound term — WYSIWYG, DNS, HTML.
Since the Spellingactualisering 2005, Dutch distinguishes two types:
- Letterwoord — a word formed by the first letters of a name or phrase, read as a word (havo, SLIP, RAS).
- Initiaalwoord — a word formed by the first letters of a name or phrase, read as a series of letters (pc, dvd).
Both are written without periods. Capitalization follows the abbreviated words. If an organization uses a notation that deviates from this rule, follow their notation. In software, this usually applies to names of products and standards.
Examples:
- Initiaalwoorden: pc (personal computer), btw (belasting toegevoegde waarde), NS (Nederlandse Spoorwegen).
- Letterwoorden: pin (persoonlijk identificatienummer), BuZa (Buitenlandse Zaken). Exception: RAM.
For compounds and derivatives: for letterwoorden without capitals, the hyphen or apostrophe disappears in the compound. For letterwoorden with capitals and for initiaalwoorden, the capital and apostrophe are retained.
Examples: aidsvirus, pincode, latrelatie, havoleerling, vipbehandeling, btw-tarief, pc-gebruiker, AOW’er, tv-kijker, API-sleutel, RAM-geheugen, RAS-verbinding.
First appearance: When an acronym makes its first appearance in body text, spell it out — put the full term in brackets immediately after the acronym. After this first appearance, use the acronym alone. In software messages, the acronym must always be followed by the full form in brackets, because in software there is no such thing as a “first appearance.”
Example: “CRC (Cyclic Redundancy Check) is een procedure die wordt gebruikt bij het controleren op fouten tijdens gegevensoverdracht. CRC-foutcontrole maakt gebruik van complexe berekeningen…”
If the acronym refers to a term that is not normally translated into Dutch, give only the full English term. If the term has a generally accepted Dutch translation, use the acronym followed by the Dutch term. Examples: DTP (Desktoppublishing), SLIP (Serial Line Internet Protocol), OLE (objecten koppelen en insluiten).
Compounds with acronyms follow the rules for initiaalwoorden and letterwoorden above: RAM-geheugen, LAN-verbinding, GUI-termen.
No explanation needed for: HDMI, USB, GUI, pc, ASCII, ANSI, API, VGA, PCI, RAM, UNIX, TCP/IP.
Localized acronyms: Very few acronyms are localized in Dutch. Most are names of organizations or countries. If the name of a multi-word country or organization is localized, the acronym is too: UK → VK, UN → VN, WWF → WNF.
Adjectives¶
In Dutch, adjectives need careful handling. Where possible, English compound adjectives should not be translated literally but described instead.
| en-US source | Dutch target |
|---|---|
| copy-protected disk | tegen kopiëren beveiligde schijf |
| cloud-based | op de cloud gebaseerde |
| user-initiated | geïnitieerd door de gebruiker |
| web-based | op het web gebaseerde |
This rule applies only to compound adjectives. Limit the number of adjectives in a sentence to avoid a “breathless” style.
Niet-: Compounds with adjectives that start with “non-” in English get a hyphen after “niet” in Dutch.
| en-US source | Dutch target |
|---|---|
| non-contiguous | niet-aaneengesloten |
| non-Windows application | niet-Windows-toepassing |
| non-Microsoft | niet-Microsoft |
Articles¶
Product names do not take articles. Write “Toolbar nu installeren” (not “De Toolbar nu installeren”). Exception: when an adjective qualifies the product name, an article is required (“De verbeterde Microsoft Teams”).
Unlocalized feature names are also used without articles, the same way they are in English. Example: “SharePoint is een uitgebreide oplossing voor het beheer van e-mail, taken en contactpersonen.”
Localized feature names: capitalize the first letter and don’t use an article. Example: “Ga naar Bureau-accessoires en start Rekenmachine.”
English loan words: When choosing an article for an English loan word, consider:
- Motivation — does the English word have formal features that allow integration into the Dutch noun class system?
- Analogy — is there an equivalent Dutch term whose article fits?
- Frequency — which article is used most often in technical documentation?
When in doubt, consult Microsoft Terminology to confirm the use of a new loan word and its proper article.
Article with “internet”: The article “het” before “internet” is optional in Dutch. Microsoft products use “het internet.”
| en-US source | Dutch target |
|---|---|
| Connect to the Internet | Verbinding maken met het internet |
Capitalization¶
Product names follow source capitalization. In sentences and headings, use uppercase only at the beginning of the sentence:
- Correct: “Download de mobiele Teams-app”
- Incorrect: “Download de Mobiele Teams-App”
Always use uppercase in the following cases:
- At the beginning of each module descriptor title: “Start | Geavanceerd zoeken | Mijn voorkeuren | Site aanmelden | Help”.
- For each descriptor of a functional graphic element: “Klik op de knop Zoeken,” “Klik op het tabblad Opties”.
- When referring to UI elements: “Kies een provincie uit de lijst en klik op Zoeken.”
- When referring to keys (T, Shift, Alt). Key combinations should be rewritten using the plus sign (+): “Ctrl+C”.
- The first word after a colon is not capitalized in Dutch, unless more than one sentence follows the colon. If multiple sentences follow, capitalize the first word.
Use accents on uppercase letters to avoid pronunciation problems: “TWEE KOPIEËN, GEÏNTEGREERD, GEÏNITIALISEERD, GEÜPLOAD, BELGIË.” Use lowercase for months and days: januari, februari, maandag, dinsdag.
Compounds (the single most important Dutch translation rule)¶
The parts of a compound noun in English are often separated by a space or hyphen. In Dutch, compounds are written as a single word.
| en-US source | Dutch target |
|---|---|
| text object | tekstobject |
| pie chart | cirkeldiagram |
| laptop computer | laptopcomputer |
| Live event | Livegebeurtenis |
Compounds should be understandable and clear to the user. Overly long or complex compounds should be avoided — unintuitive compounds are an intelligibility and usability issue.
Why this matters: Mishandled compounds are the #1 marker of English-source translation. In legal text: “data processing agreement” → “gegevensverwerkingsovereenkomst” (one word), not “gegevens verwerkings overeenkomst”. In medical text: “patient information leaflet” → “patiëntenbijsluiter”, not “patiënten bijsluiter”. In marketing: “customer success story” → “klantsuccesverhaal” or with hyphens for readability. Writing compound parts as separate words is a hard error.
Compounds with proper names, brand or product names
According to the Groene boekje, compounds with brand names are concatenated without hyphens, just like compounds with proper names: “Philipslamp”, “Essotankstation”. Capitalization is retained.
However, to improve readability, Microsoft texts do use the hyphen with brand/product names. Onze Taal mentions this as a clearer alternative. Example: the Groene boekje recommends “Albert Heijnfiliaal” but allows “Albert Heijn-filiaal” as a clearer alternative.
Compounds with a word group ending in a symbol, letter or digit get a hyphen (e.g. version indicators).
Examples:
- Een Microsoft Windows-hulpprogramma, een Esso-tankstation
- Een Microsoft-product, een Philips-lamp
- Middellandse Zee-gebied, i9-processor
- Een Microsoft PowerPoint Viewer-bestand, Microsoft 365-app
- Koningin Beatrix-estafette
Compounds with Dutch and English components
Compound nouns with Dutch and English components are tricky because the English components are often not in the Groene boekje (unless they are well-accepted English-language terms). Guidelines:
- Always try to find a Dutch translation first.
- Only leave a term in English if there are no other options (product name that cannot be localized, or a decision to use the English term).
A compound of English words accepted in Dutch is written as a single word. This applies to three-part compounds with two or three English components. For vowel clash, or if one component is an acronym, single letter, digit or symbol, use a hyphen.
Examples: online accountmanager, businessclass, download, sciencefiction, voicemail, demi-john, e-mail, pay-tv, publicrelationsschool, humanresourcesafdeling, lowbudgetfilm, onlinebestand, offlinewerkmap, online-Help.
The following are separated by spaces — they are considered word groups, not compounds: “low budget” (was lowbudget), “slow motion” (was slowmotion).
Note: compounds using online/offline + verb are spelled as two words; compounds with a noun are spelled as one word.
| Verb form (two words) | Noun form (one word) |
|---|---|
| offline gebruiken | offlinebestand |
| online bankieren | online-Help |
Hyphens in compounds
Compounds are spelled with a hyphen in the following situations:
- In compounds of English words accepted in Dutch, where a vowel clash occurs or one component is an acronym, single letter, digit or symbol.
- To improve readability — an optional hyphen can be used between components (bodyart and body-art; knowhowovereenkomst and knowhow-overeenkomst). This applies to many compounds with only Dutch parts too: valk-uil.
- If the final letter of one component and the first letter of the next can spell a diphthong (see Vowel clash below).
- Certain combinations treated as compounds: combinations with equally important parts (singer-songwriter); compounds that also have a hyphen in English (up-to-date); combinations whose left part is “no” or “non” (non-profit, no-nonsensepolitiek); combinations whose right part is an English prepositional adverb (lay-out, back-upbestand, stand-by, all-invakantie).
| Correct | Incorrect |
|---|---|
| contrastrijker | contrast-rijker |
| zwart-witdia | zwart/wit-dia |
| identiteitschip | identiteits-chip |
Vowel clash
When the following vowel combinations appear between two words in a compound, a hyphen must be used: a-a, a-e, a-i, a-u, e-e, e-i, e-u, i-e, o-e, o-i, o-o, o-u, u-i, u-u.
When the following vowel combinations occur, a hyphen is not necessary: ao, ea, eo, ia, io, iu, oa, ua, ue, uo, aj, ej, oj, uj, iji (ij + i), ay, ya, ey, ye, iy, yi, oy, yo, uy, yu.
The combinations i + j, e + ij, e + ui, i + i result in vowel clash in a compound (gummi-jas) but not in a single-part word or derivative (beijveren).
Examples:
| Compound (hyphen for vowel clash) | Compound (no hyphen) | Single word |
|---|---|---|
| gala-avond | cameraopstelling | poëzie |
| gummi-jas | koffieautomaat | ruïne |
| bureau-inhoud | cadeauabonnement | onderzeeër |
| college-uitstap | maximumprijs | beijveren |
| vanille-ijs | minimumprijs | geuit |
Linker/rechter, maximum/minimum
The use of “linker” and “rechter” before a noun often causes problems. Microsoft style concatenates “linker” and “rechter” to the noun for consistency.
“Maximum” and “minimum” are nouns and should always be concatenated to the following words within a compound when they mean “maximal” or “minimal”. They cannot be used as adjectives.
Examples: rechtermarge, rechtermuisknop, linkerbenedenhoek, maximumprijs, minimumprijs.
But: “Het maximum aantal deelnemers” — because of the noun after “maximum aantal”.
Standaard
If ‘standaard’ is used adjectivally and is tightly linked to the following noun, concatenate the two: standaardbrief, standaardmap, standaardgeheugenconfiguratie.
Audio/video
Unlike in English, ‘audio’ and ‘video’ cannot be used as standalone nouns — only as prefixes to other nouns.
| Incorrect | Correct |
|---|---|
| audio instellen | audio-instellingen |
| instellingen voor video | video-instellingen |
Same rule applies to: audioweergave, videoweergave. You may also use beeldweergave, geluidsweergave instead.
Help
Compounds starting with the word ‘Help’ (referring to online documentation) use a hyphen to mark that specific meaning: Help-tekst, Help-onderwerp, Help-venster, Help-index.
Acronyms and numbers in compounds
If a compound noun contains an acronym or a number, both parts are separated by a hyphen: HDMI-poort, 64-bits.
This does not apply to compounds with word groups. If the first part of the word group is a cardinal number, concatenate it in the three-part compound. If the cardinal number is written with digits, use a space.
| Concatenated (number spelled out) | Spaced (number as digits) |
|---|---|
| vijfsterrenhotel | 64 bitsprocessor |
| vijftigeurobiljet | 50 eurobiljet |
| eenaprilgrap | 1 aprilgrap |
In compounds with numbers + shortened units + noun, concatenate the number and unit and add a hyphen between unit and noun: 5GHz-processor, 30km-zone, 35mm-dia, 230V-aansluiting.
Plural formation
Consult the Woordenlijst Nederlandse taal for plural formations. If two plural forms are possible for a word (e.g. “typen” and “types”), use the plural ending in “en”. Note: use “datums” for the plural of “datum”.
Conjunctions¶
For English Microsoft voice, conjunctions help convey a conversational tone — starting a sentence with a conjunction can be informal. The Dutch register can convey conversational tone similarly, by using conjunctions or by leaving them out.
| en-US source text | Dutch old use | Dutch new use |
|---|---|---|
| As |
Omdat |
Maar door deze nieuwe functies wordt oudere inhoud vaak niet meer juist weergegeven. |
| (Als er kans op oververhitting bestaat, moet u direct contact opnemen met de systeembeheerder.) | (Als er kans op oververhitting bestaat, moet u direct contact opnemen met de systeembeheerder.) | Bel direct de systeembeheerder als de pc te warm wordt. |
| (Het is ons streven om alles duidelijk uit te leggen.) | Het is ons streven om alles duidelijk uit te leggen. | We proberen alles zo duidelijk mogelijk uit te leggen. |
Constructions with “om”
Sentences can only start with “om” if “om” indicates a purpose and starts a non-finite clause:
- (-) “Om steeds die om-ellende te moeten beredeneren, lijkt me geen pretje.”
- (+) “Om een koppeling te maken met een diagram kunt u verschillende procedures volgen.”
Nothing is wrong with “om”, but Microsoft prefers constructions without “om”:
| English | Dutch |
|---|---|
| If you want to create a link to a diagram, you can follow several different procedures. | (+) U kunt verschillende procedures volgen om een koppeling te maken met een grafiek. (+) Als u een koppeling met een grafiek wilt maken, kunt u verschillende procedures volgen. |
In software messages, “om” is allowed, but constructions without “om” are still preferred. Avoid “om” at the start of a sentence.
| English | Dutch |
|---|---|
| The current application will be terminated. Press any key to terminate the application. | (-) De actieve toepassing moet worden afgesloten. Om de toepassing af te sluiten druk op een willekeurige toets. (-) De actieve toepassing moet worden afgesloten. Om de toepassing af te sluiten, drukt u op een willekeurige toets. (+) De actieve toepassing moet worden afgesloten. Druk op een willekeurige toets om de toepassing af te sluiten. (+) De actieve toepassing moet worden afgesloten. Sluit de toepassing door op een willekeurige toets te drukken. |
Gender¶
Although gender plays a smaller role in Dutch than in many other languages, observe the rules governing relative and possessive pronouns referring to feminine, masculine, and neutral nouns. See Schrijfwijzer section 7.3.4.
Genitive¶
Attaching a genitive “s” to (trademarked) product names is not feasible — it could be interpreted as a modification of the name.
Localizing colloquialisms, idioms, and metaphors¶
For idioms and metaphors in source text, choose from the following:
- Don’t try to replace the source colloquialism with a Dutch colloquialism that “fits the same meaning” unless it is a perfect and natural fit. Local colloquialisms that work in one country may not work in another.
- Translate the intended meaning of the colloquialism (rather than translating it literally), but only if the meaning is an integral part of the text that can’t be omitted.
- Omit the colloquialism if it can be omitted without affecting the meaning.
Nouns: prepositional alternatives to compounds¶
Dutch offers the possibility to clarify the relationship between the parts of a compound by using prepositions. Sometimes this is clearer than a compound:
| en-US source | Dutch target |
|---|---|
| driver information database | database met stuurprogrammagegevens |
In many cases, however, compounds are preferred over prepositions — excessive use of prepositions can make sentences unnecessarily long and difficult to read.
| English | Dutch (prepositional) | Dutch (compound) |
|---|---|---|
| The file name may be misspelled, or the file name extension was omitted. Enter a different file name. | De naam van het bestand is verkeerd gespeld of de extensie van het bestand ontbreekt. Geef een andere naam voor het bestand op. | De bestandsnaam is verkeerd gespeld of de bestandsextensie ontbreekt. Geef een andere bestandsnaam op. |
| Find a solution provider and download their cache/proxy plug-in. | Zoek een provider van oplossingen en download de invoegtoepassing voor cache/proxy. | Zoek een oplossingsprovider en download de cache-/proxy-invoegtoepassing. |
Numbers¶
Cardinals:
- Write cardinal numbers as digits when they refer to numbered pages, chapters, figures, etc. Example: chapter 9, page 3, figure 1.
- Use digits for numbers displayed as digits on screen. Example: document 2, line 8, column 30.
- Use digits for units of measurement and time, percentages, street numbers, etc., except in sentences where the unit is stated in full. Example: 3,5 inch; 360 kB; van 16:00 tot 18:30 uur; 12%. BUT: “Van Amsterdam naar Parijs is vierhonderdvijftig kilometer.”
For all other cases, refer to the Schrijfwijzer.
Prepositions¶
Many translators, influenced by English, omit prepositions or change the word order. For interface terminology, prepositions are standardized for a number of phrases so that everyone uses the same prepositions:
- Kies de opdracht Plakken in het menu Bewerken
- Klik op de knop Plakken op de werkbalk
- Klik op de knop Ovaal in de werkset
- Plaats de tekst op het Klembord
- Verwijder de vermelding uit de lijst
- Plaats de tekst in de lijst
For Microsoft voice, use of prepositions can also help convey a casual or conversational tone. Starting or ending a sentence with a preposition is acceptable.
Punctuation¶
Comma: Use a comma where the sentence would otherwise be too long or where omission would cause confusion. Do not use the comma to separate two sentences. See the Schrijfwijzer for full rules.
Colon and bulleted lists: Use colons to introduce lists and at the end of a sentence introducing a procedure.
Example:
In dit hoofdstuk wordt beschreven hoe u:
- Voetnoten in een document kunt plaatsen.
- Opmerkingen in een document kunt opnemen.
Het hele document selecteren:
- Druk op Ctrl+Home.
- Druk op Ctrl+Shift+End.
If a single sentence follows the colon, do not capitalize the first word: “Opmerking: met behulp van de liniaal kunt u de marges instellen…”
If multiple sentences follow the colon, do capitalize the first word: “Scenario: U bent de accountmanager van The Garden Company en u wilt een brief bekijken en afdrukken. De brief dient als antwoord…”
Dashes and hyphens
Three different dash characters are used in Dutch:
- the normal hyphen
- the non-breaking hyphen
- the N-dash (ANSI code 0150)
Normal hyphen connects components of a compound term: bestand met het kenmerk Alleen-lezen; PowerPoint-presentatie; client-serververificatie.
The hyphen is also used as an ellipsis marker for a component that has been omitted (but not for ellipsis of a whole word):
- hoofd- en kleine letters
- vaste en verwisselbare schijven
- hard- en software
- computerverkopers en -gebruikers
In software, hyphenation is only allowed where space is limited or layout requires it. Generally avoid hyphenation. The hyphen is also used as the minus sign.
Non-breaking hyphen: Use where a word or word combination cannot be broken at the hyphen location (pages 12-14, 30-40 °C, etc.). Insert with Ctrl+Shift+Hyphen.
En dash and em dash: Do not use the en dash or em dash. Any en or em dashes in English text must be replaced by commas or brackets in Dutch.
Ellipses (suspension points)
Avoid using dots to mark ellipses, except in captions with multiple parts and in truncations.
Example:
- De cellen die u op deze manier hebt geselecteerd, …
- … kunnen eindeloos worden gekopieerd
The English “ing” form often causes truncations. English status messages using the present participle (“Uninstalling software…”) result in long Dutch text that may be cut off. Prefer translations that are not much longer than English.
| English | Incorrect Dutch | Correct Dutch |
|---|---|---|
| Uninstalling software… | Bezig met het ongedaan maken van de installatie van de software | Software verwijderen… |
| Searching for updates | Bezig met het zoeken naar updates / Er wordt gezocht naar updates. | Updates zoeken… |
| Deleting temporary files | Bezig met het verwijderen van de tijdelijke bestanden | Tijdelijke bestanden verwijderen… |
Please wait (while) is often translated as “Een ogenblik geduld terwijl…” The user may not see the end of the text. Split the Dutch translation into two parts, with the most important information first.
| English | Incorrect Dutch | Correct Dutch |
|---|---|---|
| Please wait while Windows copies the files to disk. | Een ogenblik geduld terwijl Windows de bestanden naar schijf kopieert. | De bestanden worden naar schijf gekopieerd. Een ogenblik geduld… |
Period
A period between an abbreviation at the end of a sentence is also the sentence-ending period — don’t add another.
In American numbered lists, the digit is not followed by a period. In Dutch, put a period after the digit:
| English | Dutch |
|---|---|
| 1 abc | 1. abc |
| 2 def | 2. def |
| 3 ghi… | 3. ghi |
Acronyms and units of measurement are not spelled with periods: kB, mm, ASCII, sec.
The period is used as a separator:
- Thousands (but not in years, postal codes, phone numbers): 1.000.000
- Version numbers: PowerPoint 11.0
- File names: Autoexec.bat
Quotation marks
In US source strings, software references may be surrounded by English quotation marks. Use single quotation marks to mark names of chapters, sections and appendixes of manuals. If single quotation marks affect functionality, use double quotation marks.
Example: See chapter 10, ‘Search and Replace’.
In English, file names and variables are often placed between quotation marks. In Dutch, omit them.
| en-US source | Dutch target |
|---|---|
| Do you want to save the changes in “Sales.xls”? | Wilt u de wijzigingen in Verkoop.xls opslaan? |
Parentheses
In Dutch, there is no space between the parentheses and the text inside. Use parentheses to add a comment or clarification:
- Er wordt een sterretje (*) naast de documentnaam geplaatst. Hiermee wordt aangegeven dat deze documentnaam is geselecteerd.
- Vul de gewenste gegevens (getallen) op de stippellijn in.
Also use parentheses for the full form of an acronym: XML (Extended Markup Language).
Sentence fragments¶
For English Microsoft voice, sentence fragments help convey a conversational tone — they are short and to the point.
| en-US long form | en-US fragment |
|---|---|
| Use the following steps. | Here’s how |
Dutch can convey this to some extent through sentence fragments, but avoid using too-trendy phrases just for their own sake.
| en-US source | Dutch long form | Dutch fragment |
|---|---|---|
| Use the following steps. | Gaat u als volgt te werk: | Doe het volgende: |
| (Behind every sentence belongs a period.) | Achter elke zin hoort een punt te staan. | Achter elke zin hoort een punt. |
| (The display of this film is very good.) | De weergave van deze film is erg goed. | Deze film ziet er goed uit. |
| (This document won’t be made available for public consultation.) | Dit document wordt niet voor publieke kennisneming beschikbaar gesteld. | Dit document wordt niet openbaar gemaakt. |
Split infinitive¶
Avoid splitting the infinitives of compound verbs or verbs that include a preposition. This applies regardless of whether the infinitives can be split according to the grammar rules.
- (-) Klik op Opslaan als u dit bestand op wilt slaan
- (+) Klik op Opslaan als u dit bestand wilt opslaan
Symbols and special characters¶
| Character | English | Dutch |
|---|---|---|
| ´ | Accent acute | Accent aigu (´) |
| ^ | Accent circumflex | Accent circonflexe (^) |
| Accent grave | Accent grave () |
||
| & | Ampersand | &-teken |
| <> | Angle brackets | Punthaken (<>) |
| ‘ | Apostrophe | Apostrof (‘) |
| * | Asterisk | Sterretje (*) |
| @ | At sign | Apenstaartje (@); @-teken |
| \ | Backslash | Backslash () |
| { } | Braces | Accolades ({ }) |
| [ ] | Brackets | Vierkante haken ([ ]) |
| ^ | Caret | Caret-teken (^) |
| « » | Chevrons | Dubbele punthaken (« ») |
| © | Copyright symbol | Copyrightsymbool (©) |
| - | Dash | Koppelstreepje (-) |
| ° | Degree symbol | Gradenteken (°) |
| $ | Dollar sign | Dollarteken ($) |
| … | Ellipsis | Weglatingsteken (…) |
| — | Em dash | Em-streepje (—) |
| – | En dash | En-streepje (–) |
| = | Equal sign | Gelijkteken (=) |
| ! | Exclamation point | Uitroepteken (!) |
| > | Greater-than sign | Groter-dan-teken (>) |
| - | Hyphen | Afbreekstreepje (-) |
| “ | Inch mark | Dubbel aanhalingsteken (“) |
| < | Less-than sign | Kleiner-dan-teken (<) |
| - | Minus sign | Minteken (-) |
| # | Number sign | Hekje (#) |
| ¶ | Paragraph mark | Alineateken (¶) |
| ( ) | Parenthesis | Ronde haken ( ) |
| % | Percent sign | Procentteken (%) |
| Pipe | ||
| + | Plus sign | Plusteken (+) |
| ± | Plus-or-minus sign | Plusminusteken (±) |
| ? | Question mark | Vraagteken (?) |
| ® | Registered trademark symbol | Registratieteken (®) |
| § | Section symbol | Paragraafteken (§) |
| / | Slash | Slash (/) |
| ~ | Tilde | Tilde (~) |
| _ | Underscore | Onderstrepingsteken (_) |
Non-breaking spaces ( ) should only be used if they are also present in the US source. Otherwise, a blank space is recommended — non-breaking spaces can cause functionality issues.
Ampersand (&): Always translate “&” as “en” when it refers to running text. Do not keep “&” in the target unless it is part of a tag, placeholder, shortcut or other code.
Verbs and tense¶
For English Microsoft voice, verb tense helps convey clarity. Use simple tenses. The easiest tense to understand is the simple present. Avoid future tense unless describing something that will really happen in the future and simple present is inapplicable. Use simple past tense for events that have already happened.
| en-US source text | Dutch incorrect | Dutch correct |
|---|---|---|
| After you are finished installing the tool, the icon will appear on your desktop. | Nadat u de installatie van het hulpprogramma hebt beëindigd, zal het pictogram worden weergegeven op het bureaublad. | Nadat u het hulpprogramma hebt geïnstalleerd, wordt het pictogram op het bureaublad weergegeven. |
| (Conditional past — hypothetical version installed) | Als u een verouderde versie van dit programma had gebruikt, zou het mogelijk zijn dat de nieuwe functies niet werken. | Als u een verouderde versie van het hulpprogramma gebruikt, werken nieuwe functies misschien niet. |
| (This will still work in two centuries.) | Over twee eeuwen, zal dit nog steeds werken. | Dit werkt over twee eeuwen nog steeds. |
Order of finite verb and past participle
In written texts, the finite verb should be placed before the past participle:
- (-) Nadat u de software geïnstalleerd hebt, dient u deze te configureren.
- (+) Nadat u de software hebt geïnstalleerd, dient u deze te configureren.
This applies only if the past participle is treated as a verb (indicating an action), not as an adjective (indicating a state). For adjectival uses, the order above is incorrect:
- (-) De gebruiker kwam tot de conclusie dat de Help-index was uitgebreid.
- (+) De gebruiker kwam tot de conclusie dat de Help-index uitgebreid was.
Error messages and software UI¶
Error messages are sent by the system or program to inform the user of an error that must be corrected. The messages can prompt the user to take action or inform of an error that requires rebooting. Apply Microsoft voice principles to make error message translation more natural, empathetic, and not robot-like.
General style for error messages¶
The style should be neutral and direct, clearly communicating the intended message. Avoid cryptic language and newspaper-headline style. Verbs should be in the present tense. Sentences must be correct, grammatical Dutch.
Translate everything. All information in an error message must be translated. For technical error messages (Windows errors), research may be required. Leave no terms in English unless the glossary prescribes it.
Style and space. Dutch text translated from English is on average 20–30% longer. Find a balance between available space and a good, direct translation. Don’t preemptively remove articles and prepositions to save space — only omit them if they cause actual layout problems.
| English | Incorrect | Correct |
|---|---|---|
| Problem converting equation. Continue with document conversion? | Er is een probleem opgetreden bij converteren van vergelijking. Wilt u toch doorgaan met conversie van document? | Er is een probleem opgetreden bij het converteren van een vergelijking. Wilt u toch doorgaan met de conversie van het document? |
Use articles and prepositions consistently:
| English | Variations to avoid | Correct |
|---|---|---|
| An error occurred while trying to update the Stored Settings file. | Er is een fout opgetreden bij bijwerken van het bestand met opgeslagen instellingen. / Er is een fout opgetreden bij het bijwerken van bestand met opgeslagen instellingen. | Er is een fout opgetreden bij het bijwerken van het bestand met opgeslagen instellingen. |
Don’t personify program names. “Microsoft Excel cannot display the information” → “De gegevens kunnen niet worden weergegeven in Microsoft Excel.” Personification is acceptable only when space is too constrained for the alternative.
Variables. Always check that all variables in the US message are also in the translation. Nouns of different gender may substitute for a variable, which may affect articles, adjectives, word order.
| Source | Recommended Dutch |
|---|---|
| Can’t read the selected “%s.” | Geselecteerde %s kan niet worden gelezen. (Works grammatically whether %s is “bestand” or “map”.) |
Don’t place variables at the beginning of a sentence — replacement text at runtime may not start with a capital.
Quotation marks in error messages: Remove the English quotation marks around variables. Use single quotation marks only if absolutely needed.
- “Do you want to save the changes in ‘%s’?” → “Wilt u de wijzigingen in %s opslaan?”
Spaces: US messages often have two spaces after a period — change to one space.
Compounds in error messages: English error messages often contain compounds of three or more nouns that are hard to translate. If translated literally, the result is awkward and sometimes wrong. Always give a description:
| English | Incorrect | Correct |
|---|---|---|
| Error opening address book provider root container. | Fout bij openen van adresboekprovider hoofdcontainer. | Fout bij het openen van de hoofdcontainer van de adresboekprovider. |
Standard error message phrases¶
When translating standard phrases, standardize. Note that English sometimes uses different forms to express the same thing.
“An error occurred while / in” → translate as “Er is een fout opgetreden bij”.
| English | Incorrect | Correct |
|---|---|---|
| An error occurred while writing a data file. | Tijdens het opslaan van een gegevensbestand is een fout gevonden. | Er is een fout opgetreden bij het schrijven van een gegevensbestand. |
“Are you sure” → “Weet u zeker dat”. Example: “Are you sure you want to remove this driver?” → “Weet u zeker dat u dit stuurprogramma wilt verwijderen?”
“Cannot / unable / not possible” — two acceptable Dutch patterns, but be consistent within a product:
| English | Pattern A | Pattern B |
|---|---|---|
| Cannot open the file “%s”. | Het bestand %s kan niet worden geopend. | Kan het bestand %s niet openen. |
| File “%s” could not be found. | Het bestand %s is niet gevonden. | Kan het bestand %s niet vinden. |
| Unable to open file. | Het bestand kan niet worden geopend. | Kan het bestand niet openen. |
| No longer able to read “%s” | %s kan niet langer worden gelezen. | Kan het bestand %s niet meer lezen. |
| Not possible to read file now. | Het bestand kan nu niet worden gelezen. | Kan het bestand nu niet lezen. |
| The tape cannot be read. | De band kan niet worden gelezen. | Kan de band niet lezen. |
“Do you want to continue? / Continue?” → “Wilt u toch doorgaan?” or “Wilt u doorgaan?” depending on context.
“Corrupt / critical / fatal / invalid / wrong”:
| English | Dutch |
|---|---|
| Corrupt | beschadigd |
| Critical | kritiek |
| Fatal | onherstelbaar |
| Invalid | ongeldig |
| Wrong | onjuist |
| English | Dutch |
|---|---|
| The file “%s” is corrupted. | Het bestand %s is beschadigd. |
| A critical error has occurred. | Er is een kritieke fout opgetreden. |
| A fatal error has occurred. | Er is een onherstelbare fout opgetreden. |
| Invalid column specified. Column values must be in the range A to IV. | Ongeldige kolomaanduiding. Kolomaanduidingen moeten liggen in het bereik van A tot IV. |
| Invalid number “%d”. | %d is geen geldig getal. (Not: Ongeldig getal %d.) |
“Not found / not available / there are no…” — Dutch generally needs a subject (“Er is geen…” / “Er zijn geen…”), where English often drops it:
| English | Incorrect | Correct |
|---|---|---|
| File not found. | Bestand niet aanwezig. | Het bestand is niet gevonden. |
| No network adapter found. | Geen netwerkadapter gevonden. | Er is geen netwerkadapter gevonden. |
| Value not found in Configuration Registry | Waarde niet gevonden in het Configuratieregister. | Geen waarde gevonden in het Configuratieregister. |
| Permanent connection not available. | Permanente verbinding niet voorhanden. | Er is geen permanente verbinding beschikbaar. |
| There are no available interrupts. The sound card will not work | Geen interrupts. De geluidskaart werkt hierdoor niet. | Er zijn geen interrupts beschikbaar. De geluidskaart zal niet werken. |
“Extremely low on memory / Not enough memory” — translate with “onvoldoende”:
| English | Incorrect | Correct |
|---|---|---|
| Extremely low on memory. Please save your work and close other applications to free up memory and continue. | Er is uitermate weinig geheugen beschikbaar. Sla wijzigingen op en sluit andere toepassingen af om geheugen vrij te maken en probeer het opnieuw. | Er is onvoldoende geheugen beschikbaar. Sla wijzigingen op en sluit andere toepassingen af om geheugen vrij te maken en probeer het opnieuw. |
| There is not enough memory available to load “%s”. | Er is niet genoeg geheugen beschikbaar om %s te laden. | Er is onvoldoende geheugen beschikbaar om %s te laden. |
| There is not enough free disk space to install Windows 10. | Er is niet voldoende ruimte op de schijf voor de installatie van Windows 10. | Er is onvoldoende ruimte op de schijf voor de installatie van Windows 10. |
Note: “your work” → “wijzigingen” (or another noun). Don’t translate as “uw werk”.
“Occurred” → “is … opgetreden”:
| English | Correct |
|---|---|
| A write fault occurred. | Er is een schrijffout opgetreden. |
| General error has occurred. | Er is een algemene fout opgetreden. |
“Please / Sorry” in error messages are not translated:
| English | Correct Dutch |
|---|---|
| Please cancel Setup and make more room, and then run Setup again. | Sluit Setup af en maak ruimte vrij op de schijf. Voer Setup vervolgens opnieuw uit. |
| Sorry, the file cannot be opened because part of it is missing. | Het bestand kan niet worden geopend omdat een gedeelte ontbreekt. |
“Please wait” → “Een ogenblik geduld.” Don’t use “Even wachten a.u.b.” or “Even geduld a.u.b.” or “Een ogenblik geduld a.u.b.”
“Please verify” → “Controleer of” (not “Controleer dat”). Example: “Drive %c: does not exist. Please verify the appropriate drive was given.” → “Station %c: bestaat niet. Controleer of het juiste station is ingevoerd.”
“Successfully” is usually omitted: “The operation was successfully completed.” → “De bewerking is voltooid.”
“Your” should be translated neutrally with an article wherever possible:
| English | Incorrect | Correct |
|---|---|---|
| The sound card is not detected in your machine. | Kan de geluidskaart niet vinden in uw computer. | Kan de geluidskaart niet vinden in de computer. |
| This will end your Windows session. | Hiermee sluit u uw Windows-sessie af. | Hiermee sluit u de Windows-sessie af. |
“Then” is always “vervolgens”, not “dan”. Sentences with “als-dan” should be avoided:
| English | Incorrect | Correct |
|---|---|---|
| Please cancel Setup and make more room, and then run Setup again. | Sluit Setup af en maak ruimte vrij op de schijf. Voer Setup dan opnieuw uit. | Sluit Setup af en maak ruimte vrij op de schijf. Voer Setup vervolgens opnieuw uit. |
Placeholders in error messages. Letter conventions:
%d,%ld,%u,%lu→ a number%c→ a letter%s→ a string
Examples: “Checking Web %1!d! of %2!d!” → “Checking Web
Keyboard shortcuts and keys¶
Keyboard shortcuts (access keys)¶
Letters or numbers in menu options that allow keyboard navigation. Rules in priority order:
- No duplicate keyboard shortcut may occur.
- Do not use letters or digits in brackets to indicate a shortcut, except when no letters are left in a dialog.
- Reuse the same shortcut within a product for a term that appears in multiple places (B for the “Bladeren” button).
- Avoid g, j, y, p, q (descenders) and i (especially in ‘ij’) — the underlining is hard to spot.
- Use the first letter of the most important word in an option. Examples: “Verschillen in rij” (r), “Verschillen in kolom” (k).
| Option | Allowed? | Notes |
|---|---|---|
| “Slim characters” (I, l, t, r, f) as shortcut | yes | Only when no other letters are left in a dialog |
| Descenders (g, j, y, p, q) as shortcut | no | |
| Extended characters as shortcut | no | |
| Additional letter in brackets after item name | yes | Only when no other letters are left |
| Number in brackets after item name | yes | Only when no other letters are left |
| Punctuation in brackets as shortcut | no | |
| Duplicate shortcut when no other character available | no | |
| No shortcut assigned (minor options only) | yes | Only when no letters are left |
Localization terminology¶
| Term | Usage |
|---|---|
| access key | A letter or number the user types to access UI controls with text labels. Access keys are assigned to top-level controls. Most use the Alt key. Example: F in Alt+F. |
| key tip | The letter or number that appears in the ribbon when Alt is pressed. In UI localization, the key tip is the last character after the “`” character. Example: Home`H. |
| shortcut key | A key the user types to perform a common action without using the UI. Shortcut keys are not available for every command. Most use Ctrl. Examples: Ctrl+N, Ctrl+V. Ctrl+letter combinations and function keys (F1–F12) are best choices for shortcut keys. |
Key names¶
References to key names — arrow keys, function keys, numeric keys — appear in normal text (not small caps).
| English Key Name | Dutch Key Name |
|---|---|
| Alt | Alt |
| Backspace | Backspace |
| Break | Break |
| Caps Lock | Caps Lock |
| Ctrl | Ctrl |
| Delete | Delete |
| Down Arrow | Pijl-omlaag |
| End | End |
| Enter | Enter |
| Esc | Esc |
| Home | Home |
| Insert | Insert |
| Left Arrow | Pijl-links |
| Num Lock | Num Lock |
| Page Down | Page Down |
| Page Up | Page Up |
| Pause | Pause |
| Right Arrow | Pijl-rechts |
| Scroll Lock | Scroll Lock |
| Shift | Shift |
| Spacebar | Spatiebalk |
| Tab | Tab |
| Up Arrow | Pijl-omhoog |
| Windows key | Windows-toets |
| Print Screen | Print Screen |
| Menu key | Menutoets |
Shortcut key combinations¶
Combinations like Ctrl+B or Shift+F12 are not localized — copy the US combinations exactly. Exception: Dutch products must support multiple keyboard layouts (US and Belgian Azerty). Where a US combination cannot be replicated on the Belgian keyboard, the shortcut must be localized. Test shortcut keys on both keyboard layouts.
| US Command | US Shortcut | Dutch Command | Dutch Shortcut |
|---|---|---|---|
| Help window | F1 | Help | F1 |
| Context-sensitive Help | Shift+F1 | Contextafhankelijke Help | Shift+F1 |
| Display pop-up menu | Shift+F10 | Pop-upmenu weergeven | Shift+F10 |
| Cancel | Esc | Annuleren | Esc |
| Activate/Deactivate menu bar | F10 | Menubalk activeren/deactiveren | F10 |
| Switch to next primary application | Alt+Tab | Schakelen naar de volgende toepassing | Alt+Tab |
| Display next window | Alt+Esc | Volgende venster weergeven | Alt+Esc |
| Display pop-up menu for window | Alt+Spacebar | Pop-upmenu voor het venster weergeven | Alt+Spatiebalk |
| Close active application window | Alt+F4 | Actief toepassingsvenster sluiten | Alt+F4 |
| Capture active window to Clipboard | Alt+Prnt Scrn | Schermafdruk kopiëren naar Klembord | Alt+Prnt Scrn |
| Capture desktop to Clipboard | Prnt Scrn | Bureaubladafdruk kopiëren naar Klembord | Prnt Scrn |
| Access Start button in taskbar | Ctrl+Esc | Menu Start in taakbalk activeren | Ctrl+Esc |
| Launch Task Manager | Ctrl+Shift+Esc | Taakbeheer en systeeminitialisatie starten | Ctrl+Shift+Esc |
| File New | Ctrl+N | Nieuw… | Ctrl+N |
| File Open | Ctrl+O | Openen | Ctrl+O |
| File Close | Ctrl+F4 | Sluiten | Ctrl+F4 |
| File Save | Ctrl+S | Opslaan | Ctrl+S |
| File Save as | F12 | Opslaan als | F12 |
| File Print Preview | Ctrl+F2 | Afdrukvoorbeeld | Ctrl+F2 |
| File Print | Ctrl+P | Afdrukken | Ctrl+P |
| File Exit | Alt+F4 | Afsluiten | Alt+F4 |
| Edit Undo | Ctrl+Z | Ongedaan maken | Ctrl+Z |
| Edit Repeat | Ctrl+Y | Opnieuw | Ctrl+Y |
| Edit Cut | Ctrl+X | Knippen | Ctrl+X |
| Edit Copy | Ctrl+C | Kopiëren | Ctrl+C |
| Edit Paste | Ctrl+V | Plakken | Ctrl+V |
| Edit Delete | Ctrl+Backspace | Verwijderen | Ctrl+Backspace |
| Edit Select All | Ctrl+A | Alles selecteren | Ctrl+A |
| Edit Find | Ctrl+F | Zoeken | Ctrl+F |
| Edit Replace | Ctrl+H | Vervangen | Ctrl+H |
| Edit Go To | Ctrl+G | Ga naar | Ctrl+G |
| Help | F1 | Help | F1 |
| Italic | Ctrl+I | Cursief | Ctrl+I |
| Bold | Ctrl+B | Vet | Ctrl+B |
| Underlined | Ctrl+U | Onderstreept | Ctrl+U |
| Large caps | Ctrl+Shift+A | Hoofdletters | Ctrl+Shift+A |
| Small caps | Ctrl+Shift+K | Kleinkapitalen | Ctrl+Shift+K |
| Centered | Ctrl+E | Centreren | Ctrl+E |
| Left aligned | Ctrl+L | Links uitlijnen | Ctrl+L |
| Right aligned | Ctrl+R | Rechts uitlijnen | Ctrl+R |
| Justified | Ctrl+J | Uitvullen | Ctrl+J |
Copilot predefined prompts¶
Copilot prompts are instructions or questions you use to tell Copilot what to do. Across Microsoft products, predefined prompts guide users in creating, learning, and using Copilot.
Best practices for localizing Copilot predefined prompts:
- Be clear and specific. English prompts are generally questions or requests starting with an action verb. Make sure target prompts are natural questions or requests. Use the imperative form for requests, rather than infinitive form.
- Keep it conversational. Use simple, natural language. Don’t sound like a machine. Use an informal tone of voice and form of address when translating Copilot predefined prompts.
- Be polite and professional. Use kind and respectful language. Don’t use slang or jargon.
- Use quotation marks — this helps Copilot know what to write, modify, or replace.
- Pay attention to punctuation, grammar, and capitalization.
- Pay attention to entity tokens. An entity token is a placeholder that triggers a pop-up menu so the user can choose an entity (file, contact, meeting). The position of the entity token must make sense in the target syntax. Entity tokens may appear within tags like
<entity type='file'>file</entity>or within( )/[ ]. The word inside the token is translated; the entity type attribute ('file','meeting') is not. - Place ghost texts at the end of the sentence. Ghost texts appear within placeholder tags. Always place them at the end so users don’t have to move the cursor.
- Be consistent. Similar English prompts should be translated consistently.
| Source prompt | Target prompt | Comments |
|---|---|---|
| List ideas for a fun remote team building event | Noem ideeën voor een leuk teambuilding-evenement | |
| What are the goals and topics from the meeting? Format each section with a bolded heading, a bulleted list, and bolded names | Wat zijn de doelen en onderwerpen van de vergadering? Geef ieder gedeelte een kop in een vet lettertype, een opsommingslijst en namen in een vet lettertype | |
Propose a new introduction to <entity type='file'>file</entity> |
Stel een nieuwe introductie voor <entity type='file'>bestand</entity> voor |
Translate inside the entity tags; don’t translate the type attribute. |
| List key points from [file] | Noem de belangrijkste punten uit [bestand] | The text within brackets should be translated. |
What were the open issues from <entity type='meeting'>meeting</entity>? |
Wat waren de openstaande problemen van <entity type='meeting'>vergadering</entity>? |
|
| Give me ideas for icebreaker activities for a new team | Geef me ideeën voor activiteiten waarmee het ijs in een nieuw team kan worden gebroken | |
Create a list of <placeholder>color names inspired by the ocean</placeholder> |
Maak een lijst met <placeholder>kleurnamen geïnspireerd op de oceaan</placeholder> |
Ghost text — placed at the end of the sentence. |
Create a brochure for <placeholder>a new theme park that is entirely underwater</placeholder> |
Maak een brochure voor <placeholder>een nieuw pretpark dat zich helemaal onder water bevindt</placeholder> |
Ghost text — placed at the end of the sentence. |
Voice and video considerations¶
A good voice video addresses only one intent, is not too long, has high audio quality, has visuals that add to the information, and uses the right language variant in voice-over.
Successful techniques:
- Focus on the intent — show the best way to achieve the most common task and stick to it.
- Show empathy — understand and acknowledge the viewer’s situation.
- Use SEO — include search phrases in the title, description, and headers.
- Talk to the customer as if they are next to you, watching you explain.
- Record a scratch audio file. Check length, pace and clarity.
English pronunciation¶
Generally, English terms and product names left unlocalized in target material should be pronounced the English way. Microsoft is pronounced the English way. However, if Dutch has an established pronunciation for a common term (“server”), use the local pronunciation. Pronunciation can be adapted to Dutch phonetics if the original sounds awkward.
If numbers are involved, pronounce them in Dutch.
| Example | Phonetics (Dutch) | Comment |
|---|---|---|
| SecurID | sekjoer ai die | |
| Release Pack | rielies pek | |
| Digest | daidjest | |
| Microsoft Windows Server 2019 | maicrosoft windows surver 2019 | Numbers pronounced Dutch; “Microsoft” English |
| Outlook Web Access | outloek web akses | |
| InfoPath | infoopath | |
| Exchange Server | ekstjeensj surver | |
| Program Files | prokram fails | |
| SecurNAT | sekjoer nat | |
| ECHO_REQUEST | ekko rekwest | |
| proxy | proksie | |
| .NET | dot net | .NET is considered a product name |
| Skype | skaip | Product names pronounced English |
Acronyms and abbreviations
Strict acronyms are pronounced like real words, the Dutch way:
| Example | Phonetics |
|---|---|
| RADIUS | radius |
| RAS | ras |
| ISA | iesaa |
| LAN | lan |
| WAN | wan |
| WAP | wap |
| MAPI | mapie |
| POP | pop |
Other abbreviations are pronounced letter by letter, Dutch way:
| Example | Phonetics |
|---|---|
| ICMP | ie cee em pee |
| URL | u er el |
| TCP/IP | tee cee pee slash ie pee |
| HTTP GET | ha tee tee pee gee ee tee |
| Rqc.exe | er q cee punt exuh |
| XML | ex em el |
| HTML | ha tee em el |
| SQL | es q el |
| OWA | oo wee aa |
| IIS | ai ai es (English — considered a product name) |
URLs
- “http://” is left out; the rest of the URL is read entirely.
- “www” is pronounced as “wee-wee-wee”.
- The dot can be omitted or read as Dutch “punt”.
Example: http://www.microsoft.com/nederland → “wee wee wee punt maikrosoft punt com slash nederland”.
Punctuation marks are implied by voice (? ! : ; ,). The en dash (–) is pronounced as a comma — a short pause. Em dashes should be replaced by commas in the written localized Dutch audio script.
Special characters (/ \ < > + -) are pronounced using the Dutch translations from Microsoft Terminology. Example: \ → “backslash”.
Tone¶
Match tone to the target audience — more informal, playful and inspiring for most Microsoft products and games; formal, informative and factual for technical texts.
Video voice checklist¶
Topic and script:
- Apply Microsoft voice principles: single intent, clarity, everyday language, friendliness, relatable context.
Title:
- Includes the intent.
- Includes keywords for search.
Intro: 10 seconds to set up the issue.
- Put the problem into a relatable context.
Action and sound:
- Keep something happening, both visually and audibly, but maintain an appropriate pace.
- Synchronize visuals with voice-over.
- Fine to alternate between first and second person.
- Repetition of big points is fine.
Visuals:
- Eye is guided through the procedure with smooth, easily trackable pointer motions.
- Judicious callout use.
- Appropriate use of motion graphics and/or branding-approved visuals.
Ending:
- Recaps are unnecessary.
Trademarks¶
Trademarked names and “Microsoft Corporation” should not be localized unless local laws require translation and an approved translated form is available. The full list of Microsoft trademarks is at: https://www.microsoft.com/en-us/legal/intellectualproperty/Trademarks/
Version strings¶
Product, feature and component names often appear in version strings as they appear in the software. Version strings containing copyright information should always be translated.
| US English | Dutch target |
|---|---|
| © 2022 Microsoft Corporation. All rights reserved. | Refer to Microsoft Terminology to check the correct translations for “All rights reserved” and “Microsoft Corporation”. |
Version numbers always contain a period (e.g. Version 4.2).
Reference materials¶
Normative references (adhere to these):
- Woordenlijst Nederlandse taal (‘Groene boekje’) (2015). Den Haag: Van Dale. The official spelling list.
- Van Dale Groot woordenboek van de Nederlandse taal (2015). 15th edition. Utrecht – Antwerpen: Van Dale Lexicografie.
- Jan Renkema, Schrijfwijzer (2020). 6th edition. Amsterdam: Boom uitgevers.
- woordenlijst.org — online version of the Groene boekje.
- taalunieversum.org — Taalunie language advice and resources.
Informative references (supplementary):
- Algemene Nederlandse Spraakkunst (ANS) (1997). W. Haeseryn et al. (Eds.). Groningen: Nijhoff.
- Algemene Nederlandse Spraakkunst, online version: http://ans.ruhosting.nl/e-ans/index.html
- Theo de Boer, Taalhandboek Nederlands (2011). Utrecht: Van Dale Uitgevers.
- Theo de Boer, Van Dale Taalhandboek spelling (2012). Utrecht: Van Dale Uitgevers.
FAQ¶
Should I use ‘u’ or ‘je’ when translating to Dutch?¶
Use ‘u’ for legal documents, business correspondence, medical materials addressed to patients in a clinical setting, government communication and most product documentation. Use ‘je/jij’ for marketing copy targeting younger consumers, gaming, social apps and some Microsoft consumer products that have adopted the informal tone. Pick one and stay consistent within the same product or document.
How are compound nouns written in Dutch?¶
As a single word — tekstobject (text object), cirkeldiagram (pie chart), laptopcomputer (laptop computer). Writing them with a space (tekst object) is an Anglicism and is wrong. Use a hyphen only for vowel clash (gala-avond), compounds with acronyms or numbers (HDMI-poort, 64-bits), brand-name compounds for readability (Microsoft-product, Esso-tankstation), or specific cases listed in the rules above.
Which Dutch vocabulary should I avoid in modern translation?¶
Archaic, bureaucratic and overly formal forms: tevens (use ‘ook’), betreffende (use ‘deze’ or omit), met ingang van (use ‘vanaf’), aanbevelenswaardig (use ‘aan te raden’), mijnerzijds/uwerzijds (use ‘van mij/van u’), ten aanzien van / met betrekking tot / in verband met (rewrite the sentence). See the full table in “Words and phrases to avoid” above.
When should I use a hyphen versus concatenation in Dutch compounds?¶
Default to concatenation. Use a hyphen when: (1) compounding with an acronym, single letter, digit or symbol (API-sleutel, HDMI-poort, 64-bits); (2) vowel clash that would create misreading (gala-avond, ski-instructeur); (3) compound with a brand or proper name where readability suffers without it (Microsoft-product); (4) compounds that already use a hyphen in English (up-to-date, lay-out); (5) Help-compounds referring to documentation (Help-venster); (6) niet- + adjective when the English source uses non- (niet-aaneengesloten).
What authoritative Dutch references should I use?¶
Normative: Woordenlijst Nederlandse taal (‘Groene boekje’, 2015, Van Dale), Van Dale Groot woordenboek van de Nederlandse taal (2015), Jan Renkema’s Schrijfwijzer (2020), woordenlijst.org and taalunieversum.org. Informative: Algemene Nederlandse Spraakkunst (ANS), Theo de Boer’s Taalhandboek Nederlands and Taalhandboek spelling (Van Dale).
How do I handle English loan words in Dutch?¶
When choosing the article (de/het), use motivation (does the word have formal features that fit Dutch noun classes), analogy (is there an equivalent Dutch term whose article fits) and frequency (which article dominates in published technical documentation). Compounds of English words accepted in Dutch are written as a single word (sciencefiction, voicemail, businessclass), with hyphens only for vowel clash, acronyms or readability.
Are em-dashes used in Dutch text?¶
No. Dutch does not use the em-dash. Any em-dash (—) or en-dash (–) in English source should be replaced by a comma or by parentheses in the Dutch translation. This applies in body text, marketing copy and even voice-over scripts.