Conceptes bàsics de la web

Project and component structure

A Weblate les traduccions s’organitzen en projectes i components. Cada projecte pot contenir un nombre de components i aquests contenen traduccions a idiomes individuals. El component correspon a un fitxer traduïble (per exemple GNU gettext PO (objecte portàtil) o Recursos de cadenes d’Android). Els projectes estan allà per ajudar-vos a organitzar el component en conjunts lògics (per exemple, per agrupar totes les traduccions utilitzades dins d’una aplicació).

A més, els components dels projectes es poden estructurar mitjançant categories. Els components poden pertànyer a una categoria i les categories es poden imbricar.

Internament, cada projecte té traduccions a cadenes comunes propagades per altres components dins d’ell per defecte. Això alleugerirà la càrrega de la traducció repetitiva i de diverses versions. La propagació de la traducció es pot desactivar per Configuració dels components utilitzant Permet la propagació de traduccions en cas que les traduccions diverguin.

Repository integration

Weblate està dissenyat per integrar-se amb el dipòsit de control de versions amunt, Localització contínua descriu els blocs de construcció i com flueixen els canvis entre ells.

Vegeu també

Architecture overview describes how Weblate works internally.

User attribution

Weblate manté les traduccions escrites correctament pels traductors al repositori de control de versions mitjançant el nom i el correu electrònic. Tenir un correu electrònic real adjunt al commit segueix els esperits de control de versions distribuïts i permet que serveis com GitHub associïn les vostres contribucions fetes a Weblate amb el vostre perfil de GitHub.

Aquesta característica també comporta el risc de fer un mal ús del correu electrònic publicat a les confirmacions de control de versions. A més, una vegada que es publica aquest compromís a l’allotjament públic (com GitHub), efectivament no hi ha manera de redactar-lo. Weblate permet escollir un correu electrònic de confirmació privat a Compte per evitar-ho.

Per tant, els administradors haurien de tenir en compte això mentre configuren Weblate:

  • Aquest ús del correu electrònic s’ha de descriure clarament en els termes del servei en cas que aquest document sigui necessari. Legal module pot ajudar amb això.

  • PRIVATE_COMMIT_EMAIL_OPT_IN pot fer que els correus electrònics siguin privats per defecte.

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

  1. 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.

  2. 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.

  3. 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.

Language settings with French selected for translation and German as a secondary language.

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 Searching to find existing translations. If your language is missing, use the option to start or request a translation when available, or contact the maintainers.

Vegeu també

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 Comentaris 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 Plurals.

French translation editor with plural forms, a missing-placeholder warning, the preferred glossary term for workspace, and a billing banner screenshot.

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 Estats de traducció and Fluxos de treball de traducció.

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 Comentaris and Receiving source string feedback.

Keep contributing

Watch projects you want to return to and choose your Notificacions. Your Tauler principal 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 Dreceres de teclat, Context de la traducció, Glossari, and Searching. The editor’s History tab shows earlier changes to a string. See Preferències for editor preferences and Descàrrega i càrrega de traduccions for downloading and uploading translations to work offline.