Project Management

Plural Forms in Memsource

Plural Rules

Each language has its own grammatical forms for singular and plural phrases. For example, while English has two forms (“one” and “other”, like “1 file” and “2 files”), other languages have one or even several forms (e.g. “one”, “few”, and “other”). This presents a challenge for localization. To address this, Memsource supports the translation of plural-sensitive strings. These strings must be translated using the plural forms based on the plural rules of the target language. These plural forms have to be defined in the source file.

For example, the English string “There are %d% items left”, where %d% represents any number except 1, needs to be translated to Czech 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”). To learn more about plural rules, please read this article.

Please note:

  • Only PO files with specified plural-sensitive strings are supported at the moment. For more details about this file format, please see our PO File article. More file formats will be added in the future.
  • Currently, only plural rules for cardinal number types are supported.

Handling Files with Plural Forms in Memsource

Importing Files into Memsource

When importing files with plural-sensitive strings into Memsource, the Segment Key should be used as the context type in the File Import SettingsTM Match Context and Optimization. The language locale and the plural category become part of the context of such strings. This is needed for leveraging translation memory matches, avoiding false positives while running QA, and identifying repetitions.

Leveraging TM Matches

If there are multiple TM matches where the match percentage is the same and the source is the same, but where the Segment Key context is different, the match with the corresponding plural form will be suggested first in the CAT pane and pre-translated based on the preferences.

Quality Assurance Warnings

The fact that plural-sensitive strings can have a different context is also taken into account when running QA on a job with plural-sensitive strings. The warning “Identical source but different translation” is not given if segments with plural-sensitive strings (and a different context) are translated in a different way. And the warning “Identical translation but different source” is issued when the same translation is used for the same source with a different context.

Identifying Repetitions

Plural-sensitive strings which have the same source text are not considered repetitions in Analyses or in the Memsource Editor unless they have the same context.

Translating Files with Plural Forms

  • Once a file with plural-sensitive strings is imported into Memsource, the plural-sensitive strings are shown in all their forms, based on the target language plural rules, in separate segments in the Memsource Editor.
  • The required plural form for the active segment is shown in the Context Note at the bottom of the Memsource Editor, where the Plural Category and the Plural Examples are specified.
  • The Context Note is always open when these segments are active to show the plural details required so that the translation is correct.
  • The segments containing plural-sensitive strings have a blue "P" (for Plural) in the info column and the corresponding tooltip.
  • It is possible to filter plural-sensitive segments using the Pluralized filter in the Segment Status filter options. They can also be filtered out using the Not Pluralized filter.
  • Plural-sensitive segments cannot be split or joined.
Was this article helpful?



Please sign in to leave a comment.