LingoHub Help Center

Our experience, knowledge and lessons learned - all here just for you.

Text segment key uniqueness

Text segment keys can be unique either per project or resource file. Depending on your organizational preferences, you need to change the options accordingly. Learn how both settings will affect your text segments in this article.

Accessing the settings

The settings for text segment key uniqueness can be accessed via the dashboard, follow the steps below:

  1. Access the dashboard overview by clicking on dashboard in the top navigation bar.
  2. Select a project from the left side panel.
  3. Click preferences in the dashboard overview.
  4. Click import/export.

The settings for text segment key uniqueness will be displayed.

Img

Uniqueness types

Uniqueness per project

The example below shows you how LingoHub will handle new text segments when the setting for text segment key uniqueness is set to project.

Img

If a new resource file containing already existing keys is uploaded, LingoHub will remove the existing text segments of each duplicate key from the resource file.
Note: This is valid for all existing resource files and not only for the last uploaded file.

Considering the example above, if another file, e.g., x.yml contains the key form, the key would be removed from x.yml after the upload of b.yml, because b.yml also contains form and is newer, thus overwriting existing text segments with the same key.

Uniqueness per resource file

The example below shows you how LingoHub will handle new text segments when the setting for text segment key uniqueness is set to resource file.

Img

If a new resource file containing already existing keys is uploaded, LingoHub will keep the existing text segments of each duplicate key from the resource file. All text segments will be accessible in the editor.

Changing the uniqueness type

To change the uniqueness type, follow the steps below:

  1. Access the text segment key uniqueness settings, as described above.
  2. Change the settings to your preferred type.
    Changes will be saved automatically.

Note: If there are duplicate keys, it is not possible to switch from the resource file uniqueness setting to the project uniqueness setting. The duplicates need to be handled first.

Congratulations! You finished the article on text segment key uniqueness. If there's anything we can help you with, please get in touch with our support.

Ready to optimize your translation workflow?