Project Management

Plural Forms

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.

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

To more information about plural rules, see this article.

Handling Files with Plural Forms

Importing Files into Memsource

When importing files with plural-sensitive strings into Memsource, the Segment Key should be used as the context type in TM 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.

To set the Context Type as Segment key, follow these steps:

  1. From the Setup Setup_gear.png page, scroll down to the Project Settings section and click on TM Match Context and Optimization.

    The TM Match Context and Optimization page opens.

  2. For the Context Type, select Segment Key from the dropdown list.

  3. Click Save. The settings are applied to imported files imported.

These settings can also be applied at the project level by editing the project.

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

Plural-sensitive strings can have a different context and this is 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.

  • 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 editor.

  • The required plural form for the active segment is shown in the Context Note at the bottom of the 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 required plural details so that the translation is correct.

  • Segments containing plural-sensitive strings are indicated by a blue P in the info column and the corresponding tooltip.

  • Plural-sensitive segments are filtered 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?

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 you can leave a public comment below or Submit a request to our Support team.
Thank you for your feedback.

Comments

0 comments

Article is closed for comments.