Changed Source strings and Outdated Translations

What impacts have changes made to the source language

Changes made to the source text for strings where a translation already exists can lead to that translation being outdated. In both cases, changes made to the source or any local language and published on Applanga while an Applanga SDK integration is active will be distributed to the integrated mobile application so be visible to mobile app users immediately.

As shown in the picture below, if a translation is indeed outdated, this will be highlighted with a warning in the editor. Additionally, there is a filter option, with which all instances where translations are outdated can easily be found.

How to trace how the source string was changed

Use the Change Log to see exactly what was changed by whom and when.

How to assign outdated translations to your reviewers

If outdated translation should be reviewed by your team members, you can use the Applanga workflow status interface to assign the strings in questions and notify them about it (if User Groups have been set up accordingly). The workflow status interface can be accessed on string level (1) or for any multiple strings at once by selecting them (2) via the “State” button (3).

In the workflow pop-up dialogue, the translation workflow status can be set to “Needs Review”. Additionally, the comment field can be used to provide further feedback. If multiple strings were selected and the pop-up was opened via the “State” button, the translation status and comment will be applied to all selected strings.

How to order a review for outdated translations

When creating a translation request via the Applanga order interface, to include all instances where translations might be outdated should be reviewed and potentially re-translated, in the “Select Strings” section of the order creation form, use any of the selection options with “outdated translations” in the name.