Locking Entries

When you localize an app or software, you may have some text that should remain the same in all localized versions. This can include non-translated text, links, proper nouns, and so on. To ensure these entries remain the same as the Base Language text in localized versions, these entries should be Locked.

Locking prohibits any translations for the entry and GL Strings will use the Base Language entry for any specific locale (if no translation exists before the entry is locked). If an entry is locked after translations are added, then those translations are not editable (unless they are unlocked first.)

Users can lock entries using the Multi-Edit Options or users can lock individual entries in the detail view.

1. Hover over the entry then click on the information icon under the string ID
2. In the upper right-hand corner of the detail view, click Lock entry
3. This will generate a pop-up message from which users can choose to lock an entry for the selected language or across all languages.

To unlock the entry, users can simply click on the Unlock entry button.

Impacts of Locking Entries

Edits to Locked Entries

• If an entry is locked, the text cannot be edited. This includes edits to the source (if the entry is locked in the source language.)
• If edits are required (in the source or any target languages) you must unlock the entry first.

Locking Across Languages

• If an entry is locked across all languages in a project, the entry will be locked in any new language added to the project.
• To prevent the entries from being locked in new languages, you must Unlock (all languages).
• Alternatively, you can unlock the entry for specific languages.