> For the complete documentation index, see [llms.txt](https://docs.b2translate.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2translate.b2broker.com/user-guide/manage-translations/handle-plural-forms.md).

# Handle plural forms

B2TRANSLATE's pluralization feature enables accurate translation of quantity-dependent strings across different languages. This guide explains how to work with plural forms when translating content that changes based on quantity.

## Understanding plural forms

Different languages have varying rules for plural forms.

While English typically uses two forms (singular and plural), other languages may require multiple forms based on complex grammatical rules, for example:

* **English**: 1 file, 2 file**s**, 5 file**s**
* **Russian**: 1 файл, 2 файл**а**, 5 файл**ов**

B2TRANSLATE automatically determines the required plural forms based on your target language and displays the appropriate input fields.

## The Pluralization panel

When working with pluralized keys, you'll see the dedicated **Pluralization** panel containing multiple input fields, each representing a different plural form for your target language.

<figure><img src="/files/TbV234tjC646Euya6GZa" alt="Pluralization panel"><figcaption><p>Pluralization panel</p></figcaption></figure>

### The Other form

This is the primary required form used across all languages worldwide.

Every pluralized translation must include this form as it serves as the fallback for any unspecified cases. If you fill only the **Other** form and leave the others empty, B2TRANSLATE will automatically populate the remaining forms with the **Other** form value. This ensures your translation remains functional while you work on completing all forms.

{% hint style="info" %}
On the translation page of your project, this form is displayed in the **Translation** field for keys with plural forms.
{% endhint %}

### Default value

Under each plural form input field, you'll see the default value (typically the English source text). The display logic works as follows:

* If your target language has more plural forms than the source language (for example, Russian with 4 forms vs English with 2), default values will only appear under the corresponding number of forms.
* When no default translation is present in your target language, only English translations are displayed, maintaining the existing logic.

## Translation workflow

{% stepper %}
{% step %}

### Access the Pluralization panel

On the **Translations** page, click the **three dots** (View details) for a desired key.

You'll see the **Pluralization** tab where applicable. If not, only the **Info** tab is available.
{% endstep %}

{% step %}

### Fill in the plural forms

1. Start with translating the **Other** form, as this is required for all languages. If you fill only the **Other** form and leave the others empty, B2TRANSLATE will automatically populate the remaining forms with the **Other** form value. This ensures your translation remains functional while you work on completing all forms.
2. For languages requiring multiple forms, ensure every field is properly filled before saving. Though this step isn't mandatory, leaving some fields empty may result in incomplete translations depending on your target language requirements.

<figure><img src="/files/Fos6PkT9wh1GDp5E2a6j" alt="Fill in plural forms"><figcaption><p>Fill in plural forms</p></figcaption></figure>
{% endstep %}

{% step %}

### Save changes

All modifications within the **Pluralization** panel must be saved manually using the **Save changes** button.

The system will not automatically save changes as you type, allowing you to work on multiple forms before committing your translations.
{% endstep %}
{% endstepper %}

## Best practices

When working with plural forms, consider the following:

* **Review all forms together**: Since all forms for a key are displayed simultaneously, use this opportunity to ensure consistency in terminology and style.
* **Use contextual guidance**: Each form includes labels and tooltips explaining when that particular form should be used.
* **Test with numbers**: Consider how your translations will appear with different quantities (1 item, 2 items, 5 items, 100 items).
* **Complete all required forms**: Ensure all forms are filled for languages that require complete sets.
* **Verify Other form**: Always provide a translation for the **Other** form as it serves as the universal fallback.
* **Save regularly**: Remember to manually save your changes using the **Save changes** button.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.b2translate.b2broker.com/user-guide/manage-translations/handle-plural-forms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
