@@ -14,373 +14,305 @@
@@ -14,373 +14,305 @@
VTEX Localization
-Style Guide
-PORTUGUESE
- - - - - - - - - - - - - - - - -Created by: Yuli Monarin
-Updated by: Yuli Monarin
-Last updated: July 7, 2023
- - -Table of Contents
- - - - - - - - - -Regions, Demonyms and Nationalities
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Non-localized UI in Education texts
- - - - - -VTEX Portuguese Writing Style Guide
- - -Content Marketing Localization
- - - - - - - - - -Product Localization
-Created by: Yuli Monarin
+Updated by: Yuli Monarin
+Last updated: July 7, 2023
+ +Product Localization
+Product Marketing
-Product Marketing
+Education
-Education
+Legal
-Legal
+Serious, not playful — avoid jokes and puns, ambiguity, be straightforward.
-Exclusive, not arrogant — a plus of sophistication, but the choice of words should be simple and clear.
-Authority, not arbitrary.
-Young, not naive — fresh and pleasant content.
-Rebel, not inconsequential.
-The tone of voice will be guided by the source content:
-Interviews: The tone is set by the person that is being interviewed, adaptation will be only done to clarify where the source is missing clarity.
-Corporate (Finance, PR): Serious and precise, little room for target adaption except when it makes it easier to understand the content (shorter sentences or topic changes that do not affect the source meaning).
-Marketing (Blog posts): Concise and crisp, clear and on point, fresh and less formal than the Corporate or Interview texts.
-Clarity: Content free from any ambiguities. Straightforwardness helps readers have a better understanding of the message.
-Suitability: The text must match the audience, the channel and has to be focused on what is appropriate for each instance.
-Precision: Do not alter the source meaning, even when less formal texts might leave room for adaptation.
-The general style should be clear, friendly, and concise.
-Keep the following guidelines in mind:
-Serious, not playful — avoid jokes and puns, ambiguity, be straightforward.
+Exclusive, not arrogant — a plus of sophistication, but the choice of words should be simple and clear.
+Authority, not arbitrary.
+Young, not naive — fresh and pleasant content.
+Rebel, not inconsequential.
+The tone of voice will be guided by the source content:
+Interviews: The tone is set by the person that is being interviewed, adaptation will be only done to clarify where the source is missing clarity.
+Corporate (Finance, PR): Serious and precise, little room for target adaption except when it makes it easier to understand the content (shorter sentences or topic changes that do not affect the source meaning).
+Marketing (Blog posts): Concise and crisp, clear and on point, fresh and less formal than the Corporate or Interview texts.
+ +Clarity: Content free from any ambiguities. Straightforwardness helps readers have a better understanding of the message.
+Suitability: The text must match the audience, the channel and has to be focused on what is appropriate for each instance.
+Precision: Do not alter the source meaning, even when less formal texts might leave room for adaptation.
+The general style should be clear, friendly, concise.
+Keep the following guidelines in mind:
+Language specifics
-When translating texts to Portuguese, Portuguese capitalization standards must be followed. So use sentence case: keep the first letter of the first word of the sentence capitalized and then the rest of the words should be in lower case — unless there is a proper noun or a name/section that should start in upper case in the middle of the sentence.
-The section above applies to the VTEX Admin labels (UI) and titles as well.
-incorrect: Detalhes do Produto
-Correct: Detalhes do produto
- -Use lower case for months and days of the week, for example: segunda-feira, domingo, janeiro, outubro.
+Language specifics
+ +When translating texts to Portuguese, Portuguese capitalization standards must be followed. So use sentence case: keep the first letter of the first word of the sentence capitalized and then the rest of the words should be in lower case — unless there is a proper noun or a name/section that should start in upper case in the middle of the sentence.
+ +The section above applies to the VTEX Admin labels (UI) and titles as well.
+incorrect: Detalhes do Produto
+Correct: Detalhes do produto
-You should use uppercase for job titles and lower case for career fields and professions, for example: engenheiro, engenharia, Diretor de Engenharia.
-Geographic regions should always be in upper case, whereas demonyms and nationalities are in lower case. Examples: Nordeste, América Latina, sudestino, brasileiro.
-Holidays are usually capitalized, for example: Ano Novo, Natal, Dia do Trabalho, Sete de Setembro.
-When mentioning a path to a specific UI in the Admin, use the capitalization as it is on the platform. The text must reflect what users see.
-If you see common words capitalized in the middle of sentences when they do not need to or are not referring to a “path” the user must access on the platform, please consider using sentence case, as it can be an inconsistency in the source text. For example, this may happen with the term “Seller White Label”, which you can use as “seller white label”.
-In legal documents, we follow the capitalization as it appears in the source text.
-Please be clear and objective. While English usually includes “please”, the best practice for Portuguese text in the UI is to just be right to the point.
-Examples:
-English: Please try again. | Portuguese: Tente novamente.
-English: Would you like to continue? | Portuguese: Deseja continuar?
-In Q3 2022, the Localization team revised the Admin user interface, specifically focusing on the localization of text strings. Throughout this process, we applied the guidelines outlined in this style guide to ensure consistency and coherence in the Admin text. In the process, we’ve standardized the UI text and compiled all relevant information into a document. Please refer to the VTEX Admin string standardization in Portuguesefor more information.
-In the technology and marketing industries, it’s common to use terms in English amongst a text in Portuguese, unless there’s a widely used alternative in Portuguese. So remember this and question words that you cannot easily find on Google results.
-We usually do not italicize these words, unlikely in Spanish.
-Examples: start-up, direct-to-consumer, composable, chatbot, on demand.
-In general, numbers from one to ten must be spelled out, unless there are numbers bigger than ten in the same sentence (to keep the format consistent). Exceptions: For titles and currencies, always use digits.
-Avoid starting sentences with numbers. If that is the case, however, write the number in full. Exception: Titles can begin with numerals.
-Thousand units must be written with a dot, while commas are used in decimals. Note that in English it is the opposite. Examples: in Portuguese, use 4.000 (not 4000 nor 4,000) and 1,2, not 1.2.
-Always add a space between the number and its unit.
-Note: While it is common to use “Nº”, “nº”, or “no.” as an abbreviation for "number" in Portuguese, the correct and preferred abbreviation is "N.º" (or “n.º” if it’s in the middle of the sentence), with the dot. Other possibilities of abbreviations accepted are “núm.” ou “n.”. When abbreviating "number" in Portuguese, it is essential to include the dot after the letter "N" to maintain accuracy and consistency. This follows the established typographical conventions in Portuguese writing.
-The percent sign should always follow the number without any spaces between them. For example: 10%.
-In English, it’s common to use personal pronouns repeatedly. Avoid doing this in Portuguese and replace them with articles or remove them.
-Do not follow the source punctuation blindly. Keep what makes sense for a fluent text in Portuguese and adapt accordingly. Do not use punctuation in titles and subheadings.
-Avoid using exclamations marks in the text.
-Do not use the oxford comma in Portuguese.
-Use lower case after colons.
-Slashes
-In Portuguese, it is the standard practice to remove spaces before and after the forward slash (/). This rule applies when using the forward slash as a separator or in cases such as abbreviations. Example: Price/month, enviar p/ alguém.
+Use lower case for months and days of the week, for example: segunda-feira, domingo, janeiro, outubro.
+You should use uppercase for job titles and lower case for career fields and professions, for example: engenheiro, engenharia, Diretor de Engenharia.
+Geographic regions should always be in upper case, whereas demonyms and nationalities are in lower case. Examples: Nordeste, América Latina, sudestino, brasileiro.
+Holidays are usually capitalized, for example: Ano Novo, Natal, Dia do Trabalho, Sete de Setembro.
+ +When mentioning a path to a specific UI in the Admin, use the capitalization as it is on the platform. The text must reflect what users see.
+If you see common words capitalized in the middle of sentences when they do not need to or are not referring to a “path” the user must access on the platform, please consider using sentence case, as it can be an inconsistency in the source text. For example, this may happen with the term “Seller White Label”, which you can use as “seller white label”.
+ +In legal documents, we follow the capitalization as it appears in the source text.
+ +Please be clear and objective. While English usually includes “please”, the best practice for Portuguese text in the UI is to just be right to the point.
+Examples:
+English: Please try again. | Portuguese: Tente novamente.
+English: Would you like to continue? | Portuguese: Deseja continuar?
+In Q3 2022, the Localization team revised the Admin user interface, specifically focusing on the localization of text strings. Throughout this process, we applied the guidelines outlined in this style guide to ensure consistency and coherence in the Admin text. In the process, we’ve standardized the UI text and compiled all relevant information into a document. Please refer to the VTEX Admin string standardization in Portuguesefor more information.
+ +In the technology and marketing industries, it’s common to use terms in English amongst a text in Portuguese, unless there’s a widely used alternative in Portuguese. So remember this and question words that you cannot easily find on Google results.
+We usually do not italicize these words, unlikely in Spanish.
+Examples: start-up, direct-to-consumer, composable, chatbot, on demand.
+ +In general, numbers from one to ten must be spelled out, unless there are numbers bigger than ten in the same sentence (to keep the format consistent). Exceptions: For titles and currencies, always use digits.
+Avoid starting sentences with numbers. If that is the case, however, write the number in full. Exception: Titles can begin with numerals.
+Thousand units must be written with a dot, while commas are used in decimals. Note that in English it is the opposite. Examples: in Portuguese, use 4.000 (not 4000 nor 4,000) and 1,2, not 1.2.
+Always add a space between the number and its unit.
+Note: While it is common to use “Nº”, “nº”, or “no.” as an abbreviation for "number" in Portuguese, the correct and preferred abbreviation is "N.º" (or “n.º” if it’s in the middle of the sentence), with the dot. Other possibilities of abbreviations accepted are “núm.” ou “n.”. When abbreviating "number" in Portuguese, it is essential to include the dot after the letter "N" to maintain accuracy and consistency. This follows the established typographical conventions in Portuguese writing.
+ +The percent sign should always follow the number without any spaces between them. For example: 10%.
+ +In English, it’s common to use personal pronouns repeatedly. Avoid doing this in Portuguese and replace them with articles or remove them.
+ +Do not follow the source punctuation blindly. Keep what makes sense for a fluent text in Portuguese and adapt accordingly. Do not use punctuation in titles and subheadings.
+ +Avoid using exclamations marks in the text.
+ +Do not use the oxford comma in Portuguese.
+ +Use lower case after colons.
+Slashes
+In Portuguese, it is the standard practice to remove spaces before and after the forward slash (/). This rule applies when using the forward slash as a separator or in cases such as abbreviations. Example: Price/month, enviar p/ alguém.
Incorrect: "Eu comprei um livro / revista na livraria."
-Correct: "Eu comprei um livro/revista na livraria."
-In English, it’s common to use em-dashes where we would simply use commas in Portuguese. So they do not always need to be kept in the target text.
-If you opt to use it to emphasize a sentence or word, make sure you are using the correct “travessão”: — (Alt+0151) and add a space before and after it.
-It must be used to join the extreme values of a series, such as numbers, letters, or others. You can also use it to unite words that have a logical connection. The shortcut to use it is Alt+0150.
-Examples: Rio–Niterói bridge, 1995–2004, A–Z.
-Hyphens must only be used in compound words. If it is incorrectly used in the source text, please use it correctly in your translation. To use it, you can simply press the symbol on your keyboard.
-Examples: pré-requisito, bem-sucedido, Covid-19.
-Both straight/curly quotation marks are acceptable. Choose one to use throughout the text and stick to it.
-The period must be placed before the quotation mark when the quote starts and ends the sentence.
-The period must be placed after the quotation mark when the quotation does not begin but ends the sentence.
-Sometimes punctuation on lists differs according to the language. In Portuguese, there are three options for marking punctuation in lists: with periods, semicolons, or no punctuation mark.
-For bulleted list items composed of full sentences, you should use a period at the end of the sentence. For bulleted list items not composed by full sentence, no punctuation is required.
-Source texts may not always have consistent lists. It’s your job to guarantee the lists are consistent in translations.
-If the list items start with verbs, the same verb format must be used for all items. The same applies to nouns. The important point is: their items’ form must be consistent.
-Example: Incorrect vs. Correct
+Correct: "Eu comprei um livro/revista na livraria."
+ +In English, it’s common to use em-dashes where we would simply use commas in Portuguese. So they do not always need to be kept in the target text.
+If you opt to use it to emphasize a sentence or word, make sure you are using the correct “travessão”: — (Alt+0151) and add a space before and after it.
+ +It must be used to join the extreme values of a series, such as numbers, letters, or others. You can also use it to unite words that have a logical connection. The shortcut to use it is Alt+0150.
+Examples: Rio–Niterói bridge, 1995–2004, A–Z.
+ +Hyphens must only be used in compound words. If it is incorrectly used in the source text, please use it correctly in your translation. To use it, you can simply press the symbol on your keyboard.
+Examples: pré-requisito, bem-sucedido, Covid-19.
+ +Both straight/curly quotation marks are acceptable. Choose one to use throughout the text and stick to it.
+The period must be placed before the quotation mark when the quote starts and ends the sentence.
+The period must be placed after the quotation mark when the quotation does not begin but ends the sentence.
+ +Sometimes punctuation on lists differs according to the language. In Portuguese, there are three options for marking punctuation in lists: with periods, semicolons, or no punctuation mark.
+For bulleted list items composed of full sentences, you should use a period at the end of the sentence. For bulleted list items not composed by full sentence, no punctuation is required.
+ +Source texts may not always have consistent lists. It’s your job to guarantee the lists are consistent in translations.
+If the list items start with verbs, the same verb format must be used for all items. The same applies to nouns. The important point is: their items’ form must be consistent.
+Example: Incorrect vs. Correct
- -
Avoid using gerunds. Prefer the infinitive form, or change the verb to a noun.
-For Education texts, it’s common to see the gerund in English and a “How to” in Portuguese.
-Example:
-English (source): “Implementing the strategy”
-Portuguese: “Implementar a estratégia”, “Implementação da estratégia”, or “Como implementar a estratégia” (preferred for Education)
-The indirect object must always be linked to the verb by a preposition. This also applies to cases in which there is more than one direct object. Make sure your sentences are synthetically parallel.
-Examples:
-Incorrect: Esse cenário apresenta vantagens para o usuário, já que ele permite explorar o catálogo, inventário e preços com liberdade, conforme seu perfil de acesso.
-Correct: Esse cenário apresenta vantagens para o usuário, já que ele permite explorar o catálogo, o inventário e os preços com liberdade, conforme seu perfil de acesso.
- -Incorrect: [...] problemas de negócio específicos relacionados à usabilidade da loja, vendas e pós-vendas.
-Correct: (option 1) [...] problemas de negócio relacionados a usabilidade da loja, vendas e pós-vendas. (option 2) [...] problemas de negócio relacionados à usabilidade da loja, às vendas e ao pós-vendas.
-For the 12-hour format, use the abbreviation in lowercase with dots. Add a space between the hour and the abbreviation. For the 24-hour format, use the hour unit (h) between the hour and the minutes, without spaces. Zeroed minutes are not required.
-For indicating time zones, use the format (GMT) in front of the hour.
-Examples: 6 p.m. (GMT-3), 10:30 a.m., 14h30, 16h
Dates should be written as follows:
-22 de outubro de 2021, or 22/10/21 (day, month, year)
-For illustrative examples, as in Help Center: You can localize the examples that are given in another currency other than reais. Check if the context allows it.
-For precise data in general: You can either use US$ for dollars (preferred) or only the number followed by “dólares”.
-The abbreviation for real is R$. There must always be a space between the abbreviation and the number.
-In Storefront or apps used by other people (such as end customers, and pickers and couriers in Pick and Pack and Last Mile) than the Admin, use the standard R$.
-In Admin labels (technical context), prefer the 3-letter ISO format: USD, BRL.
- -If you have an acronym and want to spell it out in the text, please write the spelled-out form followed by the acronym in parentheses.
-Examples:
-Avoid using gerunds. Prefer the infinitive form, or change the verb to a noun.
+For Education texts, it’s common to see the gerund in English and a “How to” in Portuguese.
+Example:
+English (source): “Implementing the strategy”
+Portuguese: “Implementar a estratégia”, “Implementação da estratégia”, or “Como implementar a estratégia” (preferred for Education)
+ +The indirect object must always be linked to the verb by a preposition. This also applies to cases in which there is more than one direct object. Make sure your sentences are synthetically parallel.
+Examples:
+Incorrect: Esse cenário apresenta vantagens para o usuário, já que ele permite explorar o catálogo, inventário e preços com liberdade, conforme seu perfil de acesso.
+Correct: Esse cenário apresenta vantagens para o usuário, já que ele permite explorar o catálogo, o inventário e os preços com liberdade, conforme seu perfil de acesso.
+Incorrect: [...] problemas de negócio específicos relacionados à usabilidade da loja, vendas e pós-vendas.
+Correct: (option 1) [...] problemas de negócio relacionados a usabilidade da loja, vendas e pós-vendas. (option 2) [...] problemas de negócio relacionados à usabilidade da loja, às vendas e ao pós-vendas.
+ +For the 12-hour format, use the abbreviation in lowercase with dots. Add a space between the hour and the abbreviation. For the 24-hour format, use the hour unit (h) between the hour and the minutes, without spaces. Zeroed minutes are not required.
+For indicating time zones, use the format (GMT) in front of the hour.
+Examples: 6 p.m. (GMT-3), 10:30 a.m., 14h30, 16h
+ +Dates should be written as follows:
+22 de outubro de 2021, or 22/10/21 (day, month, year)
+ +For illustrative examples, as in Help Center: You can localize the examples that are given in another currency other than reais. Check if the context allows it.
+For precise data in general: You can either use US$ for dollars (preferred) or only the number followed by “dólares”.
+The abbreviation for real is R$. There must always be a space between the abbreviation and the number.
+In Storefront or apps used by other people (such as end customers, and pickers and couriers in Pick and Pack and Last Mile) than the Admin, use the standard R$.
+In Admin labels (technical context), prefer the 3-letter ISO format: USD, BRL.
+ +If you have an acronym and want to spell it out in the text, please write the spelled-out form followed by the acronym in parentheses.
+Examples:
+In the case of acronyms with more than 3 letters that can be read as a word, only the first letter is capitalized. For example, you should write Covid-19, Unesco, Aids. When it's an acronym that requires reading letter by letter, capitalize all the letters, as in FGTS.
-Job titles, especially internal, are kept in English if they are an acronym or noun and adjective. If they include the preposition “of” or “at,” the preposition is translated.
-If the job title is widely used in Portuguese, you may consider translating it but keeping the team name/area (if any) in English.
-Examples: Head de Sales, Customer Success Manager, Diretor de Marketing
-Internal team names and departments are not translated.
-Examples: Customer Success, Growth, Product
-In marketing texts, you may have to translate sayings, proverbs, or other typical expressions centered in the source language and that do not make sense if literally translated to Portuguese. In those cases, you should search for an equivalent that keeps the sentence’s intended meaning.
-Examples:
-English: “Early shoppers get the worms”
-Portuguese: “Deus ajuda os compradores que cedo madrugam”
-English: “Born omnichannel”
-Portuguese: “Omnichannel de berço”
- -If you cannot find an equivalent, just translate and adapt the sentence, keeping the intended meaning in Portuguese.
-When translating from English, the gender of the word may not always be clear. If you are unsure which gender to choose when using articles, for example, you can search out TMs on Crowdin or ask a team member. Sometimes, people tend to use inconsistent articles/genders for the same word, so please avoid that.
-Examples:
-In the case of acronyms with more than 3 letters that can be read as a word, only the first letter is capitalized. For example, you should write Covid-19, Unesco, Aids. When it's an acronym that requires reading letter by letter, capitalize all the letters, as in FGTS.
+Job titles, especially internal, are kept in English if they are an acronym or noun and adjective. If they include the preposition “of” or “at,” the preposition is translated.
+If the job title is widely used in Portuguese, you may consider translating it but keeping the team name/area (if any) in English.
+Examples: Head de Sales, Customer Success Manager, Diretor de Marketing
+ +Internal team names and departments are not translated.
+Examples: Customer Success, Growth, Product
+ +In marketing texts, you may have to translate sayings, proverbs, or other typical expressions centered in the source language and that do not make sense if literally translated to Portuguese. In those cases, you should search for an equivalent that keeps the sentence’s intended meaning.
+Examples:
+English: “Early shoppers get the worms”
+Portuguese: “Deus ajuda os compradores que cedo madrugam”
+English: “Born omnichannel”
+Portuguese: “Omnichannel de berço”
+If you cannot find an equivalent, just translate and adapt the sentence, keeping the intended meaning in Portuguese.
+ +When translating from English, the gender of the word may not always be clear. If you are unsure which gender to choose when using articles, for example, you can search out TMs on Crowdin or ask a team member. Sometimes, people tend to use inconsistent articles/genders for the same word, so please avoid that.
+Examples:
+As Portuguese is a gender-marked language, unlike English, avoid assuming the gender in situations in which you can be more gender-neutral.
-Examples:
-English: “The secretaries…”
-Portuguese: Use “As pessoas que trabalham na secretaria…” instead of “As secretárias...”
- -English: “Welcome to…”
-Portuguese: “Boas-vindas a…” or “Bem-vindo(a) a…” instead of “Bem-vindo a…”
- -Whenever referring to people with disabilities, you should always use: "pessoa com deficiência".
-
- For IBGE, black people correspond to the sum of "pretos" and "pardos". And the nomenclature that you should use is "pessoas negras", which encompass both forms.
See more information on inclusion here.
-If by any chance, the UI mentioned in the article you are translating is not localized in the Admin, you should check with our Localization Engineers if they are localizable. If yes, open a task on JIRA requesting it. If not, write the UI in bilingual format in your translation. The bilingual format must be indicated with the word that appears currently in the Admin followed by the translation in parentheses. For example: Clique no botão “Add” (adicionar).
- -When localizing content for a broader audience, it is important to consider the regional differences in terminology. In Brazil, the term "CEP" (Código de Endereçamento Postal) is widely used to refer to the postal code system established by Correios, the national postal service. On the other hand, in Portugal and other Portuguese-speaking countries, the term "postal code" is more commonly used.
-To provide a more localized experience and cater to the preferences of our primary customer base in Brazil, we usually opt to use "CEP" when translating and localizing content. This ensures that our platform aligns with the familiar terminology used by Brazilian users. However, when addressing a broader Portuguese-speaking audience, such as Portugal, and especially through our Checkout, we prioritize the use of "postal code" for better localization.
-To address both scenarios for our clients' end customers, for Checkout, we have created separate folders in our localization management system, Crowdin, one for PT-BR and another one for PT-PT. In the "PT-BR" folder we used "CEP", while in the "PT-PT" folder we used "postal code".
- -In the past, product names were defined in collaboration with the Product Marketing team. However, they are no longer directly involved in naming decisions. The responsibility for product name localization now lies with the Localization team in collaboration with Product Managers, as well as Designers and Education. The Localization team ensures that product names are accurately translated and localized to resonate with the target audience.
-If you're asking yourself if we should translate product names, the answer is not definitive: it depends. We consider several factors to make an informed decision, including brand consistency, linguistic and cultural adaptation, market familiarity, legal and trademark considerations, user experience and ease of understanding, marketing and advertising strategies, etc.
-When localizing Admin module names, our general practice is to adapt them to the target language unless they contain highly technical terms that are better known in English, even among speakers of other languages. In such cases, we may retain the English module names to ensure clarity and ease of understanding for users. For app names, we tend to keep them in English.
-If translated, the capitalization of product names will follow the standard conventions of each language. For example, in Portuguese (PT), product names will be written in sentence case, while in English (EN), they will be written in Title Case. If kept in English, the capitalization of product names will follow the English capitalization rules.
-Examples:
-English: Dashboards > Sales Performance
-Portuguese: Dashboards > Performance de vendas
- -English: Promotion Simulator
-Portuguese: Simulador de promoções
- -English: Extensions Hub
-Portuguese: Hub de extensões
- -English: VTEX Pick and Pack
-Portuguese: VTEX Pick and Pack
- -English: Intelligent Search > Analytics
-Portuguese: Intelligent Search > Analytics
- - - - - - - -Admin/Stores: Different Admin versions are available. Please always confirm with the writer which store they used as a reference. Here are two main ones: cosmetics2 (Admin V3), storecomponents (Admin V4).
- -VTEX Admin string standardization in Portuguese
- -Manual de estilo e redação (maintained by Thalita Uba, in Content Enablement/Growth)
- -https://uxwriting.vtex.com/ (applies mainly for EN UI, but some sections can be used for PT too).
- -Internal
-VTEX Glossary (maintained by Localization)
- -Marketing glossary (discontinued, the relevant terms were added to VTEX Glossary)
- -External
- - -IATE - European Union terminology
- - -Marketing Localization Guidelines
- -VOLP (Vocabulário Ortográfico da Língua Portuguesa pela Academia Brasileira de Letras)
-Priberam (focus on European Portuguese, but also has a part for Brazilian Portuguese)
- -CUNHA, Celso e CINTRA, Lindley. Nova Gramática do Português Contemporâneo. Rio de Janeiro: Editora Nova Fronteira.
-Cartilha Tem hífen?
- -LanguageTool (Grammar and spell checker)
- -As Portuguese is a gender-marked language, unlike English, avoid assuming the gender in situations in which you can be more gender-neutral.
+Examples:
+English: “The secretaries…”
+Portuguese: Use “As pessoas que trabalham na secretaria…” instead of “As secretárias...”
+English: “Welcome to…”
+Portuguese: “Boas-vindas a…” or “Bem-vindo(a) a…” instead of “Bem-vindo a…”
+Whenever referring to people with disabilities, you should always use: "pessoa com deficiência".
+For IBGE, black people correspond to the sum of "pretos" and "pardos". And the nomenclature that you should use is "pessoas negras", which encompass both forms.
+See more information on inclusion here.
+ +If by any chance, the UI mentioned in the article you are translating is not localized in the Admin, you should check with our Localization Engineers if they are localizable. If yes, open a task on JIRA requesting it. If not, write the UI in bilingual format in your translation. The bilingual format must be indicated with the word that appears currently in the Admin followed by the translation in parentheses. For example: Clique no botão “Add” (adicionar).
+ +When localizing content for a broader audience, it is important to consider the regional differences in terminology. In Brazil, the term "CEP" (Código de Endereçamento Postal) is widely used to refer to the postal code system established by Correios, the national postal service. On the other hand, in Portugal and other Portuguese-speaking countries, the term "postal code" is more commonly used.
+To provide a more localized experience and cater to the preferences of our primary customer base in Brazil, we usually opt to use "CEP" when translating and localizing content. This ensures that our platform aligns with the familiar terminology used by Brazilian users. However, when addressing a broader Portuguese-speaking audience, such as Portugal, and especially through our Checkout, we prioritize the use of "postal code" for better localization.
+To address both scenarios for our clients' end customers, for Checkout, we have created separate folders in our localization management system, Crowdin, one for PT-BR and another one for PT-PT. In the "PT-BR" folder we used "CEP", while in the "PT-PT" folder we used "postal code".
+ +In the past, product names were defined in collaboration with the Product Marketing team. However, they are no longer directly involved in naming decisions. The responsibility for product name localization now lies with the Localization team in collaboration with Product Managers, as well as Designers and Education. The Localization team ensures that product names are accurately translated and localized to resonate with the target audience.
+If you're asking yourself if we should translate product names, the answer is not definitive: it depends. We consider several factors to make an informed decision, including brand consistency, linguistic and cultural adaptation, market familiarity, legal and trademark considerations, user experience and ease of understanding, marketing and advertising strategies, etc.
+When localizing Admin module names, our general practice is to adapt them to the target language unless they contain highly technical terms that are better known in English, even among speakers of other languages. In such cases, we may retain the English module names to ensure clarity and ease of understanding for users. For app names, we tend to keep them in English.
+If translated, the capitalization of product names will follow the standard conventions of each language. For example, in Portuguese (PT), product names will be written in sentence case, while in English (EN), they will be written in Title Case. If kept in English, the capitalization of product names will follow the English capitalization rules.
+Examples:
+English: Dashboards > Sales Performance
+Portuguese: Dashboards > Performance de vendas
+English: Promotion Simulator
+Portuguese: Simulador de promoções
+English: Extensions Hub
+Portuguese: Hub de extensões
+English: VTEX Pick and Pack
+Portuguese: VTEX Pick and Pack
+English: Intelligent Search > Analytics
+Portuguese: Intelligent Search > Analytics
+ +Admin/Stores: Different Admin versions are available. Please always confirm with the writer which store they used as a reference. Here are two main ones: cosmetics2 (Admin V3), storecomponents (Admin V4).
+ +VTEX Admin string standardization in Portuguese
+ +Manual de estilo e redação (maintained by Thalita Uba, in Content Enablement/Growth)
+ +https://uxwriting.vtex.com/ (applies mainly for EN UI, but some sections can be used for PT too).
+ +Internal
+VTEX Glossary (maintained by Localization)
+ +Marketing glossary (discontinued, the relevant terms were added to VTEX Glossary)
+External
+ + +IATE - European Union terminology
+ +Marketing Localization Guidelines
+ +VOLP (Vocabulário Ortográfico da Língua Portuguesa pela Academia Brasileira de Letras)
+Priberam (focus on European Portuguese, but also has a part for Brazilian Portuguese)
+ +CUNHA, Celso e CINTRA, Lindley. Nova Gramática do Português Contemporâneo. Rio de Janeiro: Editora Nova Fronteira.
+Cartilha Tem hífen?
+ +LanguageTool (Grammar and spell checker)
+ +
