Duplicity Linking

When translating content, it’s common to encounter duplicate phrases or sentences. Translating these duplicates multiple times not only consumes valuable time and resources but also risks inconsistencies in translations. Here are some strategies to save on translations of duplicate content:

Use Key Clustering: Key Clustering automatically identifies and groups keys with identical values, eliminating the need to translate the same content multiple times. This not only saves time and resources but also ensures consistency across translations.

Leverage Duplicity Linking: Duplicity Linking allows you to link multiple keys with the same content. When one key is translated, all linked keys are automatically updated with the new translation. This reduces the time spent on translating duplicate content.

Utilize Machine Translations (MT): Machine Translations can provide initial translations for your content, which can then be reviewed and refined by human translators. This can speed up the translation process and reduce costs.

Remember, the key to saving on translations of duplicate content is to leverage the right tools to streamline the translation process and ensure consistency across all translations.

If your project has duplicate keys, you can easily resolve them by linking them together. When a key is linked to another, it automatically inherits the content of the linked key during publishing. Linked keys are automatically marked as hidden and do not require separate translations. While a linked key can still have its own content, that content won’t be used during publishing and will be replaced by the content of the linked key as long as the link is active.

You can manage duplicity links using public API, automating their creation or deletion.

Learn more in the Duplicity Linking API documentation.

Sure! If you can’t or don’t want to rename the keys to use the same name in the source integration, you can use the Duplicity Linking feature when you don’t want to alter the source, so the keys will share their translations.

Localizing a large project can result in creating duplicated keys, which becomes hard to manage, especially when multiple teams work on the same project. Localazy offers a solution called Duplicity Linking that allows you to reuse translations across linked keys in all languages and even across several projects.

Duplicity Linking is available in the Business plan

The feature links multiple different keys with the same content, with one source key acting as the content source and the others as the linked keys. The linked keys retain their own values and translations, but when the link is active, and their translation value is retrieved, the content source key value is used instead for all languages. Removing the link restores the linked key to its original behavior.

You can learn more in the article: Keep your duplicate strings under control with the Duplicity Linking feature

Your projects can often contain multiple keys with the same content. Be it button labels across a large-scale information system, including keys on the backend and frontend or Android vs. iOS versions of your app. There are two ways to approach duplicate keys with Localazy.

The first option to consider when you have two or more projects that contain duplicities is to use the Connected Projects feature, which is available with the Professional plan. Connected Projects can help you by translating identical keys across multiple projects. This feature is great for a portfolio of projects sharing duplicate keys or Android and iOS versions of the same app. When enabled, Localazy distributes existing translations between connected projects and automatically decides whether the translation can be used right away or needs to go through review first.

For a robust duplicity management that can work with duplicities inside one project and across multiple projects as well, we recommend the Duplicity Linking feature, available with the Business plan. With duplicity linking, you can define one key as the source for all other keys with the same or similar content. The other keys are then marked as hidden and get their translation from the linked key.