Gjëra elementare Weblate

Project and component structure

In Weblate translations are organized into projects and components. Each project can contain number of components and those contain translations into individual languages. The component corresponds to one translatable file (for example GNU gettext PO (Portable Object) or Burime vargjesh Android). The projects are there to help you organize component into logical sets (for example to group all translations used within one application).

Additionally, components within projects can be structured using categories. Components can belong to a category, and categories can be nested.

Internally, each project has translations to common strings propagated across other components within it by default. This lightens the burden of repetitive and multi version translation. The translation propagation can be disabled per Component configuration using Lejo përhapje përkthimesh in case the translations should diverge.

Repository integration

Weblate is built to integrate with upstream version control repository, Përkthim në vazhdimësi describes building blocks and how the changes flow between them.

Shihni edhe

Architecture overview describes how Weblate works internally.

User attribution

Weblate keeps the translations properly authored by translators in the version control repository by using name and e-mail. Having a real e-mail attached to the commit follows the distributed version control spirits and allows services like GitHub to associate your contributions done in Weblate with your GitHub profile.

This feature also brings in risk of misusing e-mail published in the version control commits. Moreover, once such a commit is published on public hosting (such as GitHub), there is effectively no way to redact it. Weblate allows choosing a private commit e-mail in Llogari to avoid this.

Therefore, admins should consider this while configuring Weblate:

• Such a usage of e-mail should be clearly described in service terms in case such document is needed. Legal module can help with that.

• PRIVATE_COMMIT_EMAIL_OPT_IN can make e-mails private by default.

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.

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

Shihni edhe

• Regjistrim dhe profil përdoruesi

• Lidhje përkthimi

• Limiting translation languages

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 Komente 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 Shumësa.

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 Translation states and Rrjedha pune përkthimi.

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

Keep contributing

Watch projects you want to return to and choose your Njoftime. Your Pult 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 Shkurtore tastiere, Kontekst përkthimi, Fjalorth, and Kërkim. The editor’s History tab shows earlier changes to a string. See Parapëlqime for editor preferences and Shkarkim dhe ngarkim përkthimesh for downloading and uploading translations to work offline.