Fundamentos de Weblate

Estructura de los proyectos y los componentes

En Weblate, las traducciones se organizan en proyectos y componentes. Cada proyecto puede contener varios componentes, cada uno con traducciones a idiomas individuales. El componente corresponde a un archivo traducible (por ejemplo, PO (Portable Object)de GNU gettext o Recursos de cadenas Android). Los proyectos sirven para organizar los componentes en conjuntos lógicos (por ejemplo, para agrupar todas las traducciones utilizadas en una aplicación).

Adicionalmente, los componentes internos al proyecto pueden estar estructurados utilizando categorías. Los componentes pueden a continuación pertenecer a una categoría, y las categorías pueden estar anidadas.

Internamente, cada proyecto tiene traducciones a cadenas comunes que se propagan entre sus componentes de forma predeterminada. Esto reduce la carga de traducción repetitiva y multiversión. La propagación de la traducción se puede desactivar por Configuración de componentes mediante Conceder propagación de traducciones en caso de que las traducciones diverjan.

Integración del repositorio

Weblate está diseñado para integrarse con el repositorio de control de versiones ascendente, Localización continua describe los bloques de construcción y cómo fluyen los cambios entre ellos.

Ver también

Descripción general de la arquitectura describe como funciona Weblate internamente.

Atribución al usuario

Weblate mantiene las traducciones correctamente realizadas por los traductores en el repositorio de control de las versiones utilizando el nombre y el correo electrónico. Tener un correo electrónico real adjunto al commit sigue el control de las versiones y permite a servicios como GitHub asociar tus contribuciones hechas en Weblate con tu perfil de GitHub.

Esta característica también conlleva el riesgo de que se haga un mal uso del correo-e publicado en los commits del control de versiones. Además, una vez que un commit se ha consolidado en un alojamiento público (como GitHub), no hay forma de redactarlo. Weblate permite consolidar correo-e privado en Cuenta para evitar esto.

Por lo tanto, los administradores deben tener en cuenta lo siguiente al configurar Weblate:

  • Tal uso del correo-e debe estar claramente descrito en los términos del servicio en caso de que se necesite dicho documento. Módulo legal puede ayudar con eso.

  • PRIVATE_COMMIT_EMAIL_OPT_IN puede hacer que los correos electrónicos sean privados de forma predeterminada.

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

Ver también

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 Comentarios 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 Plurales.

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 Estados de traducción and Flujos de trabajo de traducción.

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 Comentarios and Recibiendo retroalimentación de cadena origen.

Keep contributing

Watch projects you want to return to and choose your Notificaciones. Your Cuadro de mando 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 Atajos de teclado, Contexto de la traducción, Glosario, and Búsquedas. The editor’s History tab shows earlier changes to a string. See Preferencias for editor preferences and Descargar y cargar traducciones for downloading and uploading translations to work offline.