There is tremendous value in knowing if a product is global-ready as part of your development cycle. Large amounts of development, marketing and branding dollars are at stake. Yet often, the only way software gets verified for localization, is during the localization process itself, or based on a limited series of manual interface testing. That’s way too late in the development cycle to be efficient and a very incomplete way to address the issue.
There are all kinds of products to support issues like software security and efficiency, but how about checking on internationalization, which for many companies is a hefty and vital product requirement for a good share of company revenue?
In this webinar, we’ll be demonstrating how Globalyzer 3.4 (our new release) finds, categorizes, tracks and helps fix internationalization bugs in source code using static analysis.
The Webinar features special guest Michael Kuperstein, Localization Engineer, Global Language Solutions, at Intel. Michael’s responsibilities at Intel include tools development and internationalization consulting for product development teams; he has lead Globalyzer implementation at Intel.
We’ll start with some source code and then:
- Analyze it for internationalization issues
- Customize “rule-sets” so that specific issues to that code can be address
- Show how that information can be accessed and shared among development team members
- Integrate automated Globalyzer static analysis via command line
- Support testing initiatives
The Webinar targets technical managers, software engineers, test engineering managers, QA managers, internationalization and localization managers, and anyone facing ongoing software globalization and localization challenges.