€¦ · web viewstyle guide for latin american spanish. produced by vmware, inc. revision history....

STYLE GUIDE FOR LATIN AMERICAN SPANISH

Produced by VMware, Inc.

Revision HistoryDate Revision Revised By Approved By Description of changesJune 2008

1 Translation vendor America Perez

General Style Guide update

April 2009

2 Gabriela Abraham Marlen Bernardez


June 2010

3 Gabriela Abraham/Translation vendor

Maria Clara Macedo


July 2011 4 Gabriela Abraham Maria Clara Macedo


October 2011

5 Gabriela Abraham MariaClaraMacedo

Update to the translation of: Slogans, Product and Brand Names, Services, Functionalities, Solutions, Product features, and Events

January 2012

6 Gabriela Abraham Maria Clara Macedo

Update to the section on how to deal with currencies and numbers.

April 2012

7 Gabriela Abraham Maria Clara Macedo/Silvia Pavoni

Update on supportive themes, prices (VMware reviewers only), references to documents, time zones.

June 2012

8 Gabriela Abraham Silvia Pavoni Update on slogans, partner programs, and product names.

August 2012


Update on how to deal with prices, and the translation of VMware’s VPN.

November 2012


Update on the translation of slogans and dealing with amounts and prices in USD. Updated list of approved product names. New section on pronunciation guidelines for the recording of scripts.

Contents1 INTRODUCTION................................................................................................................................1

1.1 Purpose........................................................................................................................................11.2 Principles of Localization...........................................................................................................11.3 General Instructions....................................................................................................................1

2 GENERAL ISSUES.............................................................................................................................22.1 General Rule...............................................................................................................................22.2 Addressing the Reader................................................................................................................2

2.2.1 Audience and General Style....................................................................................................22.2.2 Voice & Mood........................................................................................................................22.2.3 Marketing e-mail campaigns...................................................................................................2

2.3 Terminology & Usage.................................................................................................................32.3.1 General Rule...........................................................................................................................32.3.2 Slogans, Product and Brand Names, Services, Functionalities, Solutions, Product features, Partner Programs and Events...............................................................................................................3

2.4 References to URLs and Addresses............................................................................................72.5 References to other documents...................................................................................................82.6 Abbreviations & Acronyms........................................................................................................82.7 Numbers, Weights & Measures..................................................................................................82.8 Names of countries.....................................................................................................................9

3 GRAMMAR & STYLE.....................................................................................................................103.1 General Instructions..................................................................................................................103.2 Orthography..............................................................................................................................103.3 Wording & Phrasing Options....................................................................................................10

3.3.1 Nouns or infinitives for titles and descriptions.....................................................................103.3.2 Infinitive for Web actions......................................................................................................113.3.3 Latinisms...............................................................................................................................113.3.4 Preferences...........................................................................................................................12

3.4 Syntax Conventions..................................................................................................................123.5 User Interface Elements............................................................................................................12

3.5.1 Third party UI elements........................................................................................................134 FORMATTING CONVENTIONS....................................................................................................14

4.1 Paragraph Formats....................................................................................................................144.2 Number Formats.......................................................................................................................14

4.2.1 Ranges...................................................................................................................................144.2.2 Currencies.............................................................................................................................144.2.3 Prices Updated!.................................................................................................................154.2.4 Decimal & Thousands Separators.........................................................................................164.2.5 Dates.....................................................................................................................................174.2.6 Time......................................................................................................................................174.2.7 Phone Numbers.....................................................................................................................17

5 LEGAL & OTHER DOCUMENTS..................................................................................................185.1 Legal Language.........................................................................................................................185.2 Copyright Information..............................................................................................................185.3 Item Numbers............................................................................................................................185.4 Part Numbers............................................................................................................................195.5 Contracts...................................................................................................................................195.6 Non-Disclosure Agreements and Confidentiality Information.................................................19

6 Punctuation & Spacing.......................................................................................................................216.1 Spacing Between Sentences......................................................................................................216.2 Spacing Between Lines, Paragraphs & Sections......................................................................216.3 Superscript Reference Numbers...............................................................................................216.4 Non-Breaking Elements............................................................................................................21

6.4.1 Phrases, Numbers and Units.................................................................................................216.4.2 Bulleted Paragraphs..............................................................................................................21

6.5 Other Considerations – Punctuation.........................................................................................216.5.1 Quotation Marks...................................................................................................................216.5.2 Apostrophes..........................................................................................................................216.5.3 Dashes, Hyphens, and Slashes..............................................................................................226.5.4 Square Brackets....................................................................................................................22

7 DTP Considerations...........................................................................................................................237.1 Fonts..........................................................................................................................................237.2 Typefaces..................................................................................................................................23

7.2.1 Italic......................................................................................................................................237.2.2 Bold.......................................................................................................................................237.2.3 Underline...............................................................................................................................237.2.4 Other.....................................................................................................................................24

8 Pronunciation guidelines for voice talents.........................................................................................258.1 General rules.............................................................................................................................258.2 Procedure..................................................................................................................................258.3 Specific guidelines....................................................................................................................268.4 Frequently occurring items.......................................................................................................26

9 Local Considerations..........................................................................................................................3410 Appendix 1 Updated!................................................................................................................35

1 INTRODUCTION

1.1 PurposeThe present document is a guide to style and usage for VMware translations. The guide includes instructions for how to work with specific content. It is also intended to establish guidelines for localizers, proofreaders and reviewers in relation to some of the most common topics that arise during the translation of VMware documents.

Adherence to this Style Guide is of utmost importance in order to maintain stylistic quality and linguistic consistency across a team of localizers and reviewers working on the same project. It also tries to eliminate errors before translations arrive for quality-assurance checking (QA).

1.2 Principles of LocalizationLocalization means adapting something to a specific market and culture. Translation – like converting weights and measures, or adapting names, etc. – is only a part of the process.

Localization is, mainly, understanding how the style and tone appropriate in the target market may differ from that of the source, and reflecting the difference in the finished work. However, there are some constraints.

Computer-Aided Translation (CAT) tools place certain restrictions on free-style translation. For example, wholesale restructuring of paragraphs or changing the number or order of sentences from source to target negatively affects the efficiency of translation memory systems. There can also be line-count, character-length or time-length restrictions.

1.3 General InstructionsAs a general rule – except for technical material such as white papers and technical manuals – don’t translate. Render the source as freely, accurately, and consistently as possible. Maintain the message, humor and flavor of the original English. Approximate the English in length to better ensure fit.

Parts of VMware’s material are intended for printed documentation, while others are for use on Web pages and in presentations. All of the material is authored to market and sell VMware products. It is essential that the work you produce meet this need.

Specific VMware terminology is localized to take into consideration market specifics: products, operational practices, local advertising and branding elements, etc. The Glossary and the Style Guide reflect the most relevant terms, product names, brand names, tools and Web elements. Use approved terms to help ensure consistency and uniformity among the various parts of every project, as well as from one project to the next.

If a linguistic issue should arise, send a query to the project coordinator, manager or VMware reviewer. It is very important that you resolve all linguistic issues before delivery.

document.doc Page 1 of 39

2 GENERAL ISSUES

2.1 General RuleUnless your immediate client contact or we instruct you otherwise in writing, the rules and conventions of Latin American Spanish as found in the Real Academia Española (www.rae.es) govern VMware translations. Please advise the project coordinator or manager if any instruction not marked as an authorized exception contradicts current language standards or when you receive specific instructions from a VMware contact.

2.2 Addressing the Reader

2.2.1 Audience and General StyleWhen an English text speaks directly to the reader (i.e., “you”), use the direct, formal form of address: usted. The audiences targeted of VMware general contents are IT professionals, senior management and decision-makers from Customer, partner and VMware organizations, therefore a formal and marketing tone, considering the correct attribution of the actual features of products and/or services.

Sentences will be grammatically correct, avoiding jargon language and localisms due to the global reach of VMware. Therefore, apply linguistic criteria which are both neutral and global.

2.2.2 Voice & MoodIn general, render the Spanish in the active voice and indicative mood.

2.2.3 Marketing e-mail campaigns

Please avoid gender references in the translation of e-mails since they are directly to both men and women. Instead, try addressing the reader in an impersonal form or in plural when necessary.Example:

Sorry we missed you at VMworld.Correct target: Sentimos que no haya podido asistir a VMworld.Wrong target: Lo echamos de menos en VMworld.

We would like to invite you to VMware Virtualization Forum.Correct target: Nos gustaría contar con su presencia en VMware Virtualization Forum.Incorrect target: Nos gustaría invitarlo a VMware Virtualization Forum.

Welcome to SolutionTrack OnlineCorrect target: Bienvenidos a SolutionTrack OnlineWrong target: Bienvenido a SolutionTrack Online

As a request from VMware Marketing, please mind the following exception to Spanish capitalization rules: capitalize all verbs and nouns in e-mail’s subject lines. Example:

Email Subject Line: Academic Specialization Enrollment is Now OpenCorrect target: Email Subject Line: Ya Están Abiertas las Inscripciones para la Especialización Académica. Wrong target: Email Subject Line: Ya están abiertas las inscripciones para la especialización académica.


2.3 Terminology & Usage

2.3.1 General RuleVMware translations will comply with the solutions contained in the approved glossary and/or supplemental lists and instructions received from an authorized client contact.

Use approved terms to help ensure consistency and uniformity among the various parts of every project. Be consistent when referring to terms and concepts. If two items can be confused as the same thing, make a distinction between them.If you do not find an English term or phrase in the glossary or references, send a query.

2.3.2 Slogans, Product and Brand Names, Services, Functionalities, Solutions, Product features, Partner Programs and Events.

2.3.2.1 Product and Brand NamesUse VMware’s approved equivalent when the material references a VMware product, brand or feature by name. Make sure you follow the list in Appendix 1. While the names and brands in the list contain Trade Mark (™) and Copyright (©) symbols, it’s not necessary to add them to the localized material every time. It suffices to follow the source’s display. This goes also for the short forms of products (HA, DRS, etc.).

Formerly it was advised not to leave short forms of products names composed by 2 letters or less by themselves and add “VMware”. This is not the case anymore, the source’s display has to be reproduced. It may be the case that the source has not been updated to follow the new product line, in that case, the list in the Appendix must prevail.

Some product names are accompanied by designations specific to their purposes (for example: “vSphere 5 Standard Acceleration Kit with Smart Operations Management”). The whole block is treated like a product name and is left in English including the preposition.

Formerly, VMware services, presentations, and features were translated but now they must remain in English. Including nouns like: Kit, Suite, Edition, etc. Functionalities that are exclusive to VMware’s products or correspond to VMware’s technology (like Offline Desktop, Linked Clones, vRAM, Hot Add, NIC Teaming, Host Profiles, etc.) should all be left in English in italics but with a translation between brackets for the first instance. If the first instance is a slide title, document title, image, etc., the translation will apply to the first instance of text body. General IT concepts, even when closely related to VMware’s technology, still need to be translated (for example, “disaster recovery”, “high availability”, etc.)

2.3.2.2 Events and Partner Programs

As a general rule all event names remain in English, including, but not limited to, VMware Solution Track, VMware Solution Track On-line, VMworld, VMware Partner Forum.

The names of partner programs and all instances of VMware Partner Network should be left in English with a translation between brackets in the first instance of a document (titles should not be considered a first instance).


2.3.2.3 Slogans Updated!Some slogans and corporate themes are translated and some aren’t depending on the instructions you receive from your VMware contact.

Formerly, the corporate theme that came into effect in 2011 was left in English, but we have now been instructed to translate it, along with a few new slogans and catch phrases. It’s very important to keep consistency in the localization of slogans. Make sure to place a query whenever you are unsure if a certain phrase is a slogan, if you’re unsure whether it should be localized, or if you find inconsistencies in the TM or other reference material. Please find the approved slogan translations below:

Pioneering the New Frontier in IT Creamos nuevas fronteras para TI.

Paving the Way to Cloud Computing

Allanamos el camino hacia la computación en nube.

Your Cloud. Accelerate IT. Accelerate Your Business.

Su propia nube. Acelere TI. Acelere su negocio.

Intelligent Virtual Infrastructure. Delivered Your Way.

Infraestructura virtual inteligente. Adaptable a su medida.

Modernize Today’s Apps. Build for Tomorrow’s.

Modernice las aplicaciones de hoy. Prepárese para las de mañana.

End user freedom. IT control. Libertad para el usuario final. Control para TI.

The Journey to Your Cloud. El camino hacia su propia nube.

It All Comes Down to Business Results.

Lo único que importa es el negocio.

Leadership. Innovation. Experience Liderazgo. Innovación. Experiencia.

Cloud done right La solución ideal para la nube

Transform the possibilities Transforme las posibilidades

Your Cloud. Your Desktop. Just Got Better

Su propia nube. Su escritorio. Acaban de mejorar.

Make sure to use “Su propia nube” to translate “Your Cloud” when necessary and avoid “Su nube”.

All instance of the campaign “If only” should be translated as “Ojalá”, please avoid the translation “Si tan solo”.


Example:

IF ONLY virtualization was more affordableCorrect target: Ojalá la virtualización fuese más asequibleIncorrect target: Si tan solo la virtualización fuese más asequible

The following slogans should remain in English:Transform the possibilitiesYour Cloud. Your Desktop. Just Got Better.

VMware will assist if an item is not captured in the glossary or if there is no local equivalent of a certain product. Send a query if you encounter any such key term.

Examples:

Source Correct Incorrect Category Comments

VMware High Availability

VMware vSphere High Availability

Alta Disponibilidad de VMware /VMware High Availability/VMware HA

Former product name

Names remain in English, following the list in the Appendix.

Impress the customer with HA and DRS, and then close the sale.

Impresionar al cliente con HA y DRS, y luego cerrar la venta.

Impresionar al cliente con VMware HA y VMware DRS, y luego cerrar la venta.

Product name abbreviation

The source must be reproduced, it’s not necessary to add “VMware” or “vSphere”.

However, the DR and HA benefits of the technology are increasingly being built into virtualization’s value proposition.

Sin embargo, cada vez más, los beneficios recuperación ante desastres y de alta disponibilidad de la tecnología forman parte de la propuesta de valor de la virtualización.

Sin embargo, cada vez más, los beneficios de DR y HA de la tecnología forman parte de la propuesta de valor de la virtualización.

General IT concepts

These acronyms do not refer to a product name and aren’t exclusive to VMware. As general IT concepts they need to be translated.

Linked Clones can be refreshed at the administrator’s discretion, without affecting user data or settings.

El administrador puede actualizar los Linked Clones (clones vinculados) a discreción, sin que esto afecte la configuración ni los datos del usuario.

El administrador puede actualizar los clones vinculados a discreción, sin que esto afecte la configuración ni los datos del usuario

VMware’s functionality

Use italics for all terms left in English and add a translation between brackets for the first instance in


a document.

A key offering to focus on with all VMware Lab Manager sales is the VMware Lab Manager JumpStart.

Una oferta fundamental a tener en cuenta a la hora de vender VMware vCenter Lab Manager es el VMware Lab Manager JumpStart (taller de inicio inmediato Lab Manager)

Una oferta fundamental a tener en cuenta a la hora de vender VMware vCenter Lab Manager es el taller de inicio inmediato de VMware vCenter Lab Manager.

Service All services should be left in English with a translation in between brackets if it’s the first instance.

Virtualized by VMware

Virtualized by VMware

Virtualizado por VMware

Slogan This is the slogan found on a sticker and must remain in English.

Business Continuity Solutions

Soluciones de continuidad del negocio

Soluciones de Business Continuity

Solutions’ name

All solutions names have to be translated.

The Foundation Acceleration Kit provides the most cost-effective solution for customers looking to get started with virtualization and only want simple server consolidation.

El Foundation Acceleration Kit proporciona la solución más rentable para los clientes que desean comenzar a utilizar la virtualización y sólo buscan una simple consolidación de servidores.

El kit de aceleración Foundation proporciona la solución más rentable para los clientes que desean comenzar a utilizar la virtualización y sólo buscan una simple consolidación de servidores.

Product presentation

We will no longer translate the presentations of products. All terms like Edition, Suite, Kit, etc. must remain in English. (Except when they’re a part of speech and not accompanied by the product name.)

VMware Workstation is included with VMware ThinApp Suite.

VMware Workstation está incluido en VMware ThinApp Suite.

VMware Workstation está incluido en la serie de VMware ThinApp.

Product presentation

We will no longer translate the presentations of products. All terms like Edition, Suite, Kit, etc. must remain in


English. (Except when they’re a part of speech and not accompanied by the product name.)

VMware Virtualization Forum 2010

VMware Virtualization Forum 2010

Foro de virtualización de VMware 2010

Event name Please leave in English the names of events like SolutionTrack, Virtualization Forum, VMworld, etc.

vSphere 5 Standard Acceleration Kit with Smart Operations Management

vSphere 5 Standard Acceleration Kit with Smart Operations Management

vSphere 5 Standard Acceleration Kit con Smart Operations Management/Kit de aceleración de vSphere 5 estándar con administración inteligente de operaciones/vSphere 5 Standard Acceleration Kit con administración inteligente de operaciones

Product name and features

Leave the whole segment in English, including the preposition.

The VMware Purchasing Program (VPP) can be combined with advantage+.

El VMware Purchasing Program (VPP) se puede combiner con advantage+.

If it’s a first instance (except titles):

“El programa de compras de VMware, VMware Purchasing Program (VPP), se puede combinar con advantage+.

Programa de compras de VMware

Partner Program

Leave Partner program names in English, and add a translation on the first instance, either between brackets or integrated in the context.


2.4 References to URLs and AddressesVMware addresses are boilerplate and must be left in English, as shown below. The standard formulation for the United States is as follows. Note that the entire string appears on one line in publication:

VMware, Inc. 3145 Porter Drive Palo Alto CA 94304 USA Tel. 650-475-5000

Fax 650-475-5001

Do not break a URL.

The official company name is VMware or VMware, Inc. but not VMware Global or VMware International.

2.5 References to other documents Often in VMware’s marketing material, you’ll find references to the source from where data was take: titles of case studies, whitepapers, articles, etc. There are Resources sections in web materials that contain links to whitepapers, articles, case studies and other materials that the reader should consult to get further information on a product or service. These documents may or may not be localized into LatAm Spanish, so whenever one of these references appears, please proceed as follows:

If the document’s name appears in a title or in a space constricted section, leave it as is (in English).

If document’s name appears within a paragraph and/or resource’s page, and there are no space constraints, leave the title in English and add a translation in between brackes.

Example:This information comes from CIO: Top 10 ways to Modernize the Desktop.Target: Esta información proviene del documento CIO: Top 10 ways to Modernize the Desktop (CIO: 10 razones para modernizar el escritorio)

2.6 Abbreviations & Acronyms Abbreviations and acronyms that ordinarily appear in standard written Latin American Spanish may be used.

Technical or proprietary abbreviations, contractions, and acronyms should be either avoided or explained. In order to make sure that the user understands the acronyms references, the translator should spell out the unusual acronym on its first reference, followed by the acronym and English text in parentheses and italics, i.e. Máquina virtual (VM, Virtual Machine). In long documents, the term spelt out might be repeated at the beginning of each new section. Refer to the Glossary for localized equivalents (if any) of VMware acronyms.

All abbreviations should follow RAE’s rules for Spanish. Take into account that some common abbreviations in English are considered symbols in Spanish and should not be followed by a full stop, for instance: kg, l, cm, etc.

If RAE suggests two different options, please submit a query. For instance, VMware prefers “E.E. U.U.” to “E.U.A.” for “United States.


2.7 Numbers, Weights & Measures Localize the format of numbers, weights and measures. Convert all values from U.S. customary into metric. Bear in mind that some values, for instance, expressing the screen size, are usually in inches both in English and Spanish and they should not be converted.

Also, make sure to do an approximate conversion whenever an accurate conversion is not necessary, and feel free to calculate proportions to adjust the reference.

Example:

Source Correct Incorrect Comments

For most providers, a rack takes up 25 square feet of datacenter floor space.

Para la mayoría de proveedores, un rack ocupa aproximadamente 2,5 metros cuadrados del espacio destinado al centro de datos.

Para la mayoría de proveedores, un rack ocupa aproximadamente 2,32 metros cuadrados del espacio destinado al centro de datos.

Since this is not a scientific fact it’s not necessary to have exact conversion decimals but an approximate measure to provide the reader with an accurate idea. Make sure to always add “aproximadamente”.

The largest data center developers spend about $1,000 per square foot on their facilities.

Los desarrolladores de centros de datos más importantes invierten aproximadamente 11 000 USD por metro cuadrado en sus instalaciones.

Los desarrolladores de centros de datos más importantes invierten aproximadamente 1 000 USD por 0, 092 metros cuadrados en sus instalaciones.

Since the reference in English is a whole unit, it would be lost in Spanish if the exact conversion is applied. The best approach is to calculate the proportion based on the unit in Spanish.

Please use the English for measuring units which derive from proper names whenever RAE accepts both the English and the translation like: watts, gigahertz, joules vs. vatios, gigahercios and julios.

Do not convert currencies; refer to the section dedicated to this topic for more information. Also see sections on decimal and thousand separators and non-breaking spaces for further details on number conventions.

2.8 Names of countries

Please use RAE’s (Diccionario Panhispánico de Dudas) list of countries and capitals when translating the names of countries. You can find this list at http://buscon.rae.es/dpdI.Click Apéndices in the header menu, you’ll be redirected to the list then click Apéndice 5: Lista de países y capitales, con sus gentilicios.See screenshot below:


http://buscon.rae.es/dpdI

3 GRAMMAR & STYLE

3.1 General Instructions The localized English must be clear and precise, and read well. Avoid literalness at all cost, feel free to adapt, rephrase and/or interpret phrases to better express the original’s meaning. Make sure to adapt idiomatic expressions, use metaphors that work in Spanish and, in general, make all efforts to make the target text as naturally expressed in Spanish as possible. Since most material is marketing related, make sure to grasp the full meaning of phrases before rendering them in Spanish and do not translate word for word.

Be aware of Computer-Aided Translation (CAT) tools being used. There are certain restrictions to free translations, such as restructuring whole paragraphs or changing the number and order of sentences from source to target.

Footer and header must be translated, print preview document in order to discover hidden text in normal mode.

3.2 Orthography For all orthographic related matters (spelling, capitalization, punctuation, etc.), refer to the Real Academia Española. In 2010, RAE issued new rules for the Spanish orthography. The highlights can be found here.

Please make sure you follow the new rules.

Bear into account that some of the new rules are not in RAE’s website yet, but they also have to be followed. For instance, make sure to separate symbols from numbers with a hard space, even in the case of the percentage symbol, like this:

Example:

Did you know that virtualization can transform desktop and application management to help decrease operational costs by up to 50%? Correct target: ¿Sabía que la virtualización puede transformar la administración de aplicaciones y del escritorio de manera tal que se reduzcan los costos operacionales hasta en un 50 %?Incorrect target: ¿Sabía que la virtualización puede transformar la administración de aplicaciones y del escritorio de manera tal que se reduzcan los costos operacionales hasta en un 50%?

Diccionario panhispánico de dudas contains many of the new revised grammar topics and spelling that will be later included in the Spanish Grammar from the RAE.

Mind the following Spanish rules:

Use colons instead of hyphens

For ordinal numbers use 4.° instead of 4° or 4to.

Please, make sure you consult this reference when in doubt.

3.3 Wording & Phrasing Options

3.3.1 Nouns or infinitives for titles and descriptionsAvoid gerunds in titles, product descriptions, product benefits, etc. Use a noun whenever possible or the infinitive form if necessary, but always be consistent within sections.document.doc Page 11 of 39

http://www.rae.es/rae/gestores/gespub000018.nsf/(voAnexos)/arch8100821B76809110C12571B80038BA4A/$File/CuestionesparaelFAQdeconsultas.htm#ap0

Example:


Virtualizing the datacenter

Virtualización del centro de datos

Virtualizando el centro de datos

A noun is preferred in this case. Bear in mind that if there are similar cases throughout the document it is better to be consistent and use only nouns, alternating between nouns and infinitives is not recommended.

Winning a proposal

Cómo ganar una propuesta

Ganando una propuesta

In this case the infinitive is the most natural form.

3.3.2 Infinitive for Web actions

In materials that will be part of VMware’s Web page make sure to use infinitives for all action related items.

Example:

Source Correct Incorrect

Download now Descargar ahora Descargue ahora

Watch the Webcast

Ver el webcast Vea el webcast

3.3.3 Latinisms

Latin phrases which are commonly used in English do not convey the same meaning in Spanish if left as is, or they elevate the tone of the document, for instance: de facto, vs., ad hoc, etc. Others, like status quo, have been adapted for Spanish and their spelling has to be minded, in this case statu quo. Please translate Latin phrases in the source into Spanish or use the correct spelling for Spanish.

Example:

VMware has become the de facto standard for Intel server virtualization.Correct target: VMware se ha convertido en el estándar indiscutible para la virtualización de servidores Intel.


Incorrect target: VMware se ha convertido en el estándar de facto para la virtualización de servidores Intel.

3.3.4 Preferences

Please express timeframes in months rather than in fractions in Spanish whenever you’re encountered with abbreviations like “Q4” or “H1” in the source:

Examples:Zimbra (open source email) – December 2009, expected close Q1 2010Correct target: Zimbra (correo electrónico de código abierto), diciembre de 2009, cierre previsto para el primer trimestre de 2010Incorrect target: Zimbra (correo electrónico de código abierto), diciembre de 2009, cierre previsto para el primer cuarto de 2010

Available H2 2009Correct target: Disponible a partir del segundo semestre de 2009.Incorrect target: Disponible a partir de la segunda mitad de 2009

Always look at the source and make sure to address DTP and design when translating timeframes. If “Q3” appears in a small text box or there are space constraints, translate as “T3” and not the full form “Tercer trimestre”.

3.4 Syntax Conventions English word order is quite restricted (SPO, subject + predicate + object + adverbial phrases), whereas Spanish is more flexible. Make use of the flexibility and freedom that Spanish syntax allows, in order to enhance the general language style.

However, please mind the following preferential structure which makes Spanish sound more natural:


Innovative solutions for the difficult problems facing IT

Soluciones innovadoras para los problemas de TI.

Innovadoras soluciones para los problemas de TI.

Adjectives after nouns.

The virtual machine was created with the wrong operating-system type.

La máquina virtual se creó con el tipo equivocado de sistema operativo.

La máquina virtual fue creada con el tipo equivocado de sistema operativo.

Active structures vs. passive ones

3.5 User Interface Elements

This item mainly concerns the VMware product evaluator’s guides. These guides contain step by step instructions that assist the user in evaluating VMware products. These steps deal with the products main features and often give the user detailed instructions on how to carry out the evaluation tasks. These document.doc Page 13 of 39

instructions mention UI elements, some of which are self explanatory in English but need an extended translation for Spanish:Please see an example of these instructions below:

Right-click the result to see the virtual machine context menu, and select Guest > Install/Upgrade VMware Tools.

Please translate the segment leaving all UI elements in English but providing an extended explanation of what each step means:

Haga clic con el botón secundario del mouse para ver el menú contextual de la máquina virtual y seleccione Guest > Install/Upgrade VMware Tools para ir al invitado e instalar o cambiar a la versión superior de VMware Tools.

3.5.1 Third party UI elements Please leave all third party UI elements or references in English. However, for MS Office UI elements or other interfaces that have long been localized and which translations are well established in Spanish please use the official translation in between brackets (as long as there are no space constraints).

Example:

Go to File and choose Save As...

Vaya a File (Archivo) y elija Save As... (Guardar como).


4 FORMATTING CONVENTIONS

4.1 Paragraph FormatsStick to the English formatting (if any). If the English source is inconsistent, notify the project coordinator or manager.

4.2 Number Formats

Make sure to use the correct form of the ordinal number respecting gender concordance:Example:

The 1st generation hypervisor.Correct target: El hipervisor de 1.a generación.Incorrect target: El hipervisor de 1.° generación.

4.2.1 RangesUse the local standard character and spacing when indicating a range.

Example: hyphen + separator spaces: 1 TB – 2,4 TB

4.2.2 CurrenciesAll currencies should be expressed in U.S. dollars following the source. Since some Latin-American currencies have the same or a similar symbol $, the use of USD is always recommended. Make sure to always add a non-breaking space between the number and the symbol, if it has more than 4 numbers:

Example:

US$4.138/$4.138 = 4138 USD

US$12.560 = 12 560 USD

Whenever possible avoid spelling out amounts and use numbers instead, i.e. U.S. 3 million = 3 000 000 USD. However, if the number becomes extremely long, for instance when translating amounts in billions, it is preferred to follow RAE's rules for spelling out numbers which are considered nouns. Example: U.S. 10 billion = 10 000 millones de USD

The above applies to all amounts expressed in USD that correspond to statistics, analysis, reference data, etc. Example:

VMware, $3+ billion in 2011

Target: VMware, más de 3000 millones de USD en 2011


4.2.3 Prices Updated!NOTE: These guidelines will be applied by VMware’s internal reviewers only. Please disregard this section of the SG during the TEP stage.

It may be that the prices and deal offers for LatAm vary from the ones in USD, Local teams will have information on the offers for their countries and communicate them appropriately. For this matter, when the amounts in USD in the source refer to prices, for instance: license prices, list prices, discounted prices, membership fees, training fees, SETs prices, part number prices, product suites and bundle prices, etc., they should be completely eliminated. These occurrences are mainly in promotional brochures, partner reward presentations, e-mail deal offers, etc.

In order to properly deal with these prices in the localized material, the following guidelines have to be applied:

If the price is mentioned with a discount eliminate the price and leave the discount reference. i.e.: get a 40% discount and save $200 > Obtenga un 40 % de descuento.

If the price has an equivalent in training credit eliminate both references. i.e. 750 USD or 75 credits > Precio por determinar (consultar créditos de capacitación)

If the price appears in a table eliminate the prices (ask the vendor to delete the cell and fix the table). Add a footnote at the end of the table that reads “Consulte los precios locales”.

If the price appears as the only reference in a sentence, for instance, “You can purchase this additional feature for only $250”, use the equivalent of “You can purchase this additional feature for an affordable price”: “precio asequible”, “a buen precio”, etc.

When prices are used for competitive comparison purposes, leave them and add a footnote specifying the case, i.e. “Los precios que se muestran son los precios sugeridos para la venta minorista en Estados Unidos en USD (MSRP, Market Suggested Retail Price US) y solo se aplican con los fines de esta comparación. Los precios regionales pueden variar.”

Use your own criteria when adapting the phrases so that they sound natural in Spanish and fit in the context. Don’t leave entire tables or slides full of notes that read “Por determinar”. In the cases where it’s necessary add a note for the DTP team during LSO asking for full sections to be deleted and a footnote added: See example below:

Original slide:

Incorrect way of dealing with prices: all of the prices were replaced by “Por determinar”


Correct way of dealing with prices: all of the prices were deleted and a note was added that reads “Consulte los precios locales”

IMPORTANT: If the price doesn’t seem directly related to a product or service (for instance, minimum deal sizes) they will be dealt with on a case by case scenario. Make sure to place a query during localization.As a general rule, the amounts in USD that are present in documents addressed to the partners or internal sales personnel are not related to products so they must be kept. For example: deal sizes, minimum purchases to enter a program, minimum requirements expressed in USD amounts, company investment amounts, etc.

4.2.4 Decimal & Thousands SeparatorsSince decimal and thousand separators vary between Latin American countries, the following rules apply:

Use a non-breaking space between thousands, only where there are 4 number or more (from 10 000 on).

Example: 2,000 should be 2000

10,000 should be 10 000

Use a comma to separate decimal fractions.

Example: 8.8 should be 8,8document.doc Page 17 of 39

4.2.5 Dates Dates must be worded.

Example: June 28, 2006 = 28 de junio de 2006

In tables, slides, etc., where space saving is needed, use slashes ( /) as separators, not dots (.) or hyphens (-).

Do not use leading zeros for single digits.

Be aware that U.S. dates are given as “month-day-year”. Follow the local standard.

Example: June 28, 2006 = 28/06/2006

Abstract date formats such as mm/dd/yy represent two digits for the month, two digits for the day and two (or four) digits for the year. When localizing these, use the initial letters for the words “Day,” “Month” and “Year” of the target language.

Example: June 28, 2006 = 28/06/06

In order to keep visual consistency, especially in promotional material, use the natural number 1 instead of the ordinal 1.° for the first day of the month:

Example:Valid from April 1st through 20th.Correct target: Válido del 1 al 20 de abrilIncorrect target: Válido del 1.° al 20 de abril.

4.2.6 Time Do not localize 12-hour (i.e., “a.m.”/ “p.m.”) format to 24-hour format. Use a colon (:) to separate hours and minutes. Do use leading zeros for single digits. Use a non-breaking space after the periods within the abbreviation: a.˽m.

Example: nine o’clock in the morning = 09:00 a. m.

Example: nine o’clock in the evening = 09:00 p. m.Whenever there are references to time zones in the United States, change them adding the local time in LatAm’s main reference cities:

Example: 9:00 am Eastern Time = Buenos Aires, Argentina: 10:00 a. m; Santiago, Chile: 10:00 a. m; México, México D. F.: 08:00 a. m.; Bogota, Colombia: 08:00 a. m.

4.2.7 Phone NumbersLocal-market telephone numbers should be grouped and separated per the English source.

Example: Tel 650-475-5000; Fax 650-475-5001

In international phone numbers, put a + before the country code and omit the leading zero of the area code.


5 LEGAL & OTHER DOCUMENTS

5.1 Legal LanguageWe will only translate a new legal text if VMware, Inc. expressly requires it. In such a case, it is particularly important that the translation be factually correct: linguistic errors can result in serious legal problems.

Do not attempt to mimic legal style. If you are not a lawyer or an approved legal translator, translate the English plainly and discursively.

5.2 Copyright InformationVMware copyright statements are limited boilerplate. A standard formulation reads as follows:

© 2005 VMware, Inc. All rights reserved. Protected by one or more of U.S. Patent Nos.

6,397,242, 6,496,847, 6,704,925, 6,711,672, 6,725,289, 6,735,601, 6,785,886, 6,789,156 and

6,795,966; patents pending. VMware, the VMware “boxes” logo and design, Virtual SMP and

vMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or

other jurisdictions. Microsoft, Windows and Windows NT are registered trademarks of Microsoft

Corporation. Linux is a registered trademark of Linus Torvalds. All other marks and names

mentioned herein may be trademarks of their respective companies.

The approved localized equivalent of this statement is:© 2005 VMware, Inc. Todos los derechos reservados. Protegido por una o más Patentes de

EE.UU., números: 6,397,242, 6,496,847, 6,704,925, 6,711,672, 6,725,289, 6,735,601,

6,785,886, 6,789,156 y 6,795,966; patentes pendientes. VMware, el logotipo y diseño de los

“cuadrados” de VMware, Virtual SMP y vMotion son marcas registradas o marcas comerciales

de VMware, Inc. en los Estados Unidos y otras jurisdicciones. Microsoft, Windows y Windows

NT son marcas registradas de Microsoft Corporation. Linux es marca registrada de Linus

Torvalds. Todas las demás marcas y nombres mencionados en este documento pueden ser

marcas comerciales de sus respectivas empresas.

Note that not all copyright statements contain the same particulars. In such a case, adapt the approved translation to meet the specific need. Further: patent numbers change frequently. You must always double-check them against the English source.

5.3 Item NumbersVMware printed documents – Brochures, Datasheets and Solution Briefs – show a unique identifier, or Item Number, at the end of the Copyright statement. The Item Number includes a two- or three-letter language code. English-language publications use “Eng” or “US”.

Examples: Item No: VM_ESX3_DS_Eng_Q206 Item No.: ACE_ds_eng_Q305 Item No.: VM_SVR_US_01.06

Replace only the “Eng” / “US” with the approved two-letter Latin American Spanish language code: LE


5.4 Part NumbersVMware technical manuals show a unique identifier, or Part Number, at the end of the manual. Part Numbers for each target-language publication will be provided by VMware during the translation process, and they must be replaced in the target-language manuals prior to final delivery to VMware.

5.5 Contracts The legal department has expressed their preference in the translation of the following terms: Major release, Minor Release, Upgrade, Update, and Maintenance Release.

Even when we have an entry for Update (“actualización”) and for Upgrade (“cambio a la versión superior”) in the main reference glossary, for legal documents and contracts we will follow the following conventions:

1. Se entiende por “Versión Principal” (en inglés, Major Release), también conocida como “Upgrade” o “Versión Superior”, toda versión general del Software que contenga mejoras o ampliaciones funcionales, designada por VMware mediante un cambio de dígito situado a la izquierda del primer punto decimal (p. ej., Software 5.0 >> Software 6.0).

2. Se entiende por “Versión Secundaria” (en inglés, Minor Release) toda versión general del Software que introduzca una cantidad limitada de nuevas características y funcionalidades, designada por VMware mediante un cambio de dígito situado a la derecha del punto decimal (p. ej., Software 5.0>>Software 5.1).

3. Se entiende por “Versión de Mantenimiento” o “Actualización” (en inglés, Maintenance Release y Update), toda versión públicamente disponible del Software en la que se faciliten únicamente correcciones o ajustes de mantenimiento, designada por VMware mediante un cambio de dígito situado a la derecha del segundo punto decimal (p. ej. Software 5.0 >> Software 5.0.1), o para determinado Software, mediante un cambio en el dígito del número de Actualización (p. ej., Software 5.0 Actualización 1).

5.6 Non-Disclosure Agreements and Confidentiality Information Some VMware presentations or internal documents contain an initial section that deals with confidentiality and non-disclosure of the information. Due to segmentation issues caused by the CAT tools, sometimes it’s hard to keep consistency in its translation. Please follow the following model.

Source TargetNon-Disclosure Agreement for All VMware Partners.The VMware vSphere and Cloud Infrastructure Product, Pricing, Packaging and Licensing information that is being provided today to you, our partner, is under a Non-Disclosure Agreement which is in effect until 3rd Quarter 2011.No part of this information should be shared with any other third party unless permission is obtained from VMware in writing.

CONFIDENTIAL INFORMATION.“Confidential Information” means any information disclosed by one party to the other pursuant to this Agreement that is marked “Confidential,” “Proprietary,” or in some similar manner.Each party shall treat as confidential all Confidential Information of the other party and shall not use such Confidential Information except to exercise its rights or perform its obligations under this Agreement.Each party shall not disclose such Confidential Information to any third party during the term of this Agreement and for a protection period of three (3) years beyond such term.The terms and conditions of this Agreement shall be Confidential Information subject to the provisions of this

Contrato de confidencialidad para todos los socios de VMware.La información sobre asignación de licencias, presentaciones, precios y producto de infraestructura de nube y VMware vSphere que usted, nuestro socio, recibe está regida por un contrato de confidencialidad que estará vigente hasta el tercer trimestre de 2011.No se debe compartir esta información con ningún tercero a menos que VMware lo autorice por escrito.

INFORMACIÓN CONFIDENCIAL.“Información confidencial” comprende toda información revelada por una de las dos partes, en conformidad con este Contrato, con la designación de “Confidencial”, “Propiedad exclusiva” o con una designación similar.Cada una de las partes debe tratar como confidencial toda Información confidencial de la otra parte y no debe utilizar dicha Información confidencial a menos que sea con el fin de ejercer sus derechos o cumplir con sus obligaciones conforme a este Contrato.Las partes involucradas no deben difundir esta Información confidencial a ningún tercero durante el plazo de este Contrato y durante un período de protección de tres (3) años después de transcurrido dicho plazo.


Section 6, whether or not marked confidential.This paragraph will not apply to any Confidential Information that: (a) was rightfully in possession of either party prior to receipt of such Confidential Information from the other party; (b) is or becomes a matter of public knowledge through no fault of the party receiving such Confidential Information hereunder; (c) is rightfully received from a third party without a duty of confidentiality; (d) is independently developed by the other party without breach of any confidentiality obligations; or (e) is disclosed by either party with the other party’s written approval; or (f) the recipient is required to disclose by applicable law or court order.The parties acknowledge that breach of this Section 6 will cause irreparable damage to the disclosing party for which monetary damages will be an inadequate remedy.Accordingly, either party will be entitled to seek and obtain injunctive and any other relief (legal or equitable) to restrain any breach or anticipated breach of this Sec

Los términos y condiciones de este Contrato deben tratarse como Información confidencial conforme a lo dispuesto en la Sección 6, independientemente de que se hayan designado o no como confidenciales.Este apartado no se aplicará a ninguna Información confidencial que: (a) estuviera legítimamente en posesión de alguna de las partes antes de recibir tal información confidencial de la otra parte; (b) sea o se convierta en un asunto de conocimiento público sin que la parte tenga responsabilidad alguna al haber recibido la presente información confidencial; (c) se reciba legítimamente de un tercero sin obligaciones de confidencialidad; (d) sea desarrollada de forma independiente por una de las partes sin incumplir las obligaciones de confidencialidad; o (e) sea divulgada por cualquiera de las partes con un permiso escrito de la parte afectada; o (f) el beneficiario se vea requerido por ley aplicable u orden judicial a divulgar la información.Las partes reconocen que el incumplimiento de la sección 6 causará daños irreparables a la parte que quede expuesta y una compensación monetaria sería insuficiente.Por consiguiente, cualquier parte tendrá derecho a buscar y obtener desagravio por mandato judicial o de otro tipo (legal o equitativo) para restringir cualquier incumplimiento o posible incumplimiento de esta sección.


6 Punctuation & Spacing

6.1 Spacing Between Sentences Use one space to separate one sentence from the next as opposed to the two spaces used in English. Bear in mind that this might not be possible in certain occasions due to CAT tools. In that case it should be fixed during DTP, please let you project manager know if this is the case.

6.2 Spacing Between Lines, Paragraphs & SectionsMatch the English.

6.3 Superscript Reference NumbersWhen a superscript reference number coincides with a punctuation mark, position the number after the punctuation mark.

6.4 Non-Breaking Elements

6.4.1 Phrases, Numbers and UnitsNever break company, product or brand names, or numbers and their units, across the end of a line.

Use non-breaking spaces (Ctrl+Shift+Spacebar in Microsoft Office programs, or in HTML) to keep these elements together. Examples are:

• between numbers and measurement unit symbols & abbreviations ... 100 MB, 5 lb.

• before or after symbols that represent a word ..................................... © 2005

• between elements of product names that should not be split ............. VMware Server

• before a dash or a hyphen used as a dash ......................................... xyz – abc, xyz - abc

Use a non-breaking hyphen (Ctrl+Shift+_ in Microsoft Office programs, or ‑ in HTML) to keep these elements together. For example:

• between groups of digits in a telephone or fax number ....................... 650-475-5000

6.4.2 Bulleted ParagraphsDo not break a bulleted paragraph across a page or column boundary.

6.5 Other Considerations – Punctuation

6.5.1 Quotation MarksUse curly characters (e.g., “VMware Server”).

6.5.2 ApostrophesUse curly characters (e.g., <Joe’s Bistro>).


6.5.3 Dashes, Hyphens, and Slashes Use hyphens between linked words or to break words. Use an en-dash (Ctrl-Num -) between phrases. Also see the rule for spacing before & after punctuation marks.

Avoid the em-dash ( — ); use a colon.

Avoid the use of the slash whenever possible, use a conjunction instead.

Example: Dev./testing = Desarrollo y pruebas

6.5.4 Square BracketsMenu items are always enclosed in square brackets ( [ ] ).


7 DTP Considerations

7.1 FontsHere is the list of approved source and target-language equivalent fonts for VMware publications:

English Font Spanish FontCourier Courier

Minion Pro Minion Pro

Myriad Pro Black Myriad Pro Black

Myriad Pro Black Cond Myriad Pro Black Cond

Myriad Pro Black SemiExt Myriad Pro Black SemiExt

Myriad Pro Cond Myriad Pro Cond

Myriad Pro Light Myriad Pro Light

Myriad Pro Light Cond Myriad Pro Light Cond

Myriad Pro Light SemiExt Myriad Pro Light SemiExt

Myriad Pro SemiExt Myriad Pro SemiExt

TheSansMonoCDOffice TheSansMonoCDOffice

TheSansMonoCDOfficeLF TheSansMonoCDOfficeLF

Times Times

VAG Rounded Light VAG Rounded Light

VAG Rounded Thin Courier

7.2 Typefaces

7.2.1 ItalicDo use italic where the source is italicized.

7.2.2 BoldDo use bolding where the source is bolded.

7.2.3 UnderlineDo use underlining where the source is underlined.


7.2.4 Other

Quotations

Quotations must be translated as follows: name of the person, his or her title in English, verb in the past tense, colon, open quotation marks, first word beginning with a capital letter, close quotation marks.

Example: David Donatelli, Executive Vice President de Storage Platform Operations, señaló: “Los clientes solicitaron que EMC se ejecutara en el

nivel medio y EMC cumplió”.

Titles and Positions

People’s titles and positions remain in English.

Example: Diane Green, Executive Vice President

But: When not referring to a specific individual, positions must be translated.

Example: Database administrator: administrador de bases de datos

Marketing Collateral Paper Size

Paper size for Marketing Collateral only should be resized to A4 if the original is Letter sized. This typically applies to InDesign documents only as Word and other formats aren’t usually printed. Please check with the project manager first if you have any questions regarding this.


8 Pronunciation guidelines for voice talents New!

8.1 General rules

This section of the Style Guide is intended to clarify the correct pronunciation of various terms and names appearing in audio translations which might be problematic for the voice talents. Its purpose is to give clear pronunciation guidelines for the voice talent to fit the specific requirements of the target language.We must provide a pronunciation note for:

Product and brands names Acronyms and abbreviations Borrowings Proper names Hyperlinks Numbers and amounts

8.2 Procedure

The procedure is as follows:

Highlight in the script all instances of a word or words that require a pronunciation note. In the next column, add the note specifying if the word has to be pronounced in English or Spanish and then a phonetic representation of the word. There’s no need to use any international phonetic alphabet, just make sure to keep sounds simple. Use “s” or “k” to represent the corresponding sounds and avoid mixing “q”, “c”, “z”, etc. For sounds that do not exists in Spanish, use the English phoneme: “sh”, “th”, etc.

Please see a few examples below:

Bienvenido al módulo de descripción general de VMware vCenter. Tenga en cuenta que este curso se desarrolló utilizando una versión preliminar del software de VMware vSphere. Por lo tanto, algunas pantallas, procedimientos o valores máximos de configuración de vSphere pueden ser diferentes de los de la versión final del software.

VMware vCenter: en inglés, vi-em-wear vi-senterVMware vSphere : en inglés, vi-em-wear vi-sfirvSphere : en inglés, vi-sfir Software: en español, sóftwer

2 - Contenido del cursoEsta tabla resume los temas que se ven en este curso y muestra la duración aproximada de cada módulo. El tiempo que le tome completar los módulos dependerá de su estilo de aprendizaje y nivel de experiencia en los temas. El primer módulo de este curso es Descripción general de VMware vCenter. En este módulo, aprenderá los conceptos claves sobre vCenter Server y revisará la arquitectura de vCenter Server. También, aprenderá conceptos claves relacionados con vCenter Linked Mode, a aplicar perfiles de anfitrión Host Profiles y a utilizar Orchestrator.

vCenter Linked Mode: en inglés, vi-senter linkt moudvCenter Server: en inglés, vi-sénter sérverHost Profiles: en inglés, joust prófailsOrchestrator: en inglés, orkestréitor

There’s no need to add a note for every instance of a word in the script. While they should all be highlighted, the note only has to be added for the first occurrence. The voice talents are professional actors; they don’t need queues on where to stress the phrases or intonation notes.


8.3 Specific guidelines

The following guidelines will ensure pronunciation consistency and they must be followed:

All product names must be pronounced in English. For example: VMware vSphere : en inglés, vi-em-wear vi-sfir

The acronyms that correspond to VMware products or features (HA, DRS, DPM, FT, etc.) must be pronounced and spelled in English: For example: DRS: en inglés letra por letra, di-ar-es

General IT or industry acronyms or those that aren’t related to product names must be pronounced and spelled in Spanish.For example: TCO: en español letra por letra, ti-si-ou

Acronyms that can be pronounced as a full word are read in Spanish. For example: SAN: en español como palabra completa, san

Product versions (numbers) are read in Spanish even if the product name is read in English. Example: vSphere 5.0: en inglés y el número en español, vi-sfir sinco punto sero

8.4 Frequently occurring itemsThe following is a compilation of pronunciation notes gathered from the latest projects. This is a live document and its purpose is to facilitate the task for all reviewers. Make sure to update it here: https://docs.google.com/spreadsheet/ccc?key=0Au4d_PTYuAKYdFhjYk9ZQUhlY2FMVGcxcUNQeG5tM1E&pli=1#gid=0

Pronunciation notes2 KB: dos kilobáits2 TB: en español, dos terabáits2:1: dos a uno3a: tres a3D: en español, tres de5.0: en español, cinco punto cero50 %: cincuenta por ciento802.1: ochocientos dos punto unoActive Diretory: en inglés, áctif dairéctoriAlarms and Events Management Service: en inglés, alarms and ivents mánichment sérvisAPI: en español como palabra completa, apiAppSpeed: en inglés, ap-spidAuthentication Proxy: en inglés, othentikeishon proksiAuto Deploy: en inglés, oro diploiBIOS: en español como palabra completa, biosBytes: en inglés, báitsCapEx: en español, cápeksCBT: en español, se-be-teChanged Block Tracking: en inglés, chéinchd blok trákin

Chargeback: en inglés, chárchbak

Cisco Nexus 1000V: en inglés, sisco neksus uan thausend vi

CPU: en español letra por letra, se-pe-uData Recovery: en inglés, déita ricáveriDatastores: en inglés, deitastorsDemilitarized zone: en inglés, demilitaraist souneDHCP: en español letra por letra, de-ache-se-peDistributed Switch: en inglés, distríbiuted suich


https://docs.google.com/spreadsheet/ccc?key=0Au4d_PTYuAKYdFhjYk9ZQUhlY2FMVGcxcUNQeG5tM1E&pli=1#gid=0

https://docs.google.com/spreadsheet/ccc?key=0Au4d_PTYuAKYdFhjYk9ZQUhlY2FMVGcxcUNQeG5tM1E&pli=1#gid=0

DMZ: en español, de-eme-setaDPM: en inglés letra por letra, di-pi-em DRS: en inglés letra por letra, di-ar-esE/S: en español, entrada y salidaESX 4.1: en español, i-es-eks cuatro punto 1ESXi 4.1: en español, i-es-eks-ai cuatro punto 1ESXi 5.0: en español, i-es-eks-ai cinco punto ceroESXi Embedded: en inglés, i-es-eks-ai embeded

ESXi Installable Edition: en inglés, i-es-eks-ai instálabol edíshonESXi: en inglés letra por letra, i-es-eks-aiESXi: en inglés, i-es-eks-aiEthernet Switched Port Analyzer: en inglés, éthernet swicht port ánalaiser

Ethernet: en español, éternetFault Domain manager: en inglés, folt doméin mániyerFC SAN: en español, efe-se sanFC: en español, efe-seFDM: en español letra por letra, efe-de-emeFT: en inglés letra por letra, ef-ti HA: en inglés letra por letra, eich-eiHardware:en español, járdwerHeartbeat: en inglés, jart-bitHost and Virtual Machine Configuration Service: en inglés, joust and vírchual mashín configuiureishon sérvisHost Profiles: en inglés, joust prófailsHP: en español letra por letra, ache-peIBM DB2: en español, i-be-eme de-be dos

IBM DB2 9.5: en español, i-be-eme de-be dos nueve punto cinco

IBM DB2 9.7: en español, i-be-eme de-be dos nueve punto siete

IHV: en español letra por letra, i-ache-uveIntel: en español, intelIP: en español letra por letra, i-peiSCSI SAN: en inglés, ai-skasi saniSCSI: en inglés, ai-skasiISV: en español letra por letra, i-ese-uveJournaling: en inglés, yornalin

Link Layer Discovery Protocol: en inglés, link leier discoveri prótokol

Linux: en español, linuksLLDP: en español letra por letra, ele-ele-de-pe LUN: en español palabra completa, lunMac OS X: en inglés, mac ou-es eksMAC: en español, mak

Microsoft SQL Server: en español, máikrosoft ese-ku-ele sérver

Microsoft SQL Server 2005: en español, máikrosoft ese-ku-ele sérver dos mil cinco

Microsoft SQL Server 2008 : en español, máikrosoft ese-ku-ele sérver dos mil ocho


Microsoft SQL Server 2008 R2 Express : en español, máikrosoft ese-ku-ele sérver dos milocho erre dos ekspres

Microsoft SQL Server 2008 R2: en español, máikrosoft ese-ku-ele sérver dos mil ocho erre 2Mouse: en inglés, máusMylearn: en inglés, mai lernNAS: en español, nasNAT : en español como palabra completa, natNetflow: en inglés, netflouNetIOC: en inglés, net-ai-ou-siNetwork Core Dump: en inglés, network cor dompNIC: en español, nikOEM: en español letra por letra, o-e-emeOpEx: en español, ópeksOracle: en inglés, óraklOutline: en inglés, áutlainPlugins: en inglés, pláginPOSIX: en español como palabra completa, pósiks

Pre-boot Execution Environment: en inglés, pri-but eksekiushon envairmen

Proxy: en inglés, proksiPXE: en español letra por letra, pe-ekis-eQoS: en español letra por letra, ku-o-eseQuality of Service: en inglés, kualiti of servisRAM: en español como palabra completa, ramRaw Device Mapping: en inglés, ro divais mapinRDM: en español, erre-de-eme

Resources and VM Inventory Management Services: en inglés, rísorses and vi-em ínventori manichment sérvises

SAN: en español, sanScript: en inglés, scriptSCSI: en inglés, skasiSDK: en español letra por letra, ese-de-kaSearch: en inglés, serchSnapshots: en inglés, snapshatsSO: en español letra por letra, ese-o

Software Development Kit: en inglés, sóftwer divelopmen kit

Software: en español, sóftwerSolid State Drives: en inglés, salid steit draifsSP: en español letra por letra, ese-peSP1: en español, ese-pe unoSP2: en español, ese-pe dosSP3: en español, ese-pe tresSP4: en español, ese-pe cuatroSPAN: en español como palabra completa, spanSSD: en español letra por letra, ese-ese-de

Statistics and Logging Service: en inglés, statístics and lóguin servís

Storage vMotion: en inglés, storich vi-moushondocument.doc Page 29 of 39

Storage I/O Control: en inglés, vi-sfir ai-ou controlSVGA: en español letra por letra, ese-ve-je-aSwitches: en inglés, suiches

Task Scheduler Service: en inglés, task skédiuler sérvis

Thin Provisioning: en inglés, then provishoninThumb: en inglés, thamTI: en español letra por letra, te-iTP: en español letra por letra, te-peUEFI: en español como palabra completa, uefi

USB 3.0: en español letra por letra, u-ese-be tres punto cero

vCenter Server: en inglés, vi senter server

vCenter Hardware Status: : en inglés, vi-senter járdwer stéirus

vCenter Linked Mode: en inglés, vi-senter linkt moud

vCenter Service Status: : en inglés, vi-senter sérvis stéirus

vCenter Storage Monitoring: en inglés, vi-senter stórich mónitorin

vCLI: en inglés, vi-si-el-aiVDC: en español letra por letra, ve-de-seVDS: en inglés letra por letra, vi-di-esVirtual appliances: en inglés, vírchual apláiancesVirtual Data Center: en inglés, vírchual déita sénterVirtual Machine Provisioning Service: en inglés, vírchual mashín províshonin sérvis

Virtual Machine Monitor: en inglés, vírchual mashín monitor

vLockstep: en inglés, vi-lókstepVM: en español letra por letra, ve-eme

vmdk (.vmdk): en español letra por letra, ve-eme-de-ka

VMFS Volume Grow: en inglés, vi-em-ef-es volium grou

VMFS: en inglés letra por letra, vi-em-ef-es

VMFS2:en inglés letra por letra y el número en español, vi-em-ef-es dos

VMFS3:en inglés letra por letra y el número en español, vi-em-ef-es tres

VMFS5: en inglés letra por letra y el número en español, vi-em-ef-es cinco

VMkernel: en inglés, vi-em-karnelVMM: en español letra por letra, ve-eme-emeVMsafe: en inglés, vi-em-séifVMware Tools: en inglés, vi-em-wear tuls

VMware vSphere High Availability: en inglés, vi-em-wear vi-sfir jai avéilabiliti

VMware Distributed Power Management: en inglés, vi-em-wear distríbiuted páuer mánichmentVMware Distributed Resource Scheduler: en inglés, vi-em-wear distríbiuted risors skédiuler VMware Fault Tolerance: en inglés, vi-em-wear folt tólerans


VMware HA: en inglés, vi-em-wear eich-eiVMware VIX: en inglés, vi-em-wear vi-ai-eksVMware: en inglés, vi-em-wearvNIC: en inglés, vi nikVPN: en español letra por letra, ve-pe-enevShield App: en inglés, vi-shild apvShield Edge: en inglés, vi-shild edchvShield Endpoint: en inglés, vi-shild endpointvShield Suite: en inglés, vi-shild suitvShield Zone: en inglés, vi-shild sounvSphere Client: en inglés, vi sfir kláientvSphere Web Client: en inglés, vi-sfir web kláientvSphere CLI : en inglés, vi-sfir si-el-aivSphere Distributed Switches: en inglés, vi-sfir distríbiuted suiches

vSphere DRS: en inglés, vi-sfir di-ar-es vSphere Storage DRS: en inglés, vi-sfir storich di-ar-esvSphere HA: en inglés, vi-sfir eich-eivSphere PowerCLI: en inglés, vi-sfir páwer si-el-aivSphere Standard Switches: en inglés, vi-sfir stándard suiches

vSphere Storage vMotion: en inglés, vi-sfir storich vi-moushon

vSphere Syslog Collector: en inglés, vi-sfir sislog colector

vSphere Update Manager: en inglés, vi-sfir apdeit maniyer

vSphere vMotion: en inglés, vi-sfir vi-moushonvSphere: en inglés, vi-sfirVSS: en inglés letra por letra, vi-es-es

Windows Terminal Services: en inglés, uíndous términal sérvises

Windows: en inglés, uíndous

x86: en español, equis ochenta y seisXterm: en inglés, iks-termOrchestrator: en inglés, orkestréitorvCenter Service Status: en inglés, vi-senter sérvis stéirusvCenter vApp: en inglés, vi-sénter vi-apvServices: en inglés, vi-sérvisesvCenter Server Appliance: en inglés, vi-sénter server apláiansOVF: en español letra por letra, o-ve-efeFile: en inglés, fáilDeploy OVF Template: en inglés, diplói o-vi-ef témpleitDisk Format: en inglés, disc fórmat5480: en español, cincuenta y cuatro ochenta

http://(dirección IP del virtual appliance de vCenter):5480: en español, hache-te-te-pe diagonal diagonal paréntesis dirección i-pe del vírchual apláians de vi-sénter paréntesis dos puntos cincuenta y cuatro ochenta

root: en inglés, rut


NIS: en español como palabra copleta, nis

vCenter Server Appliance Web Console: en inglés, vi-sénter server apláians ueb cánsoul

TCP/IP: en español letra por letra, te-ce-pe i-peStatus: en inglés, stéirusAdobe Flex: en español, adobe flex64 bits: en español, sesenta y cuatro bitsvApps: en inglés, vi apsvSphere Web Client Administration Tool: en inglés, vi-sfir ueb cláient administréishon tulRegister vCenter Server: en inglés, reyister vi-sénter sérverURL: en epañol letra por letra, u-erre-eleWork in progress: en inglés, werk in prágresMy recent tasks: en inglés, mai rísent tasksvSphere Security: en inglés, vi-sfir sekiúritiInventory: en inglés, ínventoriVirtual Machines: en inglés, vírchual mashíns Hosts: en inglés, jóustsJava: en inglés, yavaQuery Service: en inglés, kueri sérvisTomcat Web Services: en inglés, tomcat ueb sérvisesX: en español, equisAdd: en inglés, adMicrosoft Active Directory Application Mode: en inglés, máikrosot actif dairéctori aplicashon moudADAM: en español como palabra completa, adam

vCenter Installer: en inglés, vi-sénter instolerLDAP: en español letra por letra, ele-de-a-peStart: en inglés, startPrograms: en inglés, prougramsvCenter Linked Mode Configuration: en inglés, vi-sénter linkt moud konfiguiuréishonModify Linked Mode Configuration: en inglés, modifai linkt moud configuiuréishonJoin vCenter instance to an existing Linked Mode group or another instance: en inglés, yoin vi-sénter instans tu an existin linkt moud grup or anoder instansDNS: en español letra por letra, de-ene-eseImage Profiler: en inglés, ímich profailerSwitch: en inglés, suichvSwitch0: en inglés y el número en español, vi-suich cerovmnic0: en inglés y el número en español, vi-em nic cerovmnic1: en inglés y el número en español, vi-em nic unoProfile Editor: en inglés, profail éditorConfiguration details: en inglés, configuiureishon diteilsCompliance details: en inglés, complaians diteilsvCO: en inglés, vi-si-ouShell: en inglés, shelPerl: en inglés, perlCMDB: en español letra por letra, se-eme-de-be


vCenter Server API: en inglés, vi-sénter ei-pi-aiSAP: en español como palabra completa, sapPower-On: en inglés, páwer onMicrosoft .NET 3.5 SPFramework: en español, máikrosoft net tres putno cinco ese pe frameworkSoftware Development Kit: en inglés, sóftwer divelopment kitSDK: en español letra por letra, ese-de-kaOrchestrator Web Service: en inglés, orkestréitor ueb sérvisWeb 2.0: en español, ueb dos punto ceroAJAX: en inglés, ayaxWorkflows: en inglés, uorkflousLifecycle Manager: en inglés, láifsaicol mániyerhttp://(nombre_del_didispositi_o_dirección_IP):8282: en español, hache te-te-pe diagonal diagonal paréntesis nombre del dispositivo o dirección IP dos puntos ochenta y dos ochenta y dosinstall_directory\Orchestrator\apps: en inglés y español, instol guión bajo dairéctory diagonal orkestréitor diagonal apsHost name: en inglés, joust neimJDBC: en español letra por letra, jota de be se VMware Infrastructure: en inglés, vi-em-wear infrastrokchur Triggered Alarms: en inglés, triguerd alarmsAlarms: en inglés, alarmsReset Alarm to Green: en inglés, riset alarm tu grinQA_: en español, ku a guión bajoLost Network Connectivity: en inglés, lost netwerk conectivitivSphere Client: en inglés, vi sfir kláientTriggered Alarms: en inglés, triguerd alarmsAlarms: en inglés, alarmsReset Alarm to Green: en inglés, riset alarm tu grinQA_: en español, ku a guión bajo

Lost Network Connectivity: en inglés, lost netwerk conectiviti

Operator: en inglés, operéitorValue: en inglés, váliuEmpty: en inglés, emptiOnce: en inglés, unasRepeat: en inglés, ripitAcknowledged: en inglés, aknolechdAcknowledged By: en inglés, aknolechd bai

vSphere Client Performance: en inglés, vi-sfir kláient performans

VM Processor: en inglés, vi-em prosesorVM memory: en inglés, vi-em mémoriWindows Management Instrumentation: en inglés, uindous manichment instrumenteishonWMI: en español letra por letra, doble u eme iVirtual Machine Resources: en inglés, vírchual mashín risorsesHost Resources: en inglés, jost rísorses


9 Local ConsiderationsAll translations should be produced such that they are acceptable to as wide of a Latin American audience as possible. There may be specific cases that limit the ability to follow this rule and in these situations, it is acceptable to use a Chilean or Argentine translation if there is no universally acceptable way of translating a given term or style. However, where possible, please ensure that a non-country specific form of Latin American Spanish is used.

General considerations on marketing materials Focus on the intent and flow of language rather than word by word translation. Use your linguistic

freedom to localize the content in order to capture the message and thus avoiding a staccato word by word translation.

One way to help capturing what the real message is, is to read the material/paragraph prior to translating the material

When comparing companies or mentioning alliances, benchmarking studies, etc., VMware`s name must always be mentioned in first place. For example, IBM and VMware hardware alliance translated as Alianza de hardware de VMware e IBM.

Work proactively with your designated VMware point of contact/reviewer and ask questions, bring forward- and clarify issues with them.

Take into account space restrictions in marketing materials such as Flyer, PPT, PDF and Sales Training Content.


10Appendix 1 Updated!The embedded spreadsheet contains the approved product and brand names. Make sure, as always, to place a query if you believe you’ve found a product name which isn’t in this list, or if you have any other questions or concerns related to the product and brand names.

Approved product names.xlsx


€¦ · web viewstyle guide for latin american spanish. produced by vmware, inc. revision history....

Documents