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

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

TL;DR¶

• Spanish (Spain) modern voice uses informal tú and second-person plural vosotros; avoid long bureaucratic phrases.
• Watch for leísmo (Spain), queísmo, and dequeísmo — common Spanish-language defects.
• Drop excessive English possessives — use definite article instead.
• Use Spain-specific vocabulary (ordenador, vídeo, ratón, coste — not computadora, video, mouse, costo).
• Reference RAE Diccionario, Diccionario panhispánico de dudas, Nueva gramática, Ortografía for normative decisions.

Register and tone for modern Spanish (Spain) translation¶

Register is the level of formality, warmth, and conversational ease the target text projects. Three principles define the modern Spanish (Spain) register for consumer-facing content:

• Warm and relaxed. Natural, less formal, more grounded in honest conversations.
• Crisp and clear. Written for scanning first, reading second. Sentences short enough to parse on a phone screen.
• Ready to help. Anticipates what the reader needs and offers it at the right moment.

The general style should be clear, friendly, and concise. Use language that resembles conversation in everyday settings as opposed to the formal, technical language often used for technical and commercial content.

Why this matters: Bureaucratic register damages outcomes across spheres. In marketing copy it kills conversion. In patient-facing medical materials it reduces comprehension and compliance. In software UI it creates friction. In consumer-facing legal documents (terms of service, privacy notices) regulators increasingly demand plain language. Only sworn legal translation (traducción jurada) and pure technical specifications retain the older formal register.

Audience targeting: technical vs. consumer vocabulary¶

Use technical terms for technical audiences; for consumers use common words. A clinical drug monograph for prescribers uses precise pharmacological terminology; the patient leaflet for the same drug uses everyday Spanish.

This applies in every sphere. Legal translation for corporate counsel uses Latinisms and procedural shorthand; consumer-facing versions need plain-Spanish framing. Medical translation for clinicians keeps Greek/Latin nomenclature; for patients it switches to common terms.

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 Spanish. Understand the whole intention of the sentence, paragraph, or page, then rewrite as if composing it for a Spanish (Spain) reader. Sometimes you need to remove unnecessary content.

Word choice: terminology and conversational vocabulary¶

Use approved terminology for key terms, technical terms, product names. Modern Spanish (Spain) voice prefers shortened forms and everyday words.

Important: Beware of shortened English words like “app” and “info” which have no shorter Spanish equivalent — use the full Spanish form regardless of source.

Synonyms¶

Use synonyms for natural, conversational tone. For example, “to wish” is almost always translated as “desear” — but in everyday speech people use “querer”. Use synonyms to deviate from what might be perceived as formal.

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

Word-to-word translation produces stiff, unnatural text. Split into shorter sentences. Omit unnecessary descriptions. Refer to source text in compiled pages to produce natural Spanish.

Words and phrases to avoid in modern Spanish (Spain)¶

Spanish should avoid long, formal constructions in favor of simpler, more direct syntax.

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.

Inclusive language¶

Microsoft technology reaches every part of the globe — communications should be inclusive. Use plain language. Be mindful of cultural references and politically disputed places. Don’t generalize or stereotype.

Avoid gender bias¶

Use gender-neutral alternatives.

For generalizations, use plural noun forms — “alumnado” (instead of “alumnos”), “personal” (trabajadores), “dirección” (directivos), “abogacía” (abogados).

Don’t use gendered pronouns (ella, él, ellas, ellos) in generic references. Instead:

• Rewrite using second person (tú).
• Use gender-neutral nouns (“abogacía” instead of “abogados”).
• Use “personas” — “personal” instead of “empleados”, “personas con interés” instead of “interesados”.
• Use broader collective references — “gente”, “personas”, “todo el mundo”.

When writing about a real person, use their preferred pronouns (él, ella, etc.).

Accessibility¶

Focus on people, not disabilities. Don’t use words that imply pity (padece de, sufre de). Prefer not to mention a disability unless relevant.

Use generic verbs that apply to all input methods. Keep paragraphs short — aim for one verb per sentence. Spell out más, aproximadamente — screen readers can misread +, -, <>, ~.

Language-specific standards¶

Abbreviations¶

• The order of letters matches the source word (art. for “artículo”).
• Don’t abbreviate by omitting only one letter — omit at least two.
• Abbreviations by dropping last syllables/letters should not end in a vowel (pról. not prólo. for “prólogo”).
• Abbreviations by contraction (omitting middle syllables/letters) can end in a vowel (pdo. for “pasado”).
• Don’t create abbreviations that coincide with an established convention for a different word.

Don’t treat words as “metro” or “litro” as abbreviations — they are symbols and should not end in a period.

Acronyms¶

Acronyms behave like nouns. Gender comes from the spelled-out form. For non-Spanish acronyms, gender varies by usage. No plural -s — number comes from the determiner. “PC” plural is “los PC” (not “PCs”). In Spain, acronym PC takes masculine from “ordenador”.

Localized acronyms¶

If widely used, use as-is. If not widely used or potentially confusing, spell out the term and include acronym in brackets on first occurrence.

Unlocalized acronyms¶

Common acronyms used without spelled-out form: ANSI, ISO, IP, USB, URL, HDMI.

If the acronym is not widely used, on first occurrence write the full name in Spanish followed by the English acronym in parentheses. If the English full name is needed, follow the pattern: Spanish name (English acronym, English full name in italics).

Adjectives¶

Spanish adjectives match the gender/number of what they modify. They can precede or follow the noun. Adjectives of nationality are NOT capitalized.

Possessive adjectives¶

Excessive possessives are an English feature — avoid in Spanish. Replace with definite article; exception is UI items (My network places → Mis sitios de red).

Articles¶

Microsoft product names and non-translated feature names are used without articles in English. Same in Spanish.

For localized feature names: when treated as a proper noun, no article. When starting with a common name (tool, wizard), include article.

Capitalization¶

Spanish capitalization differs from English. Follow normative rules.

• For software interface elements, capitalize only the first letter of the first word in commands, dialog box titles, dialog box options, menus, buttons, pane/view/window names.

• For key names, capitalization is limited to the initial letter (tecla Control); for abbreviated keys (CTRL, ALT) follow source formatting.

• In headings, captions, table/figure titles, use initial capitals only for the first word and for proper nouns/interface terms requiring it.

Accented capital letters¶

Use of accented capital letters (Á, É, Í, Ó, Ú, Ñ) is mandatory according to Spanish grammar — except where software incompatibilities prevent (e.g. programming function names).

Compounds¶

Compounds should be understandable and clear. Avoid overly long/complex compounds.

For compounds in variables/user input/programming elements, first check translatability. If not localizable, term stays unchanged. If localizable:

Conjunctions¶

Modern Spanish voice tolerates starting sentences with conjunctions (Y, O) — less commonly than English where it’s also recommended only sparingly in formal writing.

Gender (loan words)¶

When dealing with English loan words, consider:

• Motivation: Does the word have formally motivated features for Spanish noun classes?
• Analogy: Is there an equivalent Spanish term whose article could be used?
• Frequency: What article is used in technical documentation?

Always consult Microsoft Terminology to confirm article choice for loan words.

Localizing colloquialisms, idioms, and metaphors¶

Three options:

1. Don’t replace source colloquialism with Spanish unless perfect fit.
2. Translate intended meaning if integral.
3. If omittable without affecting meaning, omit.

Non-breaking spaces¶

Use non-breaking spaces (Ctrl+Shift+Spacebar) between:

• “capítulo” or “apéndice” and its corresponding number/letter.
• Unit of measure or currency and the number.
• Any items not to be divided across lines (Microsoft Office, Microsoft).

Note: NBSPs sometimes cause problems in final document generation — don’t use in online help/documentation live content.

Numbers¶

In Spanish (Spain) non-technical writing, spell out numbers of one or two words, or two words joined by “y”:

Use figures for numbers requiring more words.

In technical/scientific/business writing, figures are preferred even when spelling would be brief. Generally accepted as figures: dates, addresses, percentages, fractions, decimals, scores, statistics, pages, identification numbers, time.

In software localization, follow source usage for simplicity.

Prepositions¶

Avoid coordinating two verbs that take different prepositions when they share a common complement.

Also don’t coordinate two verbs needing different prepositions, as in “correo enviado a y recibido de”.

Queísmo and dequeísmo¶

Queísmo — omission of “de” where required. Dequeísmo — inclusion of “de” where not necessary.

Modern voice prefers simpler prepositions over extended prepositional phrases:

Pronouns¶

Use first/second-person pronouns. Avoid third-person (“user”) — sounds formal and impersonal. When the user is telling the program what to do, use the infinitive.

For Spanish (Spain), use informal second person singular pronoun “tú”.

Second person plural in Spain is “vosotros” — not “ustedes” as in Spanish Neutral / Latin America.

Leísmo¶

Leísmo (“use of le”) occurs largely in Spain — using indirect object pronoun “le” instead of masculine direct object pronoun “lo” when the direct object refers to a male person.

Punctuation¶

Punctuation marks in each Latin-based language are the same as English — exceptions are the opening ¡ and ¿ used in Spanish.

Bulleted lists¶

Bulleted lists composed of full sentences start with initial caps and end with a period:

Cuando finalice la ejecución del programa de instalación de DoubleSpace:
• Tu PC tendrá una unidad sin comprimir.
• La unidad C estará comprimida y tendrá más espacio libre.

Bulleted list elements forming part of the same sentence start lowercase with appropriate Spanish punctuation (commas or semicolons, ending period):

Estos conflictos surgen cuando:
• se deben ejecutar dos versiones de la misma aplicación al mismo tiempo,
• el departamento de finanzas migró a una versión más nueva del software de contabilidad o
• se requiere acceso a una versión antigua del software para cerrar el año fiscal.

Bulleted items that are not full sentences or continuations don’t have an ending period:

Tareas principales:
• Compatibilidad de las aplicaciones
• Virtualización del escritorio
• Seguridad y control

Dashes and hyphens¶

Hyphen — divides words between syllables, links parts of compound words, joins parts of inverted/imperative verb forms.

En dash — used as minus sign, usually with spaces.

En dash also used in number ranges (no spaces):

Em dash — only to emphasize isolated elements or introduce non-essential elements. For uses see normative references.

Ellipses¶

• Remove spaces before ellipses, even when present in source.

• Command names in menus followed by ellipses (indicating a dialog) keep the ellipses in software. In references (documentation, messages), ellipses are NOT kept.

Period¶

Do not use two spaces after a period, even if source does.

Quotation marks¶

Normative reference for Spanish: chevrons (« »). However with English source basis, curly quotes (” “) are widespread. In Microsoft Spanish documentation, use curly/smart quotes in normal text. Use term “comillas de apertura” (opening) or “comillas de cierre” (closing).

Do not use quotation marks with user input unless they’re part of the input. In technical material, specify “sencilla (‘)” or “doble (")” when the user must type them.

Parentheses¶

No space between parentheses and the text inside.

Sentence fragments¶

Sentence fragments can convey conversational tone in some cases.

Subjunctive¶

The subjunctive is an important resource in Spanish — use when content requires it. When choosing between “cantara/cantase”, Spain prefers “cantase”.

Verbs¶

Simple tenses are preferred over compound tenses. Use future tense to express future events or in conditional clauses.

Localization considerations¶

Accessibility¶

Accessibility options make computers usable by people with cognitive, hearing, physical, or visual disabilities. Some accessible products may not be available in Spanish-speaking markets.

Applications, products, and features¶

Application/product names are often trademarked and rarely translated. Feature names occasionally trademarked. When a product name contains a preposition, it is recommended to translate the preposition unless trademark/copyright says otherwise.

Feature names — wizards¶

Wizard names should follow the format: Asistente + para + noun OR Asistente + para + infinitive + object.

Version numbers¶

Version numbers contain a period:

Translation of version strings¶

Version strings with copyright info should always be translated. Refer to Microsoft Terminology for “All rights reserved” and “Microsoft Corporation”.

Copilot predefined prompts¶

Copilot prompts are functional — accuracy, consistency, conciseness, and natural tone are critical.

• Be clear and specific.
• Keep it conversational — simple, natural language.
• Be polite and professional — no slang or jargon.
• Use quotation marks — helps Copilot know what to write/modify/replace.
• Pay attention to punctuation, grammar, capitalization.
• Pay attention to entity token placement — tokens are NOT localizable. Exception: display-text prompts where dev comment instructs to translate the token.
• Be consistent.

Frequent errors and conflictive terms¶

Check and verify¶

Maintain the distinction between comprobar and verificar.

Verificar: - Check if something is true or false. - Check if a mathematical condition is met.

Comprobar (meaning): - Make sure of something (suspected or alleged). - Know something with absolute certainty.

The term “comprobar” is used as translation for “to check”.

Ignore¶

“Ignore” as ignorar is incorrect (false friend). Alternatives: omitir, pasar por alto, hacer caso omiso, prescindir.

Occurrence¶

Standard translation is repetición, caso — NOT “ocurrencia”.

• (–) Número de ocurrencias
• (+) Número de repeticiones

Trademarks¶

Trademarked names and “Microsoft Corporation” should not be localized unless local laws require translation and an approved translated form exists.

Software considerations¶

Arrow keys¶

Arrow keys move input focus within a group.

Error messages¶

Error messages inform users of an error to correct. Apply Microsoft voice principles for natural, empathetic, non-robotic translation.

Syntax and punctuation¶

English error messages may use period, semicolon, or colon as separators. Simplified to period as separator. Concise nominal phrases preferred over full sentences:

Don’t transfer exclamation marks from English:

Impersonal form preferred over excessive repetition of “tú”. When verbs in 3rd person mention an error or its cause, include the subject. If context is clear, remove the reference to the user:

Verbs ser and estar¶

Often omit “to be” without jeopardizing the message. Nominal form preferred in short sentences:

In long sentences with many participles, verbal structure preferred:

Standard phrases in error messages¶

Error messages containing placeholders¶

%d %ld %u %lu → <number>. %c → <letter>. %s → <string>.

Keyboard shortcuts¶

Terminology:

Additional notes: choose most significant letters (typically first character) for important commands. Avoid duplicate shortcuts in the same dialog. Maintain shortcut consistency throughout a product and across the product family.

Keys¶

Numeric keypad¶

Don’t distinguish numeric keypad keys from other keys unless required.

Shortcut keys¶

Voice video considerations¶

A good voice video addresses one intent, isn’t too long, has high audio quality, has informative visuals, uses the right language variant in voiceover.

Successful techniques:

• Focus on the intent.
• Show empathy.
• Use SEO — include search phrases in title, description, headers.
• Talk to the customer as if next to you.
• Record a scratch audio file — check length, pace, clarity.

Pronunciation of English terms and acronyms¶

English terms and product names should be pronounced English-way with slight Spanish accent. Microsoft pronounced English way. Pronunciation can be adapted to Spanish phonetic system if the original sounds awkward.

• Numbers pronounced in Spanish — Windows 10 → “Windows diez”.
• “r” always pronounced Spanish way (rolling r).

Acronyms pronounced as words, adapted to local pronunciation:

Other abbreviations pronounced letter by letter:

URLs¶

• “http://” left out.
• “www” pronounced “triple w” /ˈtɾipləˈub ˈdoble/.
• “dot” omitted or read as “punto”.

Punctuation marks¶

Most punctuation naturally implied by voice. En dash (–) emphasizes isolated elements — pronounced as comma (short pause).

Special characters¶

Pronounce / \ ˘ < > + - using Spanish (Spain) translations approved in Microsoft Terminology. Hyphen → “guion”; underscore → “guion bajo”.

Tone¶

Match target audience: informal/playful for products and games; formal/informative/factual for technical texts.

Video voice checklist¶

• Topic and script: single intent, clarity, everyday language, friendliness, relatable context.
• Title: include intent, include keywords for search.
• Intro 10s: put problem in relatable context.
• Action and sound: keep something happening visually/audibly with appropriate pace, synchronized visuals/voice, fine to alternate first/second person (for second person use “tú”), repetition of big points OK.
• Visuals: eye guided through procedure, smooth pointer motions, judicious callouts, motion graphics/branding visuals.
• Ending: recaps unnecessary.

Reference materials: authoritative Spanish (Spain) sources¶

Normative references:

1. Diccionario de la lengua española (Vigésima tercera edición), Real Academia Española, Madrid, Ed. Espasa, 2014.
2. Diccionario panhispánico de dudas, RAE & Asociación de Academias de la Lengua Española, Madrid, Ed. Santillana, 2005.
3. Nueva gramática de la lengua española, RAE y ASALE, Madrid, Ed. Espasa-Calpe, 2009.
4. Ortografía de la lengua española, Academias de la Lengua Española, Ed. Espasa, 2010.

Informative references:

1. Diccionario de uso del español, Moliner, M., Madrid, Ed. Gredos S.A., 1991.
2. Diccionario de informática (2.ª ed.), Oxford University Press, Ed. Díaz de Santos, 1992.
3. Diccionario comentado de terminología informática, Aguado de Cea, Ed. Paraninfo, 1996.
4. Microsoft Diccionario de Informática e Internet, McGraw-Hill Interamericana, Madrid, 2001.
5. El lenguaje de la informática e Internet y su traducción, Belda Medina, J.R., Publicaciones de la Universidad de Alicante, 2003.
6. Diccionario de Internet ATI: http://www.ati.es/novatica/glointv2.html.

FAQ¶

What’s the modern register for Spanish (Spain) translation across professional contexts?¶

Warm, conversational, scannable — uses informal tú by default in consumer-facing content. Avoid long formal constructions, replace compound verbs with simple tenses where natural. Sworn legal translation (traducción jurada), formal contracts, academic texts retain more formality and may use usted.

How does Spain Spanish differ from Latin American or neutral Spanish?¶

Second-person plural: Spain uses vosotros/vosotras + corresponding verb forms (conocéis); Latin America and neutral Spanish use ustedes (conocen). Spain has leísmo for male direct objects (Le ayudarás). Vocabulary: ordenador, coste, vídeo, ratón, archivo, marketing, móvil (vs. computadora, costo, video, mouse, archivo, mercadeo, celular).

What are queísmo and dequeísmo?¶

Queísmo: omitting ‘de’ where required (‘Asegúrate que’ instead of correct ‘Asegúrate de que’). Dequeísmo: adding ‘de’ where not needed (‘Es posible de que’ instead of correct ‘Es posible que’). Both are common errors — when in doubt, test by substituting with ‘eso’ (Asegúrate de eso → correct; Es posible eso → correct, no de).

What are the most common Spanish (Spain) translation pitfalls?¶

Excessive possessives copied from English (su, tu — drop them), formal vocabulary (sin embargo → pero; siempre y cuando → si; solicitar → pedir; volver a instalar → reinstalar), false friend ignorar for ignore (use omitir, pasar por alto, hacer caso omiso depending on context), abortar (use anular), ocurrencia for occurrence (use repetición, caso).

What punctuation rules differ from English in Spanish (Spain)?¶

Use opening ¿ ¡ at start of questions/exclamations as well as closing. Spanish prefers curly quotes “” in printed material though chevrons «» are normative; in Microsoft style follow source curly quotes. Use coma decimal (3,14) and dot for thousands (1.000). Accented capital letters (Á, É, Í, Ó, Ú, Ñ) are mandatory in Spanish.

Sources¶

• Microsoft Localization Style Guide for Spanish (Spain)
• Microsoft Globalization Style Guides hub
• Real Academia Española — Diccionario
• Real Academia Española — Diccionario panhispánico de dudas
• Diccionario de Internet ATI