Configure settings for duplicated strings to achieve the highest efficiency of the localization process and to save costs.
Crowdin Enterprise’s localization process is based on translating source strings to the defined target languages. Source strings are uploaded to the system in localization files. Each unique source string first uploaded or added (for CSV and other formats supporting string editing) in Crowdin Enterprise is considered a master string. All other strings that are identical to the master string but were uploaded or created later are considered duplicate strings.
There are six main options to work with duplicated strings in Crowdin Enterprise:
Regular duplicates detection – when comparing strings, Crowdin Enterprise considers only source texts.
Strict duplicates detection – when comparing strings, Crowdin Enterprise considers both string identifiers (keys) and source texts.
When this option is selected, all duplicate strings will be visible to translators. Each duplicate will require a separate translation.
Use case: works perfectly for the projects where the same words might have various meanings depending on the context.
When this option is selected, all duplicate strings will be shown and automatically translated. When the master string is translated, its translation is automatically shared between all duplicates. This allows translators to check and re-translate duplicate strings if necessary.
Use case: works excellent if you want to save time but need the automatic translations to be reviewed.
When this option is selected, only the master strings that were originally uploaded to the system will be available for translation. All duplicate strings will automatically get the translations of the original strings and will be hidden in all version branches. This option is available in two versions: regular duplicate detection, strict duplicate detection. If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of this option. In other cases, feel free to use a regular one.
Couple of things to keep in mind:
Use case: works perfectly for continuous projects with various version branches. Allows translators to work with unique strings in separate branches.
When this option is selected, the system spots the duplicate strings in all files. Only the master strings that were originally uploaded are visible and should be translated. The hidden duplicate strings will automatically share the translations from the corresponding master strings. This option is available in two versions: regular duplicate detection, strict duplicate detection. If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of this option. In other cases, feel free to use a regular one.
Use case: works great for the projects with narrow scopes where all duplicates share the same context.