When globally-focused companies begin implementing continuous globalization, they inevitably touch on disparate concerns between development and localization teams. Development teams commonly have fast and feature-focused release cycles. The localized quality of those releases is dependent on concurrent internationalization (i18n) and localization (L10n) activities, but it’s hard for the localization teams to stay in sync.
The most common developer objection to implementing continuous globalization systems concerns managing false positives which distract teams from real issues. Let me explain.
A system like the Lingoport’s Globalyzer and the full Lingoport Suite, analyzes code for i18n issues at key strategic points during ongoing development. But if the results are clouded with false positives (detected issues that really aren’t a problem), then you create lots of friction from development. It would be like that fable of The Boy Who Cried Wolf.
Globalyzer uses static analysis to measure and help correct i18n issues and changes that affect localization. The very fuzzy nature of i18n conditions means that you need a system that can be quickly customized and adapted for programming language, coding styles and specific application requirements. That customization needs to be powerful and quick to implement.
In this webinar, we’ll be showing multiple ways to bring that power to good use and fine tune results. Your teams get controls that help them quickly resolve issues that might otherwise not be turned up until testing, localization or even after release.
We’ll demonstrate a working sandbox example using source code in GitHub we’ll be directly processing, then step through:
- Analyzing an entire repository for i18n issues
- Refining analysis rules
- Quickly and permanently addressing issues and false positives from the developer’s IDE
- Running through issues and exceptions within the dashboard
- Isolating just that day’s work for analysis before committing to the repository
- Automatically finding and handling changed strings affecting the U/I and updating for localization
Who should attend:
- Development managers and engineers
- Localization managers and engineers
- Program managers
- Product managers
As always, we’ll have a Q&A period at the end as well.
Webinar Completed May 11th