Professional Documents
Culture Documents
2. Linguistic guidelines 11
Abbreviations and acronyms 11
2.1.1. Acronyms 11
2.1.2. Abbreviations 11
Numbers and measurements 13
2.2.1. Writing numbers 13
2.2.2. Units of measurement and symbols 13
2.2.3. Symbols vs ISO codes 15
2.2.4. Measurement conventions 15
2.2.5. Dates 15
2.2.6. Times 16
2.2.7. Decimal and thousand separators 16
Punctuation 17
2.3.1. Commas 17
2.3.2. Hyphens and dashes 18
2.3.2.1. Hyphen (-) 18
2.3.2.2. Em-dash () [ALT+0151] 18
2.3.2.3. En-dash () [ALT+0150] 18
2.3.3. Full stops 19
2.3.4. Trailing punctuation 19
2.3.5. Colons 19
2.3.6. Slashes 19
2.3.7. Brackets 19
Spelling 20
Capitalization 20
Lists 20
2.6.1. Bulleted and numbered lists 20
Names and addresses 21
2.7.1. Company names 22
2.7.2. Forms of address 22
2.7.3. Job titles 22
2.7.4. Place names 22
2.7.5. Addresses and phone numbers 22
Miscellaneous information 23
2.8.1. Common mistakes 23
2.8.1.1. And/Or 23
2.8.1.2. Effective 23
2.8.1.3. Multiple 23
2.8.2. False friends 23
3. Sector-specific guidelines 25
General 25
3.1.1. Register 25
3.1.2. Cultural localization 25
Legal 27
3.2.1. General 27
3.2.2. Legal references 27
3.2.3. Useful references 27
Life sciences 29
3.3.1. General 29
3.3.2. Patient-facing content 29
3.3.3. Physician-facing content 29
3.3.4. Clinical documentation 29
3.3.5. Adjudication/safety materials 30
3.3.6. Regulatory documentation 30
Software 31
3.4.1. General 31
3.4.2. Buttons/menu items and dialog boxes 31
3.4.3. Popups/status messages/error messages 32
3.4.4. Hot keys 32
3.4.5. Placeholders 32
3.4.6. Special Characters 32
3.4.7. Concatenated Strings 33
User guides/help content 34
Technical 35
Marketing/creative 36
3.7.1. General 36
Scope
The purpose of this Translation Style Guide is to establish grammar, style and terminology guidelines
for SDL internal staff and freelance translators, editors and proof-readers with regard to the language
preferences to be used in English to Spanish translations that are carried out for or by SDL
International.
It is imperative that both internal translators and freelancers adhere to these guidelines, so that all
manuals and online texts translated or reviewed for or by SDL International have consistent style, good
readability and stylistic quality. Adhering to the SDL Translation Style Guide will also ensure linguistic
consistency across a pool of translators on any one project. This will in turn ensure that no extra
resources have to be allocated during revision, helping to deliver on time within budget.
Some of SDLs clients have their own set of linguistic guidelines. Where this is the case, these guidelines
will be provided to translators, together with the project material for translation. Where there are
differences or contradictions, the clients preferences (if correct) take priority over those in this guide.
For any linguistic issues not covered in the client guidelines, the SDL Translation Style Guide is to be
referred to.
The general orthographical and grammatical rules for Spanish obviously remain untouched by the SDL
Translation Style Guide.
Ideally, the translated text should be easy to read, convey the same information as the source language
and be able to pass as a text originally written by a native speaker of the target language. The overall
style of translations should be clear and concise to help readability and literal translations should be
avoided unless instructed otherwise.
Consistency
Ensure that the translation is stylistically consistent, e.g. sentence structure in recurring text elements
such as headings, step-by-step instructions. Phrases which occur more than once in a document (e.g.
Related Topics) should be translated identically throughout the document.
Terminology should be used consistently throughout the text and also be consistent with legacy and
reference material, e.g. glossary (termbase) and translation memory.
Syntax
1.3.1.1. Gerunds
In English, gerunds tend to be used in section titles and subtitles in the documentation and help, where
Spanish prefers the nominal form or an infinitive form. The Spanish gerund can and should be used
when it appears in a status bar indicating an action in progress.
Note that the Spanish gerund denotes an action in progress, which takes place before or at the same
time as the main action. It is incorrect to use the gerund to denote an action that takes place after the
main one.
Note: Try to avoid alto introduce a means clause as Spanish equivalent to by + gerund. Instead,
you can use these examples: a travs/por medio de; mediante; gracias a; debido a; con
1.3.1.2. Imperatives
Use the imperative mode when giving instructions. Avoid using the infinitive form.
English expressions with modal verbs or constructions (such as make sure you do something) should
also be translated using the imperative mode.
1.3.1.4. Infinitive
When translating menu options, buttons and dialog boxes in software, always use the infinitive form.
1.3.1.5. Future
English manuals and guides tend to use the future tense, where in Spanish the present tense would be
more appropriate. Avoid using the future tense in such cases.
When changing subjects (e.g., as a result of using the active form where the English sentence uses the
passive form), be careful not to cause mistranslations.
Avoid using the same preposition for verbs that collocate with a different preposition.
A common mistake is deleting a required preposition to avoid what is called dequesmo in Spanish
(incorrect use of de que).
Personification
Personifications are frequently used in English documentation and should be avoided in Spanish.
Instead, it is recommended to use an impersonal form.
2.1.1. Acronyms
The translation of acronyms varies depending on the context. Please see the details below for more
information.
Acronyms have no plural in Spanish. The number agreement is determined by the preceding
determiner, article or adjective.
2.1.2. Abbreviations
In general, abbreviations should be avoided unless length restrictions mean the full term cannot be
used. If an abbreviation is required, the following rules should be taken into account.
When a syllable with more than one consonant needs to be cut, all consonants before the vowel should
be included in the abbreviation. In words with -cc-, only the first c is included in the abbreviation:
Abbreviated words are followed by a period unless the abbreviation is an established technical symbol,
such as measures or monetary symbols. If the abbreviation includes superscript letters, the period
goes before these letters:
Note: Words can also be abbreviated by contracting them, for example agte. (for agente), ca. (for
compaa), etc.
Exceptions: Superscript numbers and symbols (math exponents or angle measurements), registered
or trademarks, and degrees symbols, which should have no space between the number and the
corresponding symbol.
When the degrees appear together with the Celsius symbol, this must be handled as any other symbol
(i.e. figure+ non-breaking space+C symbol): 37 C.
Note: Percentage used to fall in this exception category but this changed since new orthographical
amendments by RAE in 2010. Now this is considered as any other symbol (figure and symbol must have
a non-breaking space in-between) but, given traditional approach is still in use, we recommend to
progressively adapt it (having it agreed previously with client and reviewers) until this rule is
completely implemented.
Currency symbols should be placed after the number and are separated by a space. Use a non-breaking
space:
When writing currencies, the RAE allows the currency symbol or ISO code, but these must go before
the figure separated with a space for LatAm countries. The symbol or ISO code only goes after in in
Spain.
English Spanish
12 lbs 5,4 kg (12 libras)
2.2.5. Dates
Note: In letters and documents, years are expressed without article (Quito, 9 de abril de 2007)
However, it is not considered incorrect to write the article (Quito, 9 de abril del 2007). In general texts,
where the year 2000 or subsequent years appear, it is common to use the article before the year (Este
documento fue revisado en febrero del 2002), but it is not incorrect to use it without the article (Este
documento fue revisado en febrero de 2002).
2.2.6. Times
Time format is preferential, so follow the client readme when deciding whether to use the 12-hour or
24-hour clock and whether to use a full stop or colon between the hours and minutes.
In general:
Use the 24-hour format and use a colon to separate hours, minutes and seconds
"am" and "pm" should be written in lower case with full stops and a space between the number
and each letter, e.g. 8 a. m. or 8 p. m.
Use a non-breaking space as a thousand separator for numbers with more than 4 figures.
Note 1: Some countries follow the English style (commas for thousands and periods for decimals).
However, the Spanish standard notation should be used unless otherwise instructed.
Note 3: In Mexico and some Central American countries, the English format is followed.
Punctuation
2.3.1. Commas
Commas are used to separate series of three or more elements. In Spanish, the comma before the
conjunction should not be used when the conjunction joins the last two elements in a series.
When a conjunction joins two parts of an element in a series and this element is followed by a second
conjunction, a comma must be used before the last conjunction.
Use commas with introductory phrases, and before and after phrases that use adverbs such as no
obstante, sin embargo, as pues, por el contrario, por lo tanto, etc.
2.3.5. Colons
Use colons to introduce lists and procedures. Do not use colons to introduce tables, sections or
illustrations. Unless the sentence starts on the next line, use lower case after the colon.
However, after notes, warnings and notices, upper case must be used (refer to http://lema.rae.es/dpd/
> Maysculas > 3.3).
2.3.6. Slashes
Slashes can be used to separate two alternatives.
If maintained in the translation, no space should be inserted between slash and the different terms
(LED rojo/verde/amarillo).
However, in Spanish, slashes are not so common and tend to be replaced by the conjunction o
2.3.7. Brackets
Use round (xxx) brackets.
If brackets are required within curly brackets, use square [xxx] brackets.
For information relating to the position of punctuation with brackets, see the section "Trailing
punctuation".
Spelling
Amendments by RAE about rules for written accents:
- When acting as an adjective or an adverb, the word solo does not take written accent
anymore.
- Also demonstrative pronouns (este, esta, estos, estas, ese, esa, esos, esas, aquel, aquella,
aquellos, aquellas) do not take written accent, even in the case of ambiguity.
- This monosyllable words that used to take written accent are no longer accented guion,
Sion, ion, prion, truhan, frio, friais, lie, lio, liais, hui, huis (and not *guin, *Sin, *in, *prin,
*truhn, *fri, *friis, *li, *li, *liis, *hu, *hus).
- The conjunction or between figures is never written with an accent, for example: 4 o 5/79 u
80.
Capitalization
In Spanish, capitals are only used for the first word of a sentence, caption, heading and title, and for
proper nouns.
The first letter of the following software interface elements should also be capitalized: commands,
dialog box titles, options, buttons and menu names (unless otherwise stated).
Lists
Note: As in the example above, the English text may not be consistent in punctuation or sentence
structure. These inconsistencies should not be replicated in the Spanish text.
English Spanish
Mr/Mr. Sr.
Mrs/Mrs. Sra., Sr., S.
Ms/Ms. Srta.
Miss Srta.
Dr/Dr. Dr. / Dra., Dr.
Example:
Marc Leblanc, gerente de [Transformation/Transformacin] (department depends on client)
Martyna ocupa el cargo de gerente de Compensacin y beneficios desde 2007
Pedro Martnez, director general, confirm los resultados
If necessary, add information in running text such as the city/country to provide additional context for
readers.
2.8.1.1. And/Or
This is sometimes translated as y/o when in Spanish o would be enough.
2.8.1.2. Effective
It should be translated as eficaz (inanimate objects) or eficiente (animate objects), but not
efectivo.
2.8.1.3. Multiple
This tends to be translated as mltiple(s): This translation is correct but should not be favoured over
other Spanish adjectives, such as varios, diversos, etc. If possible, avoid using mltiple(s).
3.1.1. Register
As a general rule, the register should be kept formal. English texts tend to lapse into quite a colloquial
style that should be avoided in Spanish
Similarly, the use of the second person singular to address the reader should be avoided in Spanish.
Instead, the third person singular should be used, but the pronoun usted should not be used
explicitly. If the sentence structure requires the inclusion of this word, it should be replaced by el
usuario or a similar phrase adequate in the context.
Notes
There are some texts where the use of the second person singular might be desired, for instance,
computer games, where the target audience age and more informal stylistic approach seem to call
for the use of the t form. Also in marketing and training guides.
Do be consistent in the way you address the reader.
If not indicated in the handoff email, always check with account lead or project manager what
person should be used to address the reader in each particular project.
3.2.1. General
Accuracy takes priority over style. In particular, carefully consider the word order and the position
of each element in the sentence to ensure accuracy and avoid ambiguity
That being said, translators also need to ensure that the style and tone are appropriate for the
context and target audience. Normally a formal tone is applied to this type of texts. Also the use
of usted to refer to the user is generally preferred
The exception to this rule is patents, for which no creative licence is permitted. The translation
must be as literal as possible otherwise it leaves the document open to dispute. Consider the legal
system for the target language country; advise the client/project manager of any potential issues
from a localisation perspective, i.e. if legal information is not applicable in the target country
3.3.1. General
It is particularly important to consider the target audience and adapt the style and register of the
translation accordingly. If it is unclear who the target audience is, ask the workgiver
As a general rule, the register should be formal and the overall style should be clear and concise
to aid readability
Consider whether standard translation or back translation is required and tailor the approach and
style accordingly. Back translations should be as literal as possible in order to assess the accuracy
of the forward translation
Use the relevant medical terminology for the country as per local laws. MedDRA terminology
database can be checked as reference
Check dosages and drug names thoroughly. This is imperative as incorrectly replicated dosages or
incorrect drug names could have serious consequences
In particular, consider:
- Consistency with legacy material: Has the software already been translated? Does the
translation need to be consistent with other content?
- Length restrictions
3.4.1. General
Ensure the style is as clear and precise as possible
Keep the translation short and simple without resulting in loss of meaning. Abbreviate where
necessary, but avoid using non-standard abbreviations
Adjust capitalization to target language standards
Consistency is extremely important: check reference and legacy material carefully when
translating elements such as user interface (UI) strings (text in the software that the user sees) to
ensure global consistency
Avoid using exclamation marks or any special character not present in the source string. If they
need to be used, first ask the client if they can be used or if they need to be escaped
Where possible, use positive constructions rather than negative ones to improve the readability
Avoid possessive adjectives
Incorrect Correct
Do not turn the switch on before connecting the Connect the power cable before turning the
power cable switch on
Launch your application Launch the application
3.4.5. Placeholders
Placeholders are replaced with any values (number or text) assigned by the code at run time. Be careful
handling them. Also check with the client prior to start translation whether they can be moved around
in the target sentence
Example:
Source code: %1 is inactive. To activate %1, click <b>Activate</b>.
At run time: Product Name is inactive. To activate Product Name, click Activate.
Example: GetConfigurationSoftware
Incorrect Correct
Do not turn the switch on before connecting the Connect the power cable before turning the
power cable switch on
3.7.1. General
- Literal translations are not usually necessary. It is more important to convey the intended
meaningtranslate the concept, not the words. This is especially the case for high-profile content
such as slogans and tag lines
- Take the time to understand the purpose of the source and its message:
- How will the text be used?
- Who is the target audience?
- What does the client want to say?
- How do they want their company/the product to be portrayed?
3.7.3. Wordplay
- As it is unlikely that a play on words in the source text, such as alliteration, puns, wordplay and
text that directly interacts with an image, can be replicated entirely in the translation, establish
the client's priorities and translate accordingly
- Where possible, offer a range of options based on different approaches
3.7.4. Transcreation
- For transcreation projects, the above guidelines apply. However, there should be particular
emphasis on rendering the concept as naturally as possible into the target language
- Consider whether it is necessary to provide the client with a range of options for high-profile
elements such as slogans and taglines
- Where possible, use another translator as a sounding board and discuss potential translations
3.7.5. Scripts
- The above guidelines apply too, but the "write as you speak" approach is particularly important
for script projects
- The target text should be easy to pronounce. Reading the text aloud might help to find stumbling
blocks. Listen to yourself saying the words and check whether you would actually say something
like that in a real conversation
3.8.1. General
- Consider the intended use and target audience of the document and adapt the style and register
of the translation accordingly. If it is unclear who the target audience is, ask the work giver. For
example, the style for a regular retail banking customer is very different to the style of content for
High Net Worth individuals
- Consider whether standard translation or transcreation is appropriate (see content types below)
- Do not phrase anything as financial advice or a recommendation unless the document explicitly
requests it. There are strict regulatory guidelines around providing financial advice with severe
financial penalties
3.8.2. Insurance
- Insurance documentation is likely to call on broader specialisms related to the context. Ensure that
the terminology for this content is adequately researched and is appropriate for the target
audience
- Documents will generally need to be written in an informative, matter-of-fact tone
- Communications Content & Annual Reports
- Ensure the tone of the translation reflects the tone of the source text
- Annual reports are the result of a combined authoring effort. Consider the different sections of
the report and the different styles required
- Do not make presumptions and avoid any ambiguity. Raise queries where necessary
- Familiarise yourself with the regional regulations for the country where the annual report is being
filed
Terminology lists may be provided by the client or created by SDL. Either way, it is essential to follow
them when translating the software and other project components.
The first step in terminology development is extracting the source English terms. This will usually be
the job of a terminologist, but if translators are asked to create a term list, they should follow these
guidelines:
- The term list should include technical terms, product-specific terms and product names.
- General terms should also be included if they have more than one translation or meaning
depending on the subject matter or if they are used repeatedly throughout the source text.
- Software options (i.e. menus, buttons, etc.) should not be included in terminology lists.
- Terms should be entered in the terminology list in the singular form and in lower case (unless
they are product names, proper nouns, etc.).
- In the case of verbs, they should be entered in the infinitive form followed by comma and then
to (e.g. backup, to).
Once the English terminology list is created and approved by the client, it needs to be translated. To
do this, client glossaries (if available) should be referred to, together with operating environment
glossaries and glossaries from previous relevant projects.