During localization, some strings may become unnecessary. To simplify their management and prevent accidental data loss, we’ve introduced a new feature in BabelShark — "Propose for Removal."

String removal is required in several cases:

• The string was removed from the project code but remains in BabelShark. If a string is no longer used on the website or in the application, it should not remain in the translation system.
• The string was added by mistake. Sometimes, extra strings mistakenly appear in a project that should not be translated, or the initial version of a string was modified during development, but the old version remained in the system.
• The string contains a changing value that has been replaced with the variable __var. For example, if a string previously included dynamic data (names, dates, etc.) but has now been replaced with a variable, the old string can be deleted.

While such strings can be deleted immediately, managers or proofreaders may not always have the confidence or the necessary permissions to do so. For instance, proofreaders in BabelShark cannot delete strings on their own.

Now, if a string seems unnecessary, it can be marked as "Propose for Removal". This allows you to:

• Avoid irreversible deletion without discussion.
• Enable managers and the localization team to make a joint decision.
• Organize the cleanup process by deleting only truly unnecessary elements.

Once confirmed, marked strings can be permanently deleted without the risk of losing important data.