Deu Deu StyleGuide
Deu Deu StyleGuide
Deu Deu StyleGuide
Table of Contents
1 Welcome ............................................................................................................................................... 4
1.1 Reference material........................................................................................................................ 4
2 Microsoft voice ..................................................................................................................................... 5
2.1 Choices that reflect Microsoft voice ............................................................................................. 6
2.1.1 Flexibility ............................................................................................................................... 6
2.1.2 Words and phrases to avoid ................................................................................................. 7
2.1.3 Word choice .......................................................................................................................... 9
2.1.4 Word-to-word translation................................................................................................... 10
2.2 Sample Microsoft voice text ....................................................................................................... 10
2.2.1 Address the user to take action .......................................................................................... 10
2.2.2 Promoting a feature ............................................................................................................ 11
2.2.3 Providing how-to guidelines ............................................................................................... 12
2.2.4 Explanatory text and providing support ............................................................................. 12
3 Inclusive language ............................................................................................................................... 13
3.1 Avoid gender bias........................................................................................................................ 14
3.2 Accessibility ................................................................................................................................. 19
4 Language-specific standards ............................................................................................................... 20
4.1 Grammar, syntax and orthographic standards ........................................................................... 20
4.1.1 Abbreviations ...................................................................................................................... 20
4.1.2 Acronyms ............................................................................................................................ 23
4.1.3 Articles ................................................................................................................................ 24
4.1.4 Capitalization ...................................................................................................................... 25
4.1.5 Compounds ......................................................................................................................... 26
4.1.6 Conjunctions ....................................................................................................................... 27
4.1.7 Contractions ........................................................................................................................ 28
4.1.8 Gender ................................................................................................................................ 28
4.1.9 Genitive ............................................................................................................................... 29
4.1.10 Localizing colloquialism, idioms, and metaphors ............................................................... 30
4.1.11 Nouns .................................................................................................................................. 31
4.1.12 Numbers.............................................................................................................................. 31
4.1.13 Prepositions ........................................................................................................................ 31
4.1.14 Pronouns ............................................................................................................................. 32
4.1.15 Punctuation ......................................................................................................................... 34
4.1.16 Sentence fragments ............................................................................................................ 38
4.1.17 Subjunctive.......................................................................................................................... 38
4.1.18 Symbols & nonbreaking spaces .......................................................................................... 39
4.1.19 Verbs ................................................................................................................................... 39
5 Localization considerations ................................................................................................................. 39
5.1 Accessibility ................................................................................................................................. 40
5.2 Applications, products, and features .......................................................................................... 40
5.3 English terminology and the German language system ............................................................. 41
5.4 Frequent errors—troublesome or conflictive words .................................................................. 44
5.5 Guidelines for the localization of wizard names ......................................................................... 46
5.6 Software considerations ............................................................................................................. 48
5.6.1 Arrow keys .......................................................................................................................... 48
5.6.2 Error messages .................................................................................................................... 48
5.6.3 Keyboard shortcuts ............................................................................................................. 58
5.6.4 Keys ..................................................................................................................................... 60
5.6.5 Numeric keypad .................................................................................................................. 63
5.6.6 Shortcut keys....................................................................................................................... 63
5.7 Trademarks ................................................................................................................................. 66
5.8 Voice video considerations ......................................................................................................... 67
5.8.1 English pronunciation ......................................................................................................... 67
5.8.2 Tone .................................................................................................................................... 71
5.8.3 Video voice checklist ........................................................................................................... 71
1 Welcome
Welcome to the Microsoft Localization Style Guide for German. This guide will help you
understand how to localize German content in a way that best reflects the Microsoft
voice.
• Make sure you understand the key tenants of the Microsoft voice.
• Familiarize yourself with the recommended style references in German.
Unless this style guide or the Language Portal provides alternative instructions, use the
orthography, grammar, and terminology in the following publications.
List of references:
2 Microsoft voice
Microsoft’s brand personality comes through in our voice and tone—what we say and
how we say it. The design renaissance across Microsoft products, services, and
experiences hinges on crisp simplicity.
• Warm and relaxed: We’re natural. Less formal, more grounded in honest conversations.
Occasionally, we’re fun. (We know when to celebrate.)
• Crisp and clear: We’re to the point. We write for scanning first, reading second. We
make it simple above all.
• Ready to lend a hand: We show customers we’re on their side. We anticipate their real
needs and offer great information at just the right time.
The Microsoft voice targets a broad set of users from technology enthusiasts and casual
computer users. Although content might be different for different audiences, the
principles of Microsoft voice are the same. However, Microsoft voice also means
keeping the audience in mind. Choose the right words for the audience: use technical
terms for technical audiences, but for consumers use common words and phrases
instead.
These key elements of Microsoft voice should also extend across Microsoft content for
all language locales. For each language, the specific choices in style and tone that
produce Microsoft voice are different.
2.1 Choices that reflect Microsoft voice
Translating into German in a way that reflects Microsoft voice means choosing words
and grammatical structures that reflect the same style as the source text. It also means
considering the needs of the audience and the intent of the text.
The general style should be clear, friendly and concise. Use language that resembles
conversation observed in everyday settings as opposed to the formal, technical
language that is often used for technical and commercial content.
When you are localizing source text written in Microsoft voice, feel free to
choose words that aren’t standard translations if you think that’s the best way to stay
true to the intent of the source text.
Because Microsoft voice means a more conversational style, literally translating the
source text may produce target text that is not relevant to customers. To guide your
translation, consider the intent of the text and what the customer needs to know to
successfully complete the task.
2.1.1 Flexibility
It’s important for translators to modify or re-write translated strings so that they are
more appropriate and natural to German customers. To do so, try to understand the
whole intention of the sentences, paragraphs, and pages, and then re-write just like you
are writing the contents yourselves. Sometimes, you may need to remove any
unnecessary content.
Ooh, ooh, ooh, what a little moonlight can Etwas Mondlicht erhellt die dunkelste
do to you! Yes, but how about a LOT of Nacht. Aber wie steht’s mit VIEL
moonlight? This free theme for Mondlicht? Dieses kostenlose Design für
Windows features brilliant full moons, Windows enthält strahlende Vollmonde,
hazy winter moons, and moons rising diesige Wintermonde sowie dramatische
dramatically over castles, mountains, Mondaufgänge über Burgen, Bergen und
cityscapes, and rock formations. Städten.
Microsoft voice avoids an unnecessarily formal tone. The following table lists some US
English words that add formality without adding meaning, along with more
common equivalents.
Achieve Do
Attempt Try
Configure Set up
Encounter Meet
Execute Run
Halt Stop
However But
In addition Also
In conjunction with With
Locate Find
Modify Change
Navigate Go
Obtain Get
Perform Do
Purchase Buy
Refer to See
Resolve Fix
Subsequent Next
Terminate End
Toggle Switch
Utilize Use
See below words or phrases to avoid in German and their equivalent words or phrases
to be used to convey the German Microsoft voice.
Terminology
Use approved terminology from the Microsoft Language Portal where applicable,
for example for key terms, technical terms, and product names.
Microsoft voice text written in US English prefers the short, simple words spoken
in everyday conversations. In English, shorter words are generally friendlier and
less formal. Short words also save space on screen and are easier to read quickly.
Precise, well-chosen words add clarity, but it is important to be intentional about using
everyday words that customers are accustomed to.
The German Microsoft voice can be conveyed through similar means by using short
words used by people in daily conversations. Take care to adhere to approved
terminology and not use different target terms for already established and approved
terms. There are only some occasions that allow shortened form of words. These words
are well-established in common usage. Be careful with using abbreviated forms in
German, as they might not be understood by all target audiences or it may have
different connotations in other German speaking countries.
en-US
de-DE
source de-DE word usage
word
term
Literal translation should be avoided, as it often fails to get the sense of the text across
and sounds unnatural, even ridiculous. If necessary, split or merge sentences; omit
descriptors to make the text snappier.
Incorrect German
English text Correct German translation
translation
Find what you need on the Mit dem für Windows Suchen Sie mit dem für
web, using the browser best optimierten Browser steht Windows optimierten
suited for Windows. Ihnen das Web offen. Browser im Internet.
You use multiple PCs and a Sie verwenden verschiedene Sie verwenden verschiedene
phone. PCs und ein Smartphone? PCs und ein Telefon?
Compose your vision within Lassen Sie Ihrer Kreativität in Realisieren Sie in der Cloud
the cloud der Cloud freien Lauf. Ihre Vision.
Dieses Dokument
This document will be
wird automatisch in die richtige Voice talks to the
automatically moved to the
Bibliothek und den richtigen user informatively and
right library and folder after
Ordner verschoben, nachdem Sie directly on the action that
you correct invalid or
die ungültigen oder fehlenden will be taken.
missing properties.
Eigenschaften korrigiert haben.
3 Inclusive language
Microsoft technology reaches every part of the globe, so it's critical that all our
communications are inclusive and diverse. These guidelines provide examples on how to
use inclusive language and avoid habits that may unintentionally lead to
marginalization, offense, misrepresentation, or the perpetuation of stereotypes.
General guidelines
Kolleg*innen Kollegen
colleagues; guys; ladies and alle
everyone; all gentlemen Kollegen und
Kolleginnen
Use the suffixes -hilfe, -kraft, -personal, -schaft, -leute to create neutral forms that
replace individual masculine or feminine forms whenever possible. Or, use a general
term instead that omits the notion of gender (like Eltern, Personen). Or, use nominalized
present participles or plural forms. This method results in nouns that are short and
explicit. However, in a highly technical context, they sometimes sound contrived and
should therefore be used with caution. Use nouns in this category only if they are
already commonly used in German. Avoid inventing new words that sound unnatural.
Examples:
Lehrkräfte, Eltern, Personen, Fachleute, Freundeskreis for "friends", Kundschaft for
"customers"
Note: Many terms can be neutralized using the ‘-schaft’ suffix. This suffix is used to refer
to the whole group of individuals, when we are referring to many people, but not to
subgroup of individuals. When referring to specific individuals, then the gender asterisk
should be used for the plural form.
The table below provides en-US examples of compounds words containing man or men
that should be avoided in English.
English examples
humanity, people,
man, mankind
humankind
sales
salesman
representative
synthetic,
manmade
manufactured
workforce, staff,
manpower
personnel
The table below contains examples of gender-biased words or compounds that should
be avoided in German and the alternative that should be used to promote gender-
inclusivity.
Wachpersonal Wachmann
Bankkaufperson Bankkaufmann
When presenting generalization, use plural noun forms (for example, Personen,
Menschen, etc).
Don't use gendered pronouns (sie, ihre, er, sein, etc.) in generic references. Instead:
A user with the If the user has the Benutzer*innen mit Ein Benutzer mit
appropriate rights appropriate rights, entsprechenden entsprechenden
can set other users' he can set other Rechten können… Rechten kann…
passwords. users' passwords.
When you're writing about a real person, use the pronouns that the person prefers,
whether it's er, sie, es, or another pronoun. It's OK to use gendered pronouns (like er,
sie, sein, and ihr) when you're writing about real people who use those pronouns
themselves.
Examples:
Source Former
New approach Comment
term approach
Gender-neutral noun to be
1. Undetermined context:
applied (singular and plural).
Lernende*r (singular) Lernende
Note: If in a document a context
Schüler (plural)
is clear and specific, like school
(lower 2. Lower education:
and university, then (and only
student education) Schulkind (singular)
then) the translation may be
Student Schulkinder (plural)
contextualized with the context-
(university) 3. University:
sensitive terms Schulkind(er)
Student*in (singular)
(lower education) and
Studierende (plural)
Student*in(nen) (university).
Teilnehmende is a gender-
neutral plural noun. To refer to
Teilnehmer*in (singular) participant in the singular, as
participant Teilnehmer
Teilnehmende (plural) there is no gender-neutral
option in the lexicon, the
gender asterisk should be used.
Mitarbeitende is a gender-
neutral plural noun. To refer to
Mitarbeiter*in (singular) employee in the singular, as
employee Mitarbeiter
Mitarbeitende (plural) there is no gender-neutral
option in the lexicon, the
gender asterisk should be used.
Notes:
- Use your best judgment to use a plural form with asterisk, if this alternative enhances
the style in a specific situation. A wording like “hart arbeitende Mitarbeitende” could
sound a little strange due to the duplicate usage of “arbeitende.” In such cases, it's
justifiable to use gender-neutral alternatives.
- Gender-neutral language should be used in new products and content going forward,
but it’s acceptable that we don’t update all existing or legacy material. It is up to each
product team to decide the best approach for legacy content.
3.2 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 or sickness, such
as erkrankt an or leidet an. Don't mention a disability unless it's relevant.
Menschen/Personen Normale,
person without a normal person;
ohne Behinderung Nichtbehinderte,
disability healthy person
Gesunde
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.
Wählen Klicken
Select Click
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 und, plus, and rund. Screen readers can misread text that uses
special characters like the ampersand (&), plus sign (+), and tilde (~).
4 Language-specific standards
This part of the style guide contains information and guidelines specific to the German
language.
This section includes information on how to apply the general language and syntax rules
to Microsoft products, online content, and documentation.
4.1.1 Abbreviations
Common abbreviations
You might need to abbreviate some words in the UI (mainly buttons or options
names) due to lack of space.
Use the common abbreviations listed below. Note, however, that we do not recommend
extensive use of abbreviations.
das heißt d. h.
gegebenenfalls ggf.
in der Regel i. d. R.
und Ähnliches u. Ä.
unter anderem u. a.
unter Umständen u. U.
vergleiche vgl.
beziehungsweise bzw.
zum Beispiel z. B.
zum Teil z. T.
Expression Acceptable abbreviation
zurzeit zz.
Further guidelines
1. If a sentence ends with an abbreviation that has its own period, there is no additional
end-of-sentence period.
2. Use a non-breaking space (CTRL+SHIFT+SPACEBAR) in abbreviations such as z. B. or d. h.
3. If non-breaking spaces cannot be used (e.g. in Help files), it is also acceptable to write
these abbreviations without a space to avoid having one letter move to the beginning of
the next line.
Abbreviation Comment
In addition to common measurements such as km, m, cm, mm, etc. the following
abbreviations are used in technical documentation.
Abbreviation
Measurement Comment/Example
(+)
Megabits pro
MBit/s used to be (-) Mbit/s
Sekunde
Kilobits pro
KBit/s used to be (-) Kbit/s
Sekunde
Megabytes pro
MB/s
Sekunde
Kilobytes pro
KB/s
Sekunde
Megahertz MHz
Exclusion list:
• "oder,"
• "und,"
• "allgemein,"
• "etwas,"
• "links,"
• "rechts" or
• anything else that may not be immediately recognizable to a user.
4.1.2 Acronyms
Acronyms and initialisms are words made up of the initial letters of major parts of a
compound term. Some well-known examples are WYSIWYG (What You See Is What You
Get), DNS (Domain Name Server) or HTML (Hypertext Markup Language). They are not
as common in German as they are in English.
Caution: Don't include the full form of the last letter after the acronym or initialism. It is
a redundancy that occurs in source text sometimes, but it should be corrected in
translation.
Example:
German equivalents
In UA material, use the German full form on first mention followed by the English full
and short forms in parentheses.
Example:
In UI material, other than in wizards, there is usually not enough space for all three
variants. If there are space constraints or if there is no "first" occurrence, it is up to the
localizers to judge whether the English short form is understandable without German
equivalent.
The localizer should also take into account that users of distinct products will also have
different levels of knowledge: A German user of Exchange may readily understand what
"DL" stands for, while the average German Windows user may not and prefer the
German equivalent "Verteilerliste." Try to be consistent within a product.
Note: Although the English short form generally can't be derived from the
German translation, creating a new short form from the German term is not an option.
Many acronyms and initialisms are standardized and remain in English. They are only
followed by their English full form if necessary for understanding. When the short
form is rather common, adding the full form does not add value, but may be confusing.
Examples:
4.1.3 Articles
This section treats articles for product and feature names. For general information on
grammatical gender, refer to German grammar references as well as to the section
Gender.
Like most proper names, Microsoft product names and non-translated feature names
are used without definite or indefinite articles in both English and German. "Von" and a
dative construction is an effective way of avoiding a genitive form and the associated
inflection. A genitive "s" must not be attached to trademarked product names, as it
could be interpreted as a modification of such names.
Example:
Feature names in German are not treated as proper names and therefore take a definite
or indefinite article.
Example:
Here are aspects to consider for English loan words used in Microsoft products:
• Motivation: Does the English word have any formally motivated features that would
allow a straightforward integration into the noun class system of the German language?
• Analogy: Is there an equivalent German term whose article could be used?
• Frequency: Is the term used in other technical documentation? If so, what article is used
most often?
The internet may be a helpful reference here.
Always consult the Language Portal to confirm the use of a new loan word and
its proper article to avoid inconsistencies.
Example:
4.1.4 Capitalization
Capital ẞ
On 29th June 2017, the capital ẞ (ß – ẞ) has become an official letter in German
orthography.
It can be used to replace the capital “SS” in words that are written in capital letters and
use the “SS” as a replacement for the capital ẞ.
Example: STRASSE – STRAẞE
In English titles, for example, all nouns, pronouns, adjectives, verbs, adverbs, and
subordinate conjunctions (e.g. that, until, which) are capitalized. Do not apply the same
principle to German titles. Instead, follow the general German capitalization rules. The
same rule applies to software strings.
Example:
4.1.5 Compounds
Generally, compounds should be understandable and clear to the user. Overly long
or complex compounds should be avoided. Keep in mind that unintuitive compounds
are ultimately an intelligibility and usability issue.
The Microsoft standard is that compounds of three components or less are written in
one word, unless there are definite problems with the readability of a term (i.e.
not subjective readability, but the coming together of several letters to form
an unintended character combination, e.g. US: back end, would be "backend," the
German present participle of "backen" => for better readability: Back-End), or the
software design requires hyphenation. Regarding hyphenation we do not make a
difference between English and German compounds anymore.
Examples:
Product Names
Product names are not hyphenated for legal reasons. However, in order to offset
the actual product name from the word that follows in a compound, the hyphen is
placed right between the product name and the following term. Please note that
this rule applies even if the word that follows is an English term. The
only exception is a product name directly followed by the word “Setup,” because
this Setup is treated like a product name.
Examples:
Skype Manager-
Administrator
Skype-Version
4.1.6 Conjunctions
For en-US Microsoft voice, use of conjunctions is another way to help convey a
conversational tone. Starting a sentence with a conjunction can be used to convey an
informal tone and style.
Similarly, the de-DE Microsoft voice can use conjunctions and adverbs in order to
convey a more natural and easier to understand tone.
On opening the document Beim Öffnen des Dokuments in Wenn Sie das Dokument in
in <product> potential <Produkt> werden Ihnen <Produkt> öffnen, können
coauthors will be shown in mögliche Co-Autoren mithilfe Sie eventuelle Co-Autoren
the Info bar by a ballon eines Ballontipps in der unteren per Ballontipp unten in der
tip. Infoleiste angezeigt. Infoleiste sehen.
For en-US Microsoft voice, the use of contractions helps to convey a conversational tone
and are used whenever possible.
If the German Microsoft voice can be conveyed, then contractions are fine to use. While
there are some perfectly acceptable and frequently used contractions, there are others
that are too informal.
Here are some examples of contractions that can be used in the right context.
Try again. Versuchern Sie es noch mal. Versuchen Sie’s noch mal.
4.1.8 Gender
For information on grammatical gender, follow general rules for the German language.
For terminology, where gender information in the Language Portal deviates from these
rules, Microsoft term information overrides the general language rules.
Example:
Microsoft terminology
database)
For information on gender bias, refer to the section Avoid gender bias
4.1.9 Genitive
First and foremost, follow the standard conventions on using -es vs. -s in genitive
formation. However, in cases where both solutions are possible, always use the simple
ending -s.
Following the standard conventions, words ending on -s, -ß, -z, -tz, -x need the -es
genitive.
Examples:
Convention 3: -s Genitive
In cases where both endings are valid, always use the simple ending -s. (This applies also
to words like "Debitor" or "Kreditor" where Duden allows a genitive formation with "-s"
or "-en.")
Examples:
• Text -> (+) des Texts
• Feld -> (+) des Felds
• Tag -> (+) des Tags
• Vertrag -> (+) des Vertrags
Convention 4: Abbreviations
Examples:
The Microsoft voice allows for the use of culture-centric colloquialisms, idioms and
metaphors (collectively referred to "colloquialism").
We've hit a snag. Wir sind leider auf ein Problem gestoßen.
It's lonely in here. Go to the Store to Es ist so leer hier. Besuchen Sie den Store, um
add some podcasts. Podcasts hinzuzufügen.
4.1.11 Nouns
Find information on specific nouns in the section on English Terminology and the
German Language System.
4.1.12 Numbers
Follow Duden guidelines on when to use numerals (symbol that represents a number. e.g. 1, 2, 3,
234, etc.) and when to spell out numbers (one, two, three, two hundred and thirty-four).
4.1.13 Prepositions
For the en-US Microsoft voice, use of prepositions is another way to help convey
a casual or conversational tone. Starting or ending a sentence with a preposition is
acceptable practice in conveying the en-US Microsoft voice, however, this does not
apply to German.
Translate English prepositions according to their context and avoid anglicism. The
following prepositions have become standard practice at Microsoft:
en-US
de-DE Expression Comment
Expression
update/upgrade
(+) aktualisieren/upgraden auf
to
click (on)
(+) klicken auf
something
on the net (+) im Netz (werk) Do not use: (-) auf dem
For information (+) Informationen zu/über ... Do not use: (-) "Für Informationen
on ... see ... finden Sie unter ... zu/über ... sehen Sie ..."
4.1.14 Pronouns
For the en-US Microsoft voice, use of personal pronouns is a powerful way to express
all the attributes of the Microsoft voice. The source text is moving away from indirect
methods of referring to the user as "user" and instead addressing the user directly
through the use of first- and second-person pronouns like "you." Third-person
references, such as "user," are avoided as they sound formal and impersonal.
The German Microsoft voice follows the usage of the en-US voice if this does not
harm the grammar or create redundancy. Addressing the user by first-person or second-
person pronouns conveys the meaning that this person is not anonymous and is an
agent of the situation and all actions. The usage of “wir” (we) generates the image of
a team behind the software who cares about what the user is doing. However, always
check the context and decide according to your feel for the language. In some cases the
use of "we" might sound strange and might need to be replaced by a more neutral
translation in German even if "we" is used in the source text.
Examples:
Benutzer können den Zeitpunkt für die Installation Sie bestimmen, wann neue Updates
von neuen Updates festlegen. installiert werden sollen.
Diese Einstellung bietet Benutzern eine optimale Wählen Sie eines der Schemas aus
Anzeigedarstellung. oder erstellen Sie ein neues.
Important: For German, when addressing children/teens under age of 18, use the
informal “du”. Usually, you will get specific instructions at localization time.
Your parent might not want you to visit Wahrscheinlich möchte deine Mutter oder dein
this website. Vater nicht, dass du diese Website besuchst.
If you're not sure this website would be Wenn du nicht sicher bist, ob deine Eltern diese
OK with your parents, don't visit it. Website erlauben, solltest du sie nicht besuchen.
Note: in general, verify the usage of "I", "we" and "you" in product-specific guidelines.
Examples:
• My Computer --> (+) Arbeitsplatz
• My Documents --> (+) Eigene Dateien
4.1.15 Punctuation
• Decimal Separator: ,
• Decimal Separator Description: comma
• Decimal Separator Example: 10,50 cm; 199,95 €; 1.495,68 kg
• Thousand Separator: .
• Thousand Separator Description: period
• Thousand Separator Example: 9.999,99 €; 120.000 kg; 1.250.254,99 m
• Notes: Numbers are written in groups of 3 digits.
• Decimal Separator: .
• Decimal Separator Description: period
• Decimal Separator Example: 10.50 cm; 199.95 SFR; 1'495.68 kg
• Thousand Separator: '
• Thousand Separator Description: apostrophe
• Thousand Separator Example: 9'999.99 SFR; 120'000 kg; 1'250'254.99 m
• Notes: Numbers are written in groups of 3 digits.
Comma
Follow general German language grammatical rules on using comma. Find specific
information below.
Comma before „und“ or „oder“: If „und“ or „oder“, connect two full sentences (with a
subject and verb), they need to be preceded by a comma.
For information on the use of commas in numerals refer to the top of this section.
Colon
Follow general German language grammatical rules on using colons. Find specific
information below.
Special case: Do not use colons or other punctuation mark at the end of procedural
titles.
Example:
Hyphen
The hyphen is used to divide words between syllables, to link parts of a compound
word, and to connect the parts of an inverted or imperative verb form.
For detailed information and examples on the Microsoft standard use of hyphens in
compounds, go to the section Compounds.
En Dash
The en dash is used as a minus sign, usually with spaces before and after.
Character En Dash
Example:
• – 2.375,99 EUR
The en dash is also used in number ranges, such as those specifying page numbers. No
spaces are used around the en dash in this case.
Em Dash
Character Em Dash
Character Ellipses
Period
Follow general German language grammatical rules on using periods. Find specific
information below.
Periods in lists and tables: To avoid inconsistencies when setting a period at the end of
a list or table entry, adhere to the following guidelines.
Guidelines:
For information on the use of periods in numerals refer to the top of this section.
Quotation marks
Quotation marks are, for example, used when a software user interface element is
referred to.
Some fonts do not display the German closing quotes correctly. In cases of
single sourcing where a Help engine does not support curly quotation marks,
using straight quotation marks is also a valid solution in printed documentation which is
later converted to Help.
Examples:
1. Favored solution (curly, bottom/top): „Anführungszeichen“
2. Alternate solution (straight, top/top): "Anführungszeichen"
Parentheses
Example:
While the English modern voice allows sentence fragments to convey a conversational
tone, it is very unusual in written communication for German. On rare occasions,
fragments or contractions are allowed, e.g. in headings or eye-catchers on Websites.
Important: Make sure that the fragment fits into the context and no relevant
information gets lost.
To start the process So starten Sie den Prozess Auf geht’s or Und so geht's
4.1.17 Subjunctive
In German, the subjunctive form is mainly used in written form and indirect speech.
It is, in general, not appropriate style in the Microsoft context. Rather use active voice
and imperative or indicative mood. These are easier to understand than subjunctive
mood or passive voice, which can be confusing or sound formal.
4.1.18 Symbols & nonbreaking spaces
Symbols
This style guide does not cover all symbols used in Microsoft products.
Nonbreaking spaces
In HTML coding, the nonbreaking space ( ) is a character entity which can create
white space between words or web page elements, or stop the browser from breaking a
line in the wrong place.
• Mr. Mustermann à Herr Mustermann
Note: Nonbreaking spaces should only be used whenever they are present also in the
US text. Otherwise it is recommended to use a blank space as nonbreaking spaces can
create functionality problems. They can cause problems in the generation of the final
documents and should not be used in online help and documentation live content.
4.1.19 Verbs
For US English Microsoft voice, verb tense helps to convey the clarity of Microsoft voice.
Simple tenses are used. The easiest tense to understand is the simple present, like we
use in this guide. Avoid future tense unless you are describing something that will really
happen in the future and the simple present tense is inapplicable. Use simple past tense
when you describe events that have already happened.
Follow general German language grammatical rules on using verbs. For specific
information and examples, refer to the following sections:
• Some verbs require different translations, depending on the concept or context. Refer to
the sub-section Terminological Ambiguities in the section Frequent errors—troublesome
or conflictive words for detailed information and examples.
• English terminology and the German language system
• Error messages
5 Localization considerations
This section contains guidelines for localization into German.
General considerations
The language in Microsoft products should have the "look and feel" of a product
originally written in German, using idiomatic syntax and terminology, while at the same
time maintaining a high level of terminological consistency, so as to guarantee the
maximum user experience and usability for our customers.
5.1 Accessibility
Accessibility options and programs are designed to make the computer usable
by people with cognitive, hearing, physical, or visual disabilities.
Application and product names are often trademarked or may be trademarked in the
future and therefore might remain in English even in target-language markets.
Occasionally, feature names are trademarked, too (e.g. IntelliSense™).
Version numbers
If you are using Android 9.0 or (+) Wenn Sie Android 9.0 oder höher
later... verwenden...
Version numbers are usually also a part of version strings, but technically they are not
the same.
5.3 English terminology and the German language system
The influx of English into the German language system has significantly increased with
the "information revolution." Although there is no language governing institution
in German-speaking countries, there are popular movements to resist this trend. For the
localization of Microsoft products into German, use the terminology that is most widely
used in the computer press and among users. This naturally depends on the target
market of each product (technical products are bound to contain more specialized
language which usually means more English terminology).
While it is acceptable to use English terms if they are indeed the industry standard in
Germany, it is by no means an alternative to researching current industry standards.
False friends such as "Billion" for "billion" and stylistic anglicisms are still major
translation mistakes (see section on anglicisms below). When incorporating English
terms they must follow German grammar and syntax rules. The Institut für deutsche
Sprache has guidelines for the formation and incorporation of neologisms, which we
have adapted for this style guide. In cases that require more information, we can consult
the IDS at any time.
Nouns
Examples:
Plural Formation: English loan words are generally pluralized with the plural -s.
Examples:
• (+) Clients
• (+) Websites
• (+) Downloads
Special cases:
English loan words ending in the letter -y simply receive a plural -s according to the new
German spelling.
Example:
• (+) Proxys
Loan words with the suffix -er follow German plural formation rules:
Examples:
• (+) Server
• (+) Manager
• (+) Viewer
Terms ending in -or receive a plural -s or -en depending upon whether they are already
existing German nouns:
Examples:
• (+) Locators
• (+) Administratoren
Example:
• (+) Agents
Verbs
In a few cases English verbs are used as loan words. They follow German conjugation
rules for weak verbs.
Examples:
• chat => (+) chatten, sie chattet, wir haben gechattet, zu chatten
• debug => (+) debuggen, sie debuggt, wir haben debuggt, zu debuggen
• crawl => (+) crawlen, sie crawlen, wir haben gecrawlt, zu crawlen
When faced with an English loan word previously used in Microsoft products, consider
the following options:
• Motivation: Does the English word have any formally motivated features that
would allow a straightforward integration into the noun class system of the
German language?
• Analogy: Is there an equivalent German term whose article could be used?
• Frequency: Is the term used in other technical documentation? If so, what article
is used most often?
• Refer to the Microsoft terminology database to confirm the use of a new loan word and
its proper article to avoid inconsistencies.
Example:
Anglicisms
Anglicisms also increasingly sneak into sentence structure and syntax. Edit your
documents with this in mind. The following examples illustrate the type of direct
translation that increasingly occurs, but is not acceptable.
Example:
Correct de-DE
en-US source Anglicism in de-DE
translation
(+) Um weitere
For more
Informationen zu
information (-) Für weitere Informationen kontaktieren Sie ...
erhalten, wenden Sie
contact ...
sich an ...
5.4 Frequent errors—troublesome or conflictive words
There are certain cases where terminological or orthographic ambiguities leave room for
interpretation. The intention of this section is to provide recommendations for these
specific cases.
For additional information and examples, see also: Error Messages and Anglicism in the
section English Terminology and the German Language System.
Orthographic ambiguities
The German orthographic reform sometimes allows for spelling alternatives. As long as
consistency is not at risk and other style guide rules don't prevent it, the alternatives
recommended by the Duden should be used. The following cases are mentioned here
for clarification only.
The new German spelling rules allow two different spellings for some words. To avoid
inconsistencies in Microsoft products, use the following forms:
Examples:
• so dass / sodass -> (+) sodass (BUT: aber er arbeitete so, dass er krank wurde)
• mit Hilfe / mithilfe -> (+) mithilfe
• auf Grund / aufgrund -> (+) aufgrund
• in Frage / infrage -> (+) infrage
• weit greifend / weitgreifend -> (+) weitgreifend
• schwer wiegend / schwerwiegend -> (+) schwerwiegend
• fertig stellen / fertigstellen -> (+) fertig stellen (until further notice)
Terminological Ambiguities
Some terms have different translations, depending on the concept or context. Below are
answers to some frequently asked questions.
a) select, click, point – auswählen, markieren, aktivieren, klicken auf, zeigen auf
The default translation for the US term "select" is "auswählen." It is rather general in its
meaning and should be used whenever the context does not require another specific
translation such as "aktivieren" for check boxes, or "markieren" when the emphasis is on
highlighting.
The US text mostly uses the verbs "click" and "point" (instead of "choose"). The German
equivalents are "klicken auf" and "zeigen auf" (always used with the preposition
"auf"). "Enter" and "type" should be translated as "eingeben" when the user uses the
keyboard for input.
select = auswählen
In the drop-down (+) Wählen Sie in der
The user chooses a pre-
Lists list, select an Dropdownliste eine
existing entry, e.g. in a
option. Option aus.
list.
select = aktivieren
Select the check (+) Aktivieren Sie das Correspondingly, "to
Check Boxes
box. Kontrollkästchen. clear" a check box =
"deaktivieren."
On the ____ menu, On the File menu, (+) Klicken Sie im Menü Datei
Menus
click _____. click Open. auf Öffnen.
On the ___ menu, On the View menu, (+) Klicken Sie im Menü Ansicht
Cascading
click ___, and then click Fonts, and then auf Schriftarten und dann auf
Menus
click ___. click Small. Klein.
Item en-US Wording en-US Example de-DE Example
On the shortcut
Shortcut On the shortcut (+) Klicken Sie im Kontextmenü
menu, click Set Home
Menus menu, click _____. auf Homepage festlegen.
Page.
In the _____ box, In the Color box, click (+) Klicken Sie im Feld Farbe
List Boxes
click ____. Red. auf Rot.
"Hinweis" is used for notes to the user, e.g. in software or documentation. "Notiz" is
used for notes the user is taking.
"Anmerkung" should not be used except in cases where "note" is used in the same text
or section as "remark."
General guidelines
N-Assistant
Connection Rule 1: One noun (For the treatment of
Wizard (+) Verbindungs-Assistent is followed by a the Setup wizards, refer
Installation (+) Installations-Assistent hyphen and to the information
Wizard “Assistent" available on the
relevant entries in the
en-US source de-DE target Rule Pattern
Microsoft terminology
database and mind
possible conceptual
differences. There are
good reasons for using
translations like "Two-
Sided Printing Setup
Wizard" > "Assistent
zum Einrichten des
beidseitigen Drucks" or
"Stationary Setup
Wizard" > "Briefpapier-
Assistent.")
Exception:
Command (+) Befehlsschaltflächen-
In cases where the
Button Wizard Assistent
wizard name
en-US source de-DE target Rule Pattern
cannot be
separated, it is
acceptable to have
a compound with
more than two
elements followed
by a hyphen and
"Assistent."
This section refers to all menus, menu items, commands, buttons, check boxes, etc.,
which should be consistently translated in the localized product.
The arrow keys move input focus among the controls within a group. Pressing the right
arrow key moves input focus to the next control in tab order, whereas pressing the left
arrow moves input focus to the previous control. Home, End, Up, and Down also have
their expected behavior within a group. Users can’t navigate out of a control group
using arrow keys.
Error messages are messages sent by the system or a program, informing the user of an
error that must be corrected in order for the program to keep running. The messages
can prompt the user to take action or inform the user of an error that requires rebooting
the computer.
Oops, that can't be blank... Leider darf dieser Eintrag nicht leer sein ...
German style in error messages
Be consistent in your use of terminology and style and don't translate them literally.
Standard phrases should be translated consistently, even if the error message in English
is not 100% consistent.
The phrases bellow commonly occur in error messages. When you are translating them,
try to use the provided target phrases. However, feel free to use other ways to express
the source meaning if they work better in the context.
Examples:
en-US
de-DE target Example Comment
source
(+) … kann
The texture file cannot be Could not/couldn't V
nicht.
opened / Couldn't open output = N ... konnte nicht
Cannot … file (+) Die Strukturdatei kann
(+) … konnte
Could not … nicht geöffnet werden. / Die (+) (Do not use: (-) Konnte
nicht. Ausgabedatei konnte nicht … nicht at the beginning
geöffnet werden. of the sentence)
Cannot find
…
Cannot locate
Could not
Microsoft Conversion Library.
find …
(+) finden (+) Die Microsoft- Locate, find = finden
Unable to
Konvertierungsbibliothek kann
find …
nicht gefunden werden.
Unable to
locate …
Not enough not enough,
memory insufficient = nicht
Insufficient genügend (Do not
memory Not enough memory to use: (-) nicht
There is not complete this operation. ausreichend);
(+) nicht
enough
genügend
memory (+) Nicht genügend Speicher Also: use the definite
There is not zum Abschließen des Vorgangs. article instead of the
enough demonstrative pronoun
memory unless it is important in
available context.
... is not
FCB unavailable.
available (+) Unavailable = nicht
... is nicht verfügbar verfügbar
(+) FCB ist nicht verfügbar.
unavailable
When localizing error messages containing placeholders, try to find out what will replace
the placeholder. This is necessary for the sentence to be grammatically correct when the
placeholder is replaced with a word or phrase. Note that the letters used in placeholders
convey a specific meaning, see examples below:
Wrong number of
arguments or (+) Falsche Anzahl von Argumenten Anzahl von (Do not
invalid property oder ungültige Eigenschaftszuweisung. use: (-) an or (-) der)
assignment
Read error on input file. (+) Lesefehler in der Eingabedatei. Do not use: (-) auf
Input past end of file. (+) Eingabe hinter dem Dateiende. Do not use: (-) nach
Metaphorically used
The network is down./
(+) Das Netzwerk ist ausgefallen. prepositions usually
Network is down.
require rephrasing.
en-US source de-DE target Comment
Verbs
Failed to perform (+) Fehler beim Ausführen Perform = ausführen (Do not use:
server operation. des Servervorgangs. (-) durchführen)
(+) Arbeitsspeicher-
Memory control
Kontrollblöcke wurden Destroyed = beschädigt
blocks were destroyed.
beschädigt.
Not the same device (+) Nicht das gleiche Gerät. (Do not use: (-) dasselbe).
An illegal setting
(+) Es wurde ein ungültiger
name has been Invalid, illegal = ungültig
Einstellungsname eingegeben.
entered.
Unavailable = nicht
FCB unavailable. (+) FCB ist nicht verfügbar.
verfügbar
Drive %1 is not a
(+) Das Laufwerk %1 ist kein Repeat the verb (here: ist) in
floppy disk drive or is
Diskettenlaufwerk oder ist einem order to retain the intended
mapped to a network
Netzlaufwerk zugeordnet. meaning.
drive.
Questions
Save changes to
%1? / Do you
(+) Möchten Sie die The standard form is: Möchten Sie … +
want to
Änderungen in %1 speichern? V
save changes to
%1?
Syntactic ordering
Setup encountered an
error while creating Avoid personified subjects if
your startup disk. / (+) Fehler beim Erstellen der the context allows for
Setup cannot access Startdiskette. / Kein Zugriff auf den omission (e.g. Setup
the server you chose. / gewählten Server. / Der encountered/was unable to
Setup cannot find the Remotecomputer wurde nicht ... in Setup error messages).
remote computer. / gefunden. / Der Lizenzvertrag Rephrase and change the
Setup was unable to konnte nicht angezeigt werden. / Die word order. In many cases,
display the agreement. Datenträgerinformationen können passive is possible. If the
/ Setup cannot get disk nicht abgerufen werden. / Das context does not allow for
information. / System kann nicht gestartet werden. omission of the agent,
Windows 98 cannot use vom/von der/von + N.
start your system.
Punctuation
Not available on (+) Nicht auf dieser Put a period at the end of an error message
this platform Plattform verfügbar. even if there is none in the US string.
Too many files! (+) Zu viele Dateien. Replace exclamation marks by a period.
Note that in order to display keyboard shortcuts you might need to activate this
functionality in the accessibility center (activate “Tastenkombinationen und
Zugriffstasten unterstreichen” under “Bedienung der Tastenkombinationen erleichtern”)
Usage: Is
Keyboard shortcuts special options Notes
it allowed?
Term Usage
A subtype of keyboard shortcut. A letter or number that the user types to access UI
controls that have text labels. Access keys are assigned to top-level controls so that
access the user can use the keyboard to move through the UI quickly.
key Example: F in Alt+F
Example in UI localization: H&ome
In keyboard shortcuts, most access keys are used with the Alt key.
The letter or number that appears in the ribbon when the Alt key is pressed.
In UI localization, the key tip is the last character present in the strings after the
“`” character.
Example: In UI localization Home`H
key tip
A subtype of keyboard shortcut. A key that the user types to perform a common
action without having to go through the UI. Shortcut keys are not available for
every command.
shortc
Example: Ctrl+N, Ctrl+V
ut key
In keyboard shortcuts, most shortcut keys are used with the Ctrl key.
Ctrl+letter combinations and function keys (F1 through F12) are usually the best
choices for shortcut keys.
5.6.4 Keys
In English, References to key names, like arrow keys, function keys and numeric keys,
appear in normal text (not in small caps).
In German, key names are spelled in initial caps. On the first mention, use the definite
article and "TASTE" in conjunction with the key name, for example, "die ESC-TASTE." On
all subsequent references, refer to the key only by its name, for example, "Drücken Sie
ESC." As a rule of thumb, be frugal in your use of the word TASTE.
Use it, as in the first example below, if the key name appears alone in the sentence and
the actual key name does not appear on the keyboard. In the second example, the name
ALT appears on the key of the keyboard, so you don't need to follow it with -TASTE.
Example three and four deal with a procedure involving the pressing of two or more
keys simultaneously; note that you are not using the word TASTE in this case. Also, don't
use TASTE in tables.
Examples:
• (+) Verwenden Sie die NACH-LINKS-TASTE, um das Objekt nach links zu verschieben.
• (+) Drücken Sie ALT.
• (+) Drücken Sie ALT+O.
• (+) Zum Erweitern der Markierung drücken Sie UMSCHALT+NACH-LINKS-TASTE.
Key Names
BACKSPACE RÜCK --
BREAK UNTBR --
COMMAND -- BEFEHL
NACH-UNTEN-
DOWN ARROW NACH-UNTEN-TASTE
TASTE
EINGABE
ENTER EINGABE
(Zehnertastatur)
en-US Key Name de-DE PC de-DE Macintosh
HELP -- HILFE
OPTION -- WAHL
EINGABE
RETURN (key pad) EINGABE
(Zeilenschalter)
NACH-RECHTS-
RIGHT ARROW NACH-RECHTS-TASTE
TASTE
It is recommended that you avoid distinguishing numeric keypad keys from the other
keys, unless it is required by a given application. If it is not obvious which keys need to
be pressed, provide necessary explanations.
en-US
en-US command de-DE command de-DE shortcut key
shortcut key
Anzeigen der
F1;
Context-sensitive Help Shift+F1 kontextbezogenen
UMSCHALT+F1
Hilfe
Anzeigen
Display pop-up menu Shift+F10 UMSCHALT+F10
des Kontextmenüs
Umschalten
zwischen Elementen in
Display next window Alt+Esc ALT+ESC
der Reihenfolge, in der
sie geöffnet wurden
Öffnen des
Display pop-up menu for
Alt+Spacebar Kontextmenüs für das ALT+LEER
the window
aktive Fenster
Anzeigen
Display property sheet for der Eigenschaften für
Alt+Enter ALT+EINGABE
current selection das ausgewählte
Element
Schließt das
Close active application aktive Element oder
Alt+F4 ALT+F4
window beendet das aktive
Programm
Wechseln zum
Switch to next window nächsten Fenster
Alt+F6 ALT+F6
within application innerhalb der
Anwendung
Anzeigen des
Display next child window Ctrl+F6 STRG+F6
nächsten Fensters
Vorwärtsbewegen
Display next tabbed pane Ctrl+Tab durch die STRG+TAB
Registerkarten
en-US
en-US command de-DE command de-DE shortcut key
shortcut key
File menu
Edit menu
Wiederherstellen oder
Edit Repeat Ctrl+Y STRG+Y
Wiederholen
Ctrl+Backspac
Edit Delete Letztes Wort löschen STRG-RÜCK
e
Help menu
Font format
Underlined\Word underli
Ctrl+U Unterstreichen STRG+UMSCHALT+U
ne
n/a
SIMILAR COMMAND: n/a
Small caps Ctrl+Shift+K
Groß-Kleinschreibung UMSCHALT+F3
ändern
Paragraph format
Text
Left aligned Ctrl+L STRG+L
linksbündig ausrichten
Text
Right aligned Ctrl+R rechtsbündig ausrichte STRG+R
n
5.7 Trademarks
Trademarked names and the name Microsoft Corporation remain in English unless local
laws require translation and an approved translated form of the trademark is available. A
list of Microsoft trademarks is available for your reference at the following location:
https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks
A good Microsoft voice video addresses only one intent (one customer problem), is not
too long, has high audio quality, has visuals that add to the information, and uses the
right language variant/dialect/accent in voiceover.
• 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 (Search Engine Optimization). Include search phrases in the title,
description, and headers so that people can easily find the topic.
• Talk to the customer as if (s)he is next to you, watching you explain the content.
• Record a scratch audio file. Check for length, pace and clarity.
• Try and keep translations as short as possible. For instance, avoid using semi-
colons and split your sentence in two instead. Avoid bullet points and partial
sentences, which are difficult to "read."
• Try and read translations out loud. If something sounds bad to your ear, chances
are it won't sound great in front of a microphone.
• Whenever possible and as for all types of translations, it is recommended that
you have experience with the product before translating, particularly when the
text deals with complex instructions. A good example would be interacting with
system by trying the task scenarios defined in the text.
Generally speaking, English terms and product names left unlocalized in target material
should be pronounced the English way. For instance, Microsoft must be pronounced the
English way. However, if your language has an established pronunciation for some
common term (such as "server") the local pronunciation should be used. Moreover,
pronunciation can be adapted to the German phonetic system if the original
pronunciation sounds very awkward in German.
• Accent. Always use a neutral voice. A neutral voice is a voice that cannot be
identified with a specific region or background, i.e. as Saxonian, Austrian, Swiss,
etc.
• Voice. Male and female voices may both be used without preferences.
Digest /'daɪdʒest/
/'maɪkrosoft
Microsoft Windows Numbers are pronounced in
ˌwɪndoʊz 'sə:və/
Server 2012 German, "Microsoft" in English
2012
Hardware /'hɑ:dweə/
Tool /tu:l/
Proxy /'proksɪ/
live /laɪf/
Download /'daʊnlləʊd/
Mobile /'mo:baɪl/
Acronyms are pronounced like real words, adapted to the local pronunciation:
Example Phonetics
RADIUS /'ra:dius/
RAS /ra:s/
ISA /'i:sa/
LAN /la:n/
WAN /wa:n/
WAP /wap/
MAPI /'ma:pi/
POP /pop/
COM+ /kom'plus/
OWA /o:wa/
Other abbreviations are pronounced letter by letter. They should be pronounced the
German way.
Example Phonetics Comment
CPU /tsepe'u:/
HTTP /hatete'pe/
XML /iksem'el/
HTML /hatɛem.'el/
SQL /esku.'el/
IIS /ˌaiˌai'ess/
TCP/IP /ˌti:zi:pi:'aipi:/
B2B /bi:tu'bi:/
5.8.1.2 URLs
"http://" should be left out; the rest of the URL should be read entirely.
The "dot" can safely be omitted if the target audience is advanced users. But if you are
unsure about the target audience, include the dot. If read out, then it must be
pronounced the German way, as, /puŋkt/.
Punctuation marks
Most punctuation marks are naturally implied by the sound of voice, e.g. ? ! : ; ,
Avoid unusual or too complex punctuation. For instance, avoid using semi-colons and
split your sentence in two instead.
Avoid bullet points and partial sentences, which are difficult to "read."
5.8.2 Tone
Use a tone matching the target audience, e.g. more informal, playful and inspiring tone
may be used for most Microsoft products, games etc., or formal, informative, and factual
in technical texts etc.
5.8.3.2 Title
5.8.3.5 Visuals
5.8.3.6 Ending