Translating using Weblate¶
Thank you for your interest in translating with Weblate! If you are new here, follow Make your first translation for a guided first contribution.
Generally, there are two most used modes of translation:
Il progetto accetta traduzioni dirette
Project accepts the suggestions made by users.
Sometimes, anonymous suggestions are accepted as well.
There are more translation workflows detailed in Translation workflows.
Projects, or the components in them are either visible to everyone, or only to a certain group of translators.
Vedi anche
Progetti traduzione¶
Translation projects hold related components; resources for the same software, book, or project.
Translation links¶
Having navigated to a component, a set of links lead to its actual translation. The translation is further divided into individual checks, like Untranslated strings or Unfinished strings. If the whole project is already translated without any errors, All strings is still available. Alternatively you can use the Search feature to find a specific string or term.
Suggerimenti¶
Nota
Actual permissions might vary depending on your Weblate configuration.
Anonymous users (by default) can only forward suggestions. Doing so is still available to signed-in users, in cases where uncertainty about a translation arises, prompting other translators to review it. Any user can clone an existing suggestion into the translation fields, including plural forms, and use it as the basis for a new suggestion or translation.
All suggestions are scanned on a daily basis to remove duplicates and those matching current translations.
If you have the Accept suggestions permission, you can bulk accept all suggestions from a specific user by clicking the account check icon next to their suggestion. This is useful for quickly processing suggestions from trusted contributors. Suggestions failing quality checks are skipped and remain for manual review. Weblate shows the number of matching suggestions for confirmation and processes the acceptance in the background. If you can review the translation, you can accept and approve the suggestions in the same step.
Bulk acceptance selects suggestions from that user only for the current language in the current component. It does not select suggestions in other languages or components, even within the same project. For example, when translating a component into French, bulk acceptance selects only that user’s French suggestions in that component.
Varianti¶
Variants are used to group different-length variants of a string. The frontend of your project can then utilize different strings depending on the size of a screen or window.
Vedi anche
Etichette¶
Labels are used to categorize strings within a project to further customize the localization workflow (for example to define categories of strings).
Weblate utilizza le seguenti etichette:
- Tradotto automaticamente
Stringa tradotta utilizzando Traduzione automatica.
- La sorgente necessita di revisione
Stringa contrassegnata per la revisione utilizzando Source strings reviews.
Vedi anche
Translating¶
On the translation page, the source string and an editing area for its translation are shown. Should the translation be plural, multiple source strings and editing areas are shown, each described and labeled in the amount of plural forms the translated language has.
The labels include example counts for each plural form. A range such as
10–20 includes both endpoints. If the editor shortens the list to fit,
open the translation’s Overview tab to see all the selected examples.
Special whitespace characters are marked in red and indicated with grey symbols. Consecutive spaces are also marked in red to flag a potential formatting issue. Long runs of spaces in displayed strings share a single outline. The editor uses plain text for long translations and restores highlighting when the text is shortened.
Various bits of extra info can be shown on this page, most of which coming from the project source code (like context, comments or where the message is being used). Translation fields for any secondary languages translators select in the preferences will be shown (see Lingue secondarie) above the source string.
Below the translation, translators will find suggestions made by others, to be accepted (✓), accepted with changes (✏️), bulk accepted for a specific user (👤✓), cloned into the translation fields (📑) or deleted (🗑).
Translating special text safely¶
Some source strings contain text that the application interprets at runtime. Translate the human-readable parts, but keep technical markers intact unless the project instructions say otherwise.
- Placeholders and format strings
Keep variables such as
%s,%1$d,%(name)s,{count},{{ value }}, or similar markers in the translation. Named placeholders describe the inserted value, but the names themselves are not translated. You can usually reorder numbered or named placeholders to fit the target language. Use the placeable copy shortcuts to insert them without typing mistakes.- Markup
Keep HTML and XML tags, tag names, and attribute names unchanged. Translate the visible text between tags and any attribute value that is meant for users, for example alternative text or a tooltip, when it appears as part of the translatable string. Make sure opening and closing tags still match after reordering the sentence.
- Program syntax
Leave function names, commands, environment variables, spreadsheet functions, SQL keywords, and similar program syntax untranslated unless the project explicitly documents a localized form.
- Punctuation and whitespace
Preserve punctuation and spaces that affect the interface, such as trailing colons, ellipses, leading or trailing spaces, and punctuation next to placeholders. Follow the target language’s typography when it differs from the source, and use comments when a source punctuation choice looks wrong.
- Accelerators
Menu labels can mark keyboard accelerators with characters such as
&,_, or~. When the source has an accelerator, keep one in the translation. Choose a readable key in the translated label and avoid obvious conflicts with nearby menu items or buttons.- Plural forms
Translate each plural field Weblate shows. Do not combine forms into a single construction such as
file(s)unless that is correct for the target language and project. If the source string uses an ambiguous plural, report it with a source string comment or review.
Weblate quality checks catch many technical mistakes in placeholders, markup, punctuation, whitespace, and plural forms. They do not replace translator judgment, so use Contesto di traduzione, Glossario, and Commenti when the source text needs clarification.
Vedi anche
Editing source strings and keys¶
When Gestione stringhe is enabled and you have permission to edit source strings, choose Tools → Edit source in the translation editor. You can open this dialog from any language. Changes apply to the source string and its existing translations within the component.
The dialog lets you change the source text, supported key or context, and source explanation. Existing translations, history, comments, labels, and suggestions are retained. Changing source text marks existing translations as needing editing. Changing only the key, context, or explanation preserves their states. Renaming a key may require corresponding changes in your application code. New and renamed keys must be representable in the file format and its encoding. For example, PHP keys must use supported variable or array syntax, properties keys cannot introduce additional entries, and DTD keys must be XML names.
Changes are written to translation files through the normal pending-change queue and follow the project’s commit policy. Keys used by pending edits remain reserved until those edits are written. Weblate rejects collisions rather than merging strings. Reload the editor if another user has changed the source since you opened the dialog.
Source editing supports PO, TBX, plain XLIFF 1.2, XLIFF 2.0, and Apple XLIFF. Key editing supports JSON (plain, nested, ARB, WebExtension, and i18next), YAML, Ruby YAML, TOML, Go-i18n TOML, Java properties, GWT, PHP, DTD, Android, RESX, and simple Fluent messages. These monolingual formats also support source-text editing. PO contexts and TBX keys are editable; composite XLIFF keys are not.
YAML and TOML keys can be renamed within their existing mapping, but cannot be moved between mappings or renamed inside arrays. Editing source text with unsupported inline markup, changing the number of plural forms or terminology alternatives, and editing components with an intermediate language file are not supported.
Plurali¶
Words changing form to account for their numeric designation are called plurals. Each language has its own definition of them. English, for example, supports one. In the singular definition of an example «car», implicitly one car is referenced, in the plural definition of «cars», two or more cars are referenced (or the concept of cars as a noun). Languages like, for example, Czech or Arabic have more forms of plurals, and their rules for plurals are different as well.
Weblate has full support for each of these forms, in each respective language. Each grammatical number is translated in a separate field for a pre-defined set of cardinal numbers specific to the translation language. The number of fields and how they are in turn used in the translated application or project, depends on the configured plural formula. Weblate shows the basic information and the Language Plural Rules by the Unicode Consortium is a more detailed description.
Vedi anche
Traduzioni alternative¶
Added in version 4.13.
Nota
This is currently only supported with File CSV multivalore.
With some formats, it is possible to have more translations for a single string. You can add more alternative translations using the Tools menu. Any blank alternative translations will be automatically removed upon saving.
Tasti rapidi¶
The following keyboard shortcuts can be utilized during translation:
Scorciatoie da tastiera |
Descrizione |
|---|---|
? |
Apri le scorciatoie da tastiera disponibili. |
Alt+Home |
Vai alla prima traduzione nella ricerca attuale. |
Alt+End |
Vai all’ultima traduzione nella ricerca attuale. |
Alt+PageUp or Ctrl+↑ or Alt+↑ or Cmd+↑ |
Vai alla traduzione precedente nella ricerca attuale. |
Alt+PageDown or Ctrl+↓ or Alt+↓ or Cmd+↓ |
Vai alla successiva traduzione nella ricerca attuale. |
Ctrl+Enter or Cmd+Enter |
Submit current form; this is same as pressing Save and continue while editing translation. |
Ctrl+Shift+Enter or Cmd+Shift+Enter |
Rimuovi il contrassegno «Traduzione da modificare» e inviala. |
Ctrl+Alt+Enter or Cmd+Alt+Enter |
Approve the translation and save and continue. Only available to reviewers. |
Alt+Enter or Option+Enter |
Submit the string as a suggestion; this works the same as pressing Suggest while editing translation. |
Ctrl+E or Cmd+E |
Focus sull’editor di traduzione. |
Ctrl+U or Cmd+U |
Focus sull’editor dei commenti. |
Ctrl+M or Cmd+M |
Shows Automatic suggestions tab, see Suggerimenti automatici. |
Ctrl+1 to Ctrl+9 or Cmd+1 to Cmd+9 |
Copia i posizionabili di un dato numero dalla stringa sorgente. |
Ctrl+M followed by 1 to 9 or Cmd+M followed by 1 to 9 |
Copia la traduzione automatica di un dato numero nella traduzione attuale. |
Ctrl+I followed by 1 to 9 or Cmd+I followed by 1 to 9 |
Ignorare un elemento nell’elenco dei controlli non riusciti. |
Ctrl+J or Cmd+J |
Mostra la scheda stringhe adiacenti. |
Ctrl+S or Cmd+S |
Focus sul campo di ricerca. |
Ctrl+O or Cmd+O |
Copia la stringa sorgente. |
Ctrl+Y or Cmd+Y |
Commuta la casella Needs editing. |
→ |
Sfoglia la stringa di traduzione successiva. |
← |
Sfoglia la stringa di traduzione precedente. |
Visual keyboard¶
A small visual keyboard row is shown just above the translation field. Its rows are specific to each language; it can be useful for local punctuation or characters that are hard to type by hand.
The shown symbols factor into three categories:
User configured Caratteri speciali defined in the Profilo utente
Per-language characters provided by Weblate (e.g. quotes or RTL-specific characters)
Characters configured using
SPECIAL_CHARS
Contesto di traduzione¶
This contextual description provides related info about the current string.
- Last translator and last approver
If you can view contributor identities, String information shows who last changed the translation text. For approved strings, it also shows who approved the current translation when the reviewer is known.
- String attributes
Things like message ID, context (
msgctxt) or location in source code.- File di traduzione
Where the string appears in the component translation file; when the format provides a line number, Weblate shows it and uses it for repository links when available. Without a line number, the string index in the file is shown.
- Spiegazione
Further clarification can be provided in Weblate via Spiegazione.
- Screenshot
Screenshots can be uploaded directly from this panel using Upload screenshot, or linked using Add existing screenshot to show where and how the string is used. Source-language screenshots are shown for every translation of the string, while translation-specific screenshots are shown only for that translation; see Screenshots and visual context.
- Stringhe vicine
Displays neighbouring strings from the translation file. When the format provides a line number, neighbours are the surrounding strings in file order; otherwise they are the surrounding string indexes. These are usually also used in a similar context and prove useful in keeping the translation consistent.
- Altre ricorrenze
In case a message appears in multiple places (e.g. multiple components), this tab shows all of them if they are found to be inconsistent (see Incoerente). You can choose which one to use.
- Memoria traduzione
Look at similar strings translated in past, see Memoria traduzione.
- Glossario
Displays terms from the project glossary used in the current message.
- Cronologia
List of people whom have changed this message recently using Weblate.
- Progetto
Project info like instructions for translators, or a directory or link to the string in the version control system repository the project uses.
If you want direct links, the translation format has to support it.
Adding an existing screenshot¶
To link a screenshot that has already been uploaded, open the string in the translation editor:
In the Screenshots panel, choose Add existing screenshot.
Browse the thumbnails, or enter a query in Search screenshots and choose Search. Use Previous and Next to browse additional results.
Select a screenshot by clicking its card. The card is highlighted and marked Selected. To select with a keyboard, press Tab to reach the cards, use the arrow keys to move between them, and press Space to select a card.
Choose Add screenshot. The editor reloads on the same string and displays the associated screenshot in the Screenshots panel.
The picker shows screenshots from the current component in the source language or the current translation language. A source-language screenshot is linked to the source string and shown for every translation. A translation-language screenshot is shown only for that language. Screenshots already linked to the string are excluded from the picker.
This action requires the Edit screenshot permission. To upload a new image, use Upload screenshot instead. Use Manage screenshots for the full screenshot management interface.
Translation history¶
Every change is by default (unless turned-off in component settings) saved in the database, and can be reverted. Optionally, translations can also be reverted in the underlying version control system.
Each change shows an origin badge next to the username: Web, API, Repository, or System. Changes made by automation identify the installed add-on and its execution log in the tooltip of an Automation origin badge. Hover over a badge or focus it with the keyboard to see an explanation of the origin. Session-authenticated API requests, including requests from the editor, count as web actions. Token-authenticated requests count as API actions. Strings imported from a repository count as repository changes, while uploads retain their web or API origin. Background tasks inherit the initiating origin; unrelated background work uses system. Historical changes without recorded origin have no badge.
Origin badges are visible to anyone who can view the change. Superusers also see an IP address badge when an address was recorded. Origin metadata is also available through the API to users who can access the change.
In the changes browser, use Older and Newer to browse history, or Latest to return to the newest matching changes. Jump to date starts with the latest changes on or before the selected date. You can then browse in either direction, keeping your search filters. Use Date range to restrict results to a particular period.
CSV downloads and RSS feeds use the search filters, not your browsing position or jump date. CSV downloads contain up to 2,000 matching changes, and RSS feeds contain the latest 10. Old numbered page links open the latest matching changes.
Translated string length¶
Weblate can limit the length of a translation in several ways to ensure the translated string is not too long:
The default limitation for translation is ten times longer than the source string. This can be modified with
LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH. If you are hitting this, it can also be caused by a monolingual translation being wrongly set up as a bilingual one, making Weblate mistaking the translation key for the actual source string. See Bilingual and monolingual formats for more info.Maximum length in characters defined by the translation file or flag, as per Lunghezza massima della traduzione.
Maximal rendered size in pixels as defined by flags; see Dimensione massima della traduzione.
Suggerimenti automatici¶
Based on configuration and your translated language, Weblate provides suggestions from configured translation services, including machine translation tools and Memoria traduzione. All machine translations are available in a single tab of each translation page.
Puoi anche eseguire una ricerca di concordanza nella Memoria traduzione.
Vedi anche
You can find the list of supported tools in Translation services.
Traduzione automatica¶
You can use automatic translation to bootstrap translation based on external sources. This tool is called Automatic translation accessible in the Operations menu, once you have selected a component and a language:
A similar operation Batch automatic translation is available if you have selected a project language, a component or a category.
Only one automatic translation operation can process a component and language at a time. Background operations defer busy translations and resume them later, without repeating languages they have already completed. Synchronous API and command-line requests report an error immediately if the translation is busy.
Two modes of operation are possible:
Using other Weblate components as a source for translations.
Using selected machine translation services with translations above a certain quality threshold.
When using other components as the source, Weblate first looks for an exact match of both source text and context, including empty context. If none exists, it uses a translation matching only the source text. Context matches take precedence over source component order; component order breaks ties between equally matching candidates.
Weblate applies translations only when plural forms are compatible. If the source component uses different plural rules, pluralized strings are skipped and Weblate shows a warning, while single-form strings are still translated.
You can also choose which strings are to be auto-translated.
Avvertimento
Be mindful that this will overwrite existing translations if employed with wide filters such as All strings.
Useful in several situations like consolidating translation between different components (for example the application and its website) or when bootstrapping a translation for a new component using existing translations (translation memory).
Le stringhe tradotte automaticamente vengono etichettate Automatically translated.
Vedi anche
Rate limiting¶
To avoid abuse of the interface, rate limiting is applied to several operations like searching, sending contact forms, or translating. If affected by it, you are blocked for a certain period, until you can perform the operation again.
Default limits and fine-tuning are described in the administrative manual, see Rate limiting.
Cerca e sostituisci¶
Search and replace is part of Modifica collettiva. Use it to change terminology or fix matching translations, with literal text or regular expressions.
Modifica collettiva¶
Bulk editing allows performing one operation for multiple strings. Define strings by searching for them and actions to perform on matching ones. Flag and label changes are grouped by what they affect, with separate Add flags and Remove flags fields for each flag group. Supported operations:
Modificare lo stato della stringa (ad esempio per approvare tutte le stringhe non revisionate).
Clear translations by setting the state to Empty.
Replace text, including regular expressions and captured groups.
Adjust source-wide or language-specific translation flags (see Customizing behavior using flags)
Adjust string labels (see String labels)
Source flag and label operations affect all languages of matching strings.
Translation flag operations affect only matching translations and skip source
strings. Removing translation flags removes local values; inherited flags
remain in effect. To mark matching translations read-only, add read-only
using Add flags in the Translation flags section.
Suggerimento
This tool is called Bulk edit, accessible in the Operations menu of each project, component or translation.
Text replacement uses the strings matched by the search query or your selection. Choose Text for case-sensitive literal replacement, or Regular expression for a pattern. Leave Search string empty to disable replacement. An empty Replacement string removes matching text. Spaces and newlines in the fields are preserved, and each plural form is processed separately. The usual translation autofixes still apply. Strings where the replaced text would exceed the length limit of the translation editor are left unchanged, and the preview and result report how many were skipped.
Regular expression replacements use Python syntax: \g<1> inserts the first
captured group, \g<name> inserts a named group, and \g<0> inserts the
complete match. For example, search for (Hello), (world) and replace with
\g<2>, \g<1> to swap the words. Invalid patterns or references are rejected;
expressions that take too long to evaluate stop the operation.
Replacement can be combined with state, flag, and label changes. These other operations apply to all strings matched by the query, including strings whose text does not match the replacement pattern. Setting Empty clears all translation plural forms and cannot be combined with replacement. Source strings can be replaced when editable, but cannot be cleared. These operations require bulk-edit and edit permissions and respect read-only strings.
Each selected translation is processed independently, once per operation. Automatic propagation skips other selected translations so that their own replacement inputs are preserved. Eligible translations outside the selection can still receive propagated changes.
Preview changes is selected by default. The preview shows up to 250 changed strings, with checkboxes to choose which displayed strings to apply. Edit the parameters and choose Update preview to review a different operation. Select Apply all matching strings to process all current matches, including those not displayed. The query and permissions are checked again when applying changes. Source flag and label changes affect every language of the corresponding source, even when only one translation is selected. Uncheck Preview changes to apply directly.
Each bulk edit is limited to 20,000 matching strings. Narrow the search query if it exceeds this limit. This limit also applies to Automations and the bulk-edit add-on. Browser bulk edits run in the background and show progress after submission. The query and permissions are checked again when the task starts. The selected strings are processed in batches; if a later batch fails, earlier batches remain applied and the result reports the partial progress.
Regular expression replacement runs in a separate helper process with fixed resource limits shared across the bulk operation. Patterns and replacement strings are limited to 4096 characters each. Each plural form is limited to 1 MiB of UTF-8 input and output, and the operation can return at most 64 MiB of replacement text, including unchanged text. Literal replacement does not use this helper or these regex limits.
The helper has a cumulative CPU limit of 5 seconds and a 192 MiB address-space limit. Each match operation is limited to 0.3 seconds. The application waits at most 2 seconds per helper exchange and 10 seconds cumulatively; database work between exchanges does not count toward this waiting limit. Validation and replacement reuse the helper within one request, and components processed synchronously share its budget. A separate request or queued task gets a fresh budget.
Exceeding a limit stops regex processing and rolls back the current batch. Changes to batches completed earlier remain applied. The preview and actual execution enforce the same limits. On macOS the helper enforces time and output limits but cannot enforce the address-space limit; native regex compilation or matching can still exhaust memory there.
Vedi anche
Vista matrice¶
You can compare different languages efficiently using this view. It is available on every component page, from the Operations menu. First select all languages you want to compare, confirm your selection, then click on any translation to open and edit it.
The matrix view is also a very good starting point to find missing translations in different languages, and quickly add them from one view.
Modalità Zen¶
This mode simplifies the layout and removes additional UI elements such as Nearby strings or the Glossary. It is available by clicking the Zen button on the top-right of the regular editor (translation of a string).
You can select the Zen editor as your default editor using the Preferenze tab on your Profilo utente. You can also choose there between having translations listed Top to bottom or Side by side, depending on your personal preference.
Commenti¶
Three types of comments can be posted:
per le traduzioni
per le stringhe sorgente
for reporting source string bugs when this functionality is turned on using Abilita revisioni sorgente.
Choose the suitable type for the topic you want to discuss. Source string comments are in any event good for providing feedback on the original string, for example that it should be rephrased, or to ask questions about it.
Markdown syntax can be used in all comments, as well as mentioning other users by using
@username. Use the Preview tab above the comment field to see how the Markdown and mentions will render before posting. Mention a maintainer or another translator when you need them to see a follow-up question; they can reply in the same Comments tab.To find comments again, open your Profilo utente; the comment count links to your comment activity. To find strings with comments by a specific user, use Searching. For example,
comment_author:USERNAMEfinds strings with comments by that user, andsource_comment_author:USERNAMEfinds strings with source string comments by that user. When you are signed in, the search filter menu also includes shortcuts for comments by you and source comments by you.Vedi anche
Ricezione del feedback sulla stringa di origine
Source strings reviews
Abilita revisioni sorgente