Duplicated Strings

Configure settings for duplicated strings to achieve the highest efficiency of the localization process and to save costs.

Overview

In Crowdin Enterprise, the localization process is based on translating the source strings to the defined target languages. Source strings are uploaded to the system in localization files. Each unique source string that was first uploaded or added (for CSV files) in Crowdin Enterprise is considered to be the master string. All other strings that are identical to the master string but were uploaded or created later are considered duplicated strings.

Duplicated Strings Management

There are 4 main options to work with duplicated strings in Crowdin Enterprise:

  • Show – translators will translate each duplicate separately
  • Show, but auto-translate them
  • Show (recommended for versions) – duplicates are hidden only across the version branches
  • Hide – all duplicates will share the same translation Duplicates Options

Show all duplicates

When this option is chosen, all the duplicated strings will be visible for translators. Each duplicate will require separate translation.

Use case: works perfectly for the projects where the same words might have various meanings depending on the context.

Show, but auto-translate duplicates

When this option is chosen, all the duplicated strings will be shown and automatically translated. When the master string is translated, its translation is automatically shared between all the duplicates. This allows translators to check and re-translate duplicated strings if necessary.

Use case: works great if you want to save time, but need the automatic translations to be reviewed.

Show. Duplicates are hidden only across the version branches

When this option is chosen, only the master strings that were originally uploaded to the system will be available for translations. All duplicated strings will automatically gain the translations from the original strings and will be hidden in all version branches.

Couple of things to keep in mind:

  • The system always checks the path to the string throughout the branches. For example, even if the strings are the same in different version branches (branch1 and branch2) but their paths are different (branch1 - /localization/android.xml and branch2 - /localization/apps/android.xml) they won’t be recognized as duplicates.
  • This option works only for the strings located in the files that have the same format. For example, if there is the same string in android.xml and ios.strings files it won’t be recognized as a duplicate.

Use case: works perfectly for continuous projects with various version branches. Allows translators to work with unique strings in separate branches.

Hide all duplicates

When this option is chosen, the system spots the duplicated strings in all files. Only the master strings that were originally uploaded are visible and should be translated. The hidden duplicated strings will automatically share the translations from the corresponding master strings.

Use case: works great for the projects with narrow scopes where all duplicates share the same context.

See Also

Was this article helpful?