Find strings that have not been wrapped for localization

Problem

Source code is messy and every developer seems to write their code in their own unique style. Identifying strings that might need to be localized is not always simple.

Solution

Over time we have found many ways to identify strings to present to the developer so that they can make a choice; localize, don’t localize, undecided. The new ways developers accidentally obfuscate strings are then added to the cumulative data by which apps are analyzed, continually expanding the capabilities of the automation process determining which strings should be translated. The resulting dataset is an actively-evolving, highly valuable trade secret.

Impact

By isolating and displaying the unwrapped strings that may require localization, the developer can quickly go through their source code files to decide what to localize. This saves the developer a great deal of time compared to manually reviewing every line of code in every source code file.