Top 10 Tips for Microsoft Translation into Portuguese (Brazil)
Are you helping with translation into Portuguese (Brazil) but don't have time to study all aspects of the Microsoft Portuguese (Brazil) Style Guide? Here are ten of the most important aspects to keep in mind.
1. Readability and fluency
The language in Microsoft products should have the "feel" of a product originally written in Portuguese (Brazil), using idiomatic syntax and terminology, while maintaining a high level of terminological consistency. That guarantees the maximum user experience and usability for our customers. Sticking too closely to the original text will make it sound unnatural. Focus on readability and fluency, ensuring that Microsoft products are intuitive, easy to understand, and aligned with market usage in Brazil.
Try to understand the whole intention of the sentences, paragraphs, and pages, and then rewrite just like you are writing the contents yourselves.
English: Upload your video, and go
Not our style: Carregue o seu vídeo e vá
Our style: Carregue o seu vídeo rapidamente
English: Keep track of your friends' and family's special days.
Not our style: Controle as datas especiais dos amigos e da família.
Our style: Lembre-se dos aniversários de seus amigos e familiares.
2. Friendly and conversational tone
Microsoft's brand personality comes through in our voice and tone: what we say and how we say it. Microsoft voice targets a broad set of users from technology enthusiasts and casual computer users. Translating Microsoft voice into Brazilian Portuguese means choosing words and grammatical structures that reflect the same style as the source text. It also means considering the needs of the audience and the intent of the text. In general, the style should be clear and friendly. Use language that resembles conversation observed in everyday settings as opposed to the formal, technical language that is often used for technical and commercial content.
English: Stay in the know. Turn on desktop notifications.
Our style: Fique por dentro. Ative as notificações da área de trabalho.
Shorter is always better. Lengthy strings of text can cause issues for localization. Be concise, without sounding robot-like. Use short, simple words. Abbreviations should be avoided as much as possible because they can make the text less intuitive.
English: Would you like to continue?
Our style: Quer continuar?
English: Have some fun with friends and invite them to play one of the many games online.
Our style: Convide seus amigos para jogar online.
4. Application, product, and feature names
Trademarked names and the name Microsoft Corporation shouldn't be localized unless local laws require translation and an approved translated form of the trademark is available. A list of Microsoft trademarks is available for your reference.
Application and product names that are not descriptive names are often trademarked or can potentially be trademarked in the future. These names, therefore, are rarely translated. Occasionally, feature names that aren't descriptive are trademarked, too (for example, IntelliSense). Before translating application, product, or feature names, check the full style guide or contact the Microsoft team.
When an application or product name contains a preposition, it's recommended that you translate the preposition, unless there are specific trademark or copyright instructions preventing the translation
Trademarked product name that contains a preposition
English: Microsoft Visio Pro for Office 365
Our style: Microsoft Visio Pro para Office 365 (Visio and Office 365 are Microsoft trademarks; the preposition is translated.)
Descriptive feature name English: File Plan Manager
Our style: Gerenciador de Planos de Arquivos (The feature name is translated, as it is descriptive and it is not trademarked.)
Trademarked feature name
Our style: Cortana (Cortana is not a descriptive feature name and is trademarked.)
5. Handling acronyms
Acronyms are words made up of the initial letters of major parts of a compound term. Some well-known examples are DNS (Domain Name Server) and HTML (Hypertext Markup Language).
Translate When the usage of the English acronym isn't widespread among the Brazilian audience of the product, the general recommendation is to use the spelled-out form instead.
English: Time Series Insights (LTS)
Our style: Time Series Insights (armazenamento a longo prazo) (The spelled-out form is much more user friendly and intuitive than the acronym.)
Don't translate Most technical acronyms aren't translated because they are known by the target audience in Brazil in English. The localized, spelled-out form should follow the acronym the first time that the acronym appears (space permitting). In the subsequent occurrences, only the acronym should be used.
Note For protocol names, file formats, and well-established acronyms, don't add the spelled-out form because the spelled-out form is rarely used.
English: The IR is the compute infrastructure used by Azure Data Factory to provide the following data integration capabilities across different network environments.
Our style: O IR (tempo de execução de integração) é a infraestrutura de computação usada pelo Azure Data Factory para fornecer as seguintes funcionalidades de integração de dados entre diferentes ambientes de rede. (This is first time the acronym is used in the page.)
English: Graphic Interchange Format (.gif)
Our style: formato GIF
The English language tends to use title-case capitalization a lot. When localizing Microsoft products, the standard capitalization rules for Brazilian Portuguese should be followed except for software strings. (For more details, see the following section, "Capitalization of UI strings.")
Follow a guided learning path to build practical job skills you can start using right away.
Roteiros de aprendizagem
Siga um roteiro de aprendizagem guiado para desenvolver habilidades de trabalho práticas e começar a usá-las imediatamente.
Capitalization of topic tiles in Brazilian Portuguese is sentence case, therefore, **R**oteiros de **a**prendizagem.
Capitalization of UI strings
The source (English) capitalization is followed when translating UI labels. In some cases, this may sound unnatural for the Portuguese language, but the text in the user interface is different from other kinds of text because it's composed of strings that often have to be translated outside the context in which they appear. This rule is adopted for localization simplicity.
English: Clean Up Folder
Our style: Limpar Pasta
Note: This rule doesn't apply to error messages. Normally, the source text uses sentence case in error messages, but it's not rare to see error messages using title-case capitalization in the source files. For Brazilian Portuguese, sentence case should be used in error messages.
English: Failed to Report Event
Our style: Falha ao relatar evento
The use of personal pronouns is a powerful way to express all the attributes of the Microsoft voice. The user is addressed directly through the use of first- and second-person pronouns such as "you." Third-person references, such as "user," are avoided as they sound formal and impersonal. When translating into Brazilian Portuguese, address the user as você instead of usuário or converting the sentence to passive voice.
Avoid repeating pronouns in a sentence. In Brazilian Portuguese, omitting some pronouns when the meaning is clear from the context makes the text sound more natural.
English: Depending on your service agreement, you might pay more for call or text messages when your phone is roaming.
Our style: Dependendo do contrato de serviço, você pode pagar mais por ligações ou SMS quando o telefone estiver em roaming.
Don't overuse the subjunctive mode When translating sentences that contain "Make sure" or "Ensure", it is very common to see stiff translations using the subjunctive.
English: Make sure to run Windows Update.
Our style: Não deixe de executar o Windows Update.
Avoid gerunds The gerund shouldn't be used to express the notion of progressive future, as it is commonly used in English.
English: :::no-loc text="With the new Azure Monitor service in place, we will be retiring the "classic" monitoring and alerting platform.":::
Our style: :::no-loc text="Com o novo serviço do Azure Monitor pronto, descontinuaremos a plataforma de monitoramento e alerta "clássicos".":::
Follow the standard punctuation rules used in Brazilian Portuguese. To promote a consistent style within Microsoft products, follow these guidelines:
UI strings Include the final periods if they're used in the source text because you can't foresee how the strings will combine at runtime.
Bulleted lists Items composed of a full sentence end with a period. Items not composed of a full sentence have no period.
Colons Don't capitalize common words after a colon.
English: NOTE: This purchase can't be charged to your mobile phone account. A different payment method has been selected.
Our style: OBSERVAÇÃO: esta compra não pode ser debitada na conta do seu celular. Um outro método de pagamento foi selecionado.
Commas English and Brazilian Portuguese don't share the same rule for the use of commas in a list of three or more items. In English, a comma should be included before the conjunction. In Brazilian Portuguese, there is no comma before the conjunction.
English: Sync your mail, contacts, calendar, and tasks
Our style: Sincronizar seus emails, contatos, calendários e tarefas
10. Use the right reference material
There is more, of course. If you are in doubt, consult the terminology, translation, and full Microsoft Portuguese (Brazil) Style Guide, and the following references:
- Academia Brasileira de Letras. Vocabulário Ortográfico da Língua Portuguesa, 5ª edição, 2009
- Cunha, Celso e Cintra, Lindley. Nova Gramática do Português Contemporâneo. Rio de Janeiro: Editora L&PM, 2ª edição, 2009
- Ferreira, Aurélio Buarque de Holanda. Novo Dicionário da Língua Portuguesa.Rio de Janeiro: Editora Positivo; 5ª edição, 2010
- Instituto Antônio Houaiss. Dicionário Houaiss da Língua Portuguesa–Com a Nova Ortografia. Rio de Janeiro: Objetiva, 2009