Translating

Plural Forms (Strings)

Each language has its own grammatical forms for singular and plural phrases.

Example:

  • English has two forms: one and other, as in 1 file and 2 files.

  • Other languages may have one or even several forms: one, few, and other.

This presents a challenge for localization.

The translation of plural-sensitive strings is supported. These strings must be translated using the plural forms based on the plural rules of the target language. These plural forms must be defined in the source file.

Example:

  • The English string There are %d% items left, where %d% represents any number except 1.

  • In Czech, this needs to to be translated in two ways.

    The first for numbers 2, 3 or 4 (i.e. few) and the second for numbers 0, 5 and more (i.e. other).

For more information about plural rules, see CLDR plural rules.

Handling plural forms

Many localization file formats are supported and handle plural values in different ways. The most common ways are presented for each format.

Plural forms are handled in the Plural forms tab of the Project settings window. When adding a locale to project and providing the ISO code, the plural forms process is supported by displaying the correct input fields for that language.

Plural forms can also be enabled on a per-key basis. To mark a key as having pluralized translations, select Enable plural forms for this key on the Plural forms tab of the Edit key window. Ensure a Plural key name is provided if required by the used format (e.g., when using gettext).

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.