# Traducerea folosind Weblate

Thank you for your interest in translating with Weblate!
If you are new here, follow [Make your first translation](https://docs.weblate.org/ro/latest/user/basic.md#translator-start) for a guided first contribution.

Generally, there are two most used modes of translation:

* Project accepts direct translations
* Project accepts the suggestions made by users.

Sometimes, anonymous suggestions are accepted as well.

There are more translation workflows detailed in [Fluxuri de lucru de traducere](https://docs.weblate.org/ro/latest/workflows.md#workflows).

Projects, or the components in them are either visible to everyone,
or only to a certain group of translators.

#### SEE ALSO
* [Control acces](https://docs.weblate.org/ro/latest/admin/access.md#access-control)
* [Fluxuri de lucru de traducere](https://docs.weblate.org/ro/latest/workflows.md#workflows)

## Proiecte de traducere

Proiectele de traducere dețin componente conexe; resurse pentru același software, carte sau proiect.

![image](screenshots/project-overview.webp)

<a id="strings-to-check"></a>

## Link-uri de traducere

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](https://docs.weblate.org/ro/latest/user/search.md) feature
to find a specific string or term.

![image](screenshots/strings-to-check.webp)

<a id="suggestions"></a>

## Sugestii

#### NOTE
Permisiunile efective pot varia în funcție de configurația Weblate.

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.

<a id="user-comments"></a>

## Comentarii

Three types of comments can be posted:

* for translations
* for source strings
* for reporting source string bugs when this functionality is turned on using [Activează revizuiri sursă](https://docs.weblate.org/ro/latest/admin/projects.md#project-source-review).

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 [Profil utilizator](https://docs.weblate.org/ro/latest/user/profile.md#user-profile); the comment count links
to your comment activity. To find strings with comments by a specific user, use
[Căutare](https://docs.weblate.org/ro/latest/user/search.md). For example, `comment_author:USERNAME` finds strings
with comments by that user, and `source_comment_author:USERNAME` finds
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.

#### SEE ALSO
* [Recepționarea feedback-ului șirului sursă](https://docs.weblate.org/ro/latest/devel/review.md#report-source)
* [Sursa șiruri de recenzii](https://docs.weblate.org/ro/latest/workflows.md#source-reviews)
* [Activează revizuiri sursă](https://docs.weblate.org/ro/latest/admin/projects.md#project-source-review)

## Variante

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.

#### SEE ALSO
* [Variante de șiruri](https://docs.weblate.org/ro/latest/devel/translations.md#variants)
* [Variante](https://docs.weblate.org/ro/latest/user/glossary.md#glossary-variants)

## Etichete

Etichetele sunt utilizate pentru a clasifica șirurile de caractere în cadrul unui proiect pentru a personaliza în continuare fluxul de lucru al localizării (de exemplu, pentru a defini categorii de șiruri de caractere).

Următoarele etichete sunt utilizate de Weblate:

Tradus automat
: String translated using [Traducere automată](#auto-translation).

Sursa trebuie revizuită
: String marked for review using [Sursa șiruri de recenzii](https://docs.weblate.org/ro/latest/workflows.md#source-reviews).

#### SEE ALSO
[Șir de etichete](https://docs.weblate.org/ro/latest/devel/translations.md#labels)

<a id="translating"></a>

## Traducerea

Pe pagina de traducere sunt afișate șirul sursă și o zonă de editare pentru traducerea acestuia. În cazul în care traducerea este la plural, sunt afișate mai multe șiruri sursă și zone de editare, fiecare fiind descrisă și etichetată în funcție de numărul de forme de plural pe care le are limba tradusă.

Toate caracterele speciale de spații albe sunt subliniate cu roșu și indicate cu simboluri gri. Mai mult de un spațiu ulterior este, de asemenea, subliniat cu roșu pentru a atenționa traducătorul asupra unei potențiale probleme de formatare.

Pe această pagină pot fi afișate diverse informații suplimentare, majoritatea provenind din codul sursă al proiectului (cum ar fi contextul, comentariile sau locul în care este utilizat mesajul). Câmpurile de traducere pentru orice limbă secundară selectată de traducători în preferințe vor fi afișate (a se vedea [Limbi secundare](https://docs.weblate.org/ro/latest/user/profile.md#secondary-languages)) deasupra șirului sursă.

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 (🗑).

<a id="translating-special-text"></a>

### 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 [Contextul traducerii](#source-context), [Glosar](https://docs.weblate.org/ro/latest/user/glossary.md), and
[Comentarii](#user-comments) when the source text needs clarification.

#### SEE ALSO
* [Verificări și reparații](https://docs.weblate.org/ro/latest/user/checks.md)
* [Pluraluri](#plurals)
* [Contextul traducerii](#source-context)
* [Comentarii](#user-comments)

<a id="edit-source"></a>

### Editing source strings and keys

When [Gestionează șiruri](https://docs.weblate.org/ro/latest/admin/projects.md#component-manage-units) 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.

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.

#### SEE ALSO
* [Gestionează șiruri](https://docs.weblate.org/ro/latest/admin/projects.md#component-manage-units)
* [`POST /api/units/(int:id)/source/`](https://docs.weblate.org/ro/latest/api.md#post--api-units-(int-id)-source-)

<a id="plurals"></a>

### Pluraluri

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](https://unicode-org.github.io/cldr-staging/charts/37/supplemental/language_plural_rules.html)
by the Unicode Consortium is a more detailed description.

#### SEE ALSO
[Plural definitions](https://docs.weblate.org/ro/latest/admin/languages.md#plural-definitions)

![image](screenshots/plurals.webp)

<a id="alternative-translations"></a>

### Traduceri alternative

#### Versionadded
Added in version 4.13.

#### NOTE
În prezent, acest lucru este acceptat numai cu [Fișier CSV multivaloare](https://docs.weblate.org/ro/latest/formats/csv.md#multivalue-csv).

În cazul anumitor formate, este posibil să existe mai multe traduceri pentru un singur șir de caractere. Puteți adăuga mai multe traduceri alternative folosind meniul Tools. Toate traducerile alternative goale vor fi eliminate automat la salvare.

<a id="keyboard"></a>

### Scurtături de tastatură

Următoarele comenzi rapide de la tastatură pot fi utilizate în timpul traducerii:

| Comenzi rapide de la tastatură                                                             | Descriere                                                                                                        |
|--------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|
| `?`                                                                                        | Open available keyboard shortcuts.                                                                               |
| `Alt`+`Home`                                                                               | Navigate to the first translation in the current search.                                                         |
| `Alt`+`End`                                                                                | Navigate to the last translation in the current search.                                                          |
| `Alt`+`PageUp` sau<br/><br/>`Ctrl` ``+`↑` sau<br/><br/>`Alt` ``+`↑` sau<br/><br/>`Cmd`+`↑` | Navigate to the previous translation in the current search.                                                      |
| `Alt`+`PageDown` sau<br/><br/>`Ctrl`+`↓` sau<br/><br/>`Alt`+`↓` sau<br/><br/>`Cmd`+`↓`     | Navighează la următoarea traducere din căutarea curentă.                                                         |
| `Ctrl`+`Enter` sau<br/><br/>`Cmd`+`Enter`                                                  | Trimiteți formularul curent; este același lucru cu apăsarea Salvare și continuare în timpul editării traducerii. |
| `Ctrl`+`Shift`+`Enter` sau<br/><br/>`Cmd`+`Shift`+`Enter`                                  | Unmark translation as Needing edit and submit it.                                                                |
| `Ctrl`+`Alt`+`Enter` or<br/><br/>`Cmd`+`Alt`+`Enter`                                       | Approve the translation and save and continue.<br/>Only available to reviewers.                                  |
| `Alt`+`Enter` sau<br/><br/>`Option`+`Enter`                                                | Submit the string as a suggestion; this works the same as<br/>pressing Suggest while editing translation.        |
| `Ctrl`+`E` sau<br/><br/>`Cmd`+`E`                                                          | Focus on translation editor.                                                                                     |
| `Ctrl`+`U` sau<br/><br/>`Cmd`+`U`                                                          | Focus on comment editor.                                                                                         |
| `Ctrl`+`M` sau<br/><br/>`Cmd`+`M`                                                          | Afișează fila Sugestii automate, vezi [Sugestii automate](#machine-translation).          |
| `Ctrl`+`1` to `Ctrl`+`9` sau<br/><br/>`Cmd`+`1` la `Cmd`+`9`                               | Copies placeable of a given number from source string.                                                           |
| `Ctrl`+`M` followed by<br/>`1` to `9` or<br/><br/>`Cmd`+`M` followed by<br/>`1` to `9`     | Copy the machine translation of a given number to current translation.                                           |
| `Ctrl`+`I` followed by<br/>`1` to `9` or<br/><br/>`Cmd`+`I` followed by<br/>`1` to `9`     | Ignorați un element din lista de verificări nereușite.                                                           |
| `Ctrl`+`J` ori<br/><br/>`Cmd`+`J`                                                          | Afișează fila Nearby strings.                                                                                    |
| `Ctrl`+`S` ori<br/><br/>`Cmd`+`S`                                                          | Focus on search field.                                                                                           |
| `Ctrl`+`O` sau<br/><br/>`Cmd`+`O`                                                          | Copiază șirul sursă.                                                                                             |
| `Ctrl`+`Y` ori<br/><br/>`Cmd`+`Y`                                                          | Activați caseta de selectare Necesită editare.                                                                   |
| `→`                                                                                        | Browse the next translation string.                                                                              |
| `←`                                                                                        | Browse the previous translation string.                                                                          |

<a id="visual-keyboard"></a>

### Tastatura vizuală

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.

Simbolurile prezentate se împart în trei categorii:

* Configurat de utilizator [Caractere speciale](https://docs.weblate.org/ro/latest/user/profile.md#profile-specialchars) definit în [Profil utilizator](https://docs.weblate.org/ro/latest/user/profile.md#user-profile)
* Per-language characters provided by Weblate (e.g. quotes or RTL-specific characters)
* Caracterele configurate cu ajutorul [`SPECIAL_CHARS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SPECIAL_CHARS)

![image](screenshots/visual-keyboard.webp)

<a id="source-context"></a>

### Contextul traducerii

Această descriere contextuală oferă informații conexe despre șirul curent.

Atributele șirurilor de caractere
: Lucruri precum ID-ul mesajului, contextul (`msgctxt`) sau locația în codul sursă.

Explicație
: Further clarification can be provided in Weblate via [Explicație](https://docs.weblate.org/ro/latest/admin/translating.md#additional-explanation).

Capturi de ecran
: 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](https://docs.weblate.org/ro/latest/admin/translating.md#screenshots).

Șiruri apropiate
: Displays neighbouring strings from the translation file.
  These are usually also used in a similar context and prove
  useful in keeping the translation consistent.

Alte apariții
: În cazul în care un mesaj apare în mai multe locuri (de exemplu, mai multe componente), această filă le afișează pe toate dacă se constată că sunt inconsecvente (a se vedea [Inconsecvent](https://docs.weblate.org/ro/latest/user/checks.md#check-inconsistent)). Puteți alege pe care dintre ele să o utilizați.

Memorie de traducere
: Uită-te la șiruri similare traduse în trecut, vezi [Memorie de traducere](https://docs.weblate.org/ro/latest/admin/memory.md#memory).

Glosar
: Afișează termenii din glosarul proiectului utilizați în mesajul curent.

Istoric
: Lista persoanelor care au modificat recent acest mesaj folosind Weblate.

Proiect
: Informații despre proiect, cum ar fi instrucțiuni pentru traducători sau un director sau un link către șirul din depozitul sistemului de control al versiunilor pe care îl folosește proiectul.

Dacă doriți linkuri directe, formatul de traducere trebuie să fie compatibil.

<a id="add-existing-screenshot"></a>

#### Adding an existing screenshot

To link a screenshot that has already been uploaded, open the string in the
translation editor:

1. In the Screenshots panel, choose Add existing screenshot.
2. Browse the thumbnails, or enter a query in Search screenshots and
   choose Search. Use Previous and Next to
   browse additional results.
3. 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.
4. Choose Add screenshot. The editor reloads on the same string and
   displays the associated screenshot in the Screenshots panel.

![Screenshot picker with a highlighted card marked Selected.](screenshots/screenshot-picker-selected.webp)

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](https://docs.weblate.org/ro/latest/admin/translating.md#screenshots).

<a id="translation-history"></a>

### Istoricul traducerii

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](https://docs.weblate.org/ro/latest/admin/automation.md#automation-reference) 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](https://docs.weblate.org/ro/latest/api.md) 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.

### Lungimea șirului tradus

Weblate poate limita lungimea unei traduceri în mai multe moduri pentru a se asigura că șirul tradus nu este prea lung:

* The default limitation for translation is ten times longer than the source
  string. This can be modified with [`LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-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 [Formate bilingve și monolingve](https://docs.weblate.org/ro/latest/formats.md#bimono) for more info.
* Maximum length in characters defined by the translation file or flag, as per
  [Lungime maximă a traducerii](https://docs.weblate.org/ro/latest/user/checks.md#check-max-length).
* Maximal rendered size in pixels as defined by flags; see [Dimensiune maximă a traducerii](https://docs.weblate.org/ro/latest/user/checks.md#check-max-size).

<a id="machine-translation"></a>

## Sugestii automate

Based on configuration and your translated language, Weblate provides suggestions
from configured [translation services](https://docs.weblate.org/ro/latest/admin/machine.md#machine-translation-setup), including
machine translation tools and [Memorie de traducere](https://docs.weblate.org/ro/latest/admin/memory.md#translation-memory).
All machine translations are available in a single tab of each translation page.

You can also perform a concordance search on the [Memorie de traducere](https://docs.weblate.org/ro/latest/admin/memory.md#translation-memory).

#### SEE ALSO
Puteți găsi lista de instrumente acceptate în [Translation services](https://docs.weblate.org/ro/latest/admin/machine.md#machine-translation-setup).

<a id="auto-translation"></a>

## Traducere automată

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:

![image](screenshots/automatic-translation.webp)

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.

Sunt posibile două moduri de funcționare:

- Utilizarea altor componente Weblate ca sursă pentru traduceri.
- Utilizarea serviciilor de traducere automată selectate cu traduceri care depășesc un anumit prag de calitate.

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.

De asemenea, puteți alege ce șiruri de caractere trebuie să fie traduse automat.

#### WARNING
Rețineți că acest lucru va suprascrie traducerile existente dacă este utilizat cu filtre largi, cum ar fi All strings.

Utile în mai multe situații, cum ar fi consolidarea traducerii între diferite componente (de exemplu, aplicația și site-ul său web) sau atunci când se creează o traducere pentru o nouă componentă utilizând traducerile existente (memorie de traducere).

Șirurile de caractere traduse automat sunt etichetate Automatically translated.

#### SEE ALSO
[Păstrarea traducerilor la fel în toate componentele](https://docs.weblate.org/ro/latest/admin/continuous.md#translation-consistency)

<a id="user-rate"></a>

## Limitarea ratei

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 [Limitarea ratei](https://docs.weblate.org/ro/latest/admin/optionals.md#rate-limit).

<a id="search-replace"></a>

## Caută și înlocuiește

Search and replace is part of [Editare în masă](#bulk-edit). Use it to change terminology or
fix matching translations, with literal text or regular expressions.

<a id="bulk-edit"></a>

## Editare în masă

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:

* Change string state (for example to approve all unreviewed strings).
* 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 [Personalizarea comportamentului cu ajutorul stegulețelor](https://docs.weblate.org/ro/latest/admin/checks.md#custom-checks))
* Reglați etichetele șirurilor de caractere (a se vedea [Șir de etichete](https://docs.weblate.org/ro/latest/devel/translations.md#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.

#### HINT
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.

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.

![image](screenshots/bulk-edit.webp)![image](screenshots/bulk-edit-preview.webp)

#### SEE ALSO
[Bulk edit add-on](https://docs.weblate.org/ro/latest/admin/addons.md#addon-weblate-flags-bulk)

## Vedere Matrix

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.

![image](screenshots/matrix-view.webp)

<a id="zen-mode"></a>

## Modul 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
[Preferințe](https://docs.weblate.org/ro/latest/user/profile.md#profile-preferences) tab on your [Profil utilizator](https://docs.weblate.org/ro/latest/user/profile.md#user-profile).
You can also choose there between having translations listed
Top to bottom or Side by side,
depending on your personal preference.

![image](screenshots/zen-mode.webp)
