Básico do Weblate¶
Estrutura de projetos e componentes¶
No Weblate, as traduções são organizadas em projetos e componentes. Cada projeto pode conter vários componentes, os quais contêm traduções para idiomas individuais. O componente corresponde a um arquivo traduzível (por exemplo, GNU gettext PO (Objeto Portátil) ou Recurso de textos do Android). Os projetos estão lá para ajudá-lo a organizar componentes em conjuntos lógicos (por exemplo, para agrupar todas as traduções usadas dentro de um aplicativo).
Além disso, componentes dentro de projetos podem ser estruturados usando categorias. Componentes podem pertencer a uma categoria, e categorias podem ser aninhadas.
Internamente, cada projeto tem traduções para textos comuns propagados em outros componentes dentro dele por padrão. Isso alivia o fardo da tradução repetitiva e de várias versões. A propagação da tradução pode ser desabilitada por Configuração de componente usando Permitir propagação de tradução caso as traduções devam divergir.
Integração com repositório¶
O Weblate foi criado para integrar-se ao repositório de controle de versão upstream, Tradução contínua descreve os blocos de construção e como as alterações fluem entre eles.
Ver também
Visão geral da arquitetura descreve como o Weblate funciona internamente.
Atribuição ao usuário¶
O Weblate mantém as traduções devidamente criadas pelos tradutores no repositório de controle de versão usando nome e e-mail. Ter um e-mail real anexado ao commit segue os espíritos do controle de versão distribuído e permite que serviços como o GitHub associem suas contribuições feitas no Weblate com seu perfil do GitHub.
Esse recurso também traz o risco de uso indevido de e-mail publicado nos commits de controle de versão. Além disso, uma vez que tal commit é publicado em hospedagem pública (como GitHub), não há efetivamente nenhuma maneira de redigi-lo. O Weblate permite escolher um e-mail de commit privado em Conta para evitar isso.
Portanto, os administradores devem considerar isso ao configurar o Weblate:
Esse uso de e-mail deve ser claramente descrito nos termos de serviço, caso tal documento seja necessário. Legal module pode ajudar com isso.
PRIVATE_COMMIT_EMAIL_OPT_INpode tornar os e-mails privados por padrão.
Make your first translation¶
You can contribute to a project using your web browser. You do not need to install Weblate or work with its source code repository.
Find your project and language¶
Follow the translation link from the project you want to help. Projects can use Hosted Weblate or their own Weblate installation; use an account on that installation. If you arrive at its dashboard, choose Projects > Browse all projects to find the project.
Sign in, or follow the site’s registration instructions. Access depends on the project: you might need to request permission from its maintainers. Some projects also accept suggestions without signing in.
If you are signed in, open your user menu and choose Settings. Under Languages, select your Translated languages and, optionally, Secondary languages you understand. Secondary languages appear above the source as additional help. Save your settings. If you are contributing anonymously, skip this step and choose your language directly in the project as described below.
Read the project’s translation instructions before starting. These can explain terminology, style, priorities, and how to contact the language team. If you cannot find them, ask the maintainers which component to start with.
Choose your language and a component. A component groups related strings, such as an application’s interface or its documentation. Open Untranslated strings to start with empty translations, or Unfinished strings to include translations that still need work. Use All strings or Buscas to find existing translations. If your language is missing, use the option to start or request a translation when available, or contact the maintainers.
Translate a string¶
The editor shows the source text and a field for your translation. Read any explanation, screenshot, nearby strings, and glossary entries before writing. Short strings can have several meanings: ask in Comentários if the context is unclear. Other languages can help, but their translations can also contain mistakes.
Write a natural expression of the intended meaning in your language. Follow your language’s typography and the project’s terminology and style. Preserve technical markers such as placeholders and markup; see Translating special text safely. When Weblate displays several plural fields, complete each one according to its label; see Plurais.
Use explanations, screenshots, and glossary terms to choose the right wording.
Quality checks highlight problems such as the missing %(days)s placeholder
in this draft. The translator can edit, save, or suggest a translation.¶
Choose the action that fits your contribution:
Save and continue saves your translation and opens the next string. Use Save and stay to remain on the current string.
Mark Needs editing when saving a translation that still needs work. Clear it after you have resolved the outstanding issues.
Suggest proposes a translation for someone to accept. Use this when you want another translator to consider your wording, or when the project only allows you to suggest changes. A suggestion does not replace the current translation until it is accepted.
Skip moves on without saving your edits. You can return later.
The available actions depend on your permissions and the project’s workflow. For example, an approved translation might only allow you to suggest a change. Saving in Weblate does not mean the translation is immediately published in the application: review, repository synchronization, and releases depend on the project. See Status de tradução and Fluxos de tradução.
Check your work and ask for help¶
Read your translation again after saving. If Weblate reports failing quality checks, open their explanations and correct the problem. Ignore a check only when you have confirmed it is a false positive and your permissions allow it. Passing all checks does not guarantee that the meaning or tone is correct. Review suggestions from translation memory or machine translation just as carefully as text you write yourself.
Use a translation comment for questions about your language, or a source string comment for an unclear or incorrect original. Explain the problem and include the context you have found. If source editing or source review is available, follow the project’s instructions for proposing a correction; otherwise use its advertised contact or repository link. See Comentários and Recebendo feedback de texto fonte.
Keep contributing¶
Watch projects you want to return to and choose your Notificações. Your Painel helps you find watched translations in your selected languages. You can also help by reviewing existing translations and suggestions when your permissions allow it.
As you become familiar with the editor, explore Teclas de atalho, Contexto da tradução, Glossário, and Buscas. The editor’s History tab shows earlier changes to a string. See Preferências for editor preferences and Baixando e enviando traduções for downloading and uploading translations to work offline.