Request the recording of this webinar by completing the form at the bottom of this page
Internationalization efforts are often costly, highly iterative, late and incomplete. Internationalization release requirements can fall significantly behind new functionality and localization entropy ensues. Agile release schedules put more emphasis than ever on building i18n into coding practices. At the same time, many companies are enjoying 60% and more of their revenues or significant growth outside their home markets.
Besides the time consuming process of verifying internationalization, it’s very difficult to hit all the likely internationalization test cases that will be needed. That undermines the very expense and effort of performing localization to reach new clients. Using Globalyzer to analyze and fix issues at the source code level minimizes costly testing and fixing cycles during localization. Plus it just makes internationalization go faster, whether you have a big i18n effort ahead, or a new release that needs checking.
This webinar recording goes over:
- Discuss the process of static analysis for internationalization issues
- Show how it’s a lot more efficient to search and internationalize code using Globalyzer than poking and picking your way through with scripts, eyeballs and testing
- Work with some sample open source code
- Discuss False Positive and False Negative results and how to manage them
- Introduce rule sets and dictionary comparisons for pinpointing i18n issues
- Show results with filtering and without on large scale projects
- Show how you can automatically audit code and track new development for i18n issues
Who should view:
- Development Managers
- Technical Managers
- Developers
- Localization Managers and Engineers
In our services effort we’ve been using Globalyzer to get excellent intelligence on internationalization issues, step through them and fix them. We’ve spent a great deal of development effort in the past year to bring about a major new release and two follow-up releases, so that we can bring this system out to you and your teams, and analyze and fix code for internationalization issues without all the usual costly iterations and delays.
While we’ve been bringing this message out broadly this year, there’s quite a bit of initial skepticism on applying Globalyzer and getting valuable results, as opposed to getting deluged by false reporting. So in this webinar, we’re going to show you how we get our work done.
