General FAQ

What programming languages does Globalyzer support?

ActionScript, C#, C/C++, Delphi, HTML, Java, JavaScript, Perl, PHP, Qt, SQL (MS SQL, MySQL, Oracle, PostgreSQL), VB (Classic and .NET), VBScript, and XML (including MXML). We add additional programming languages at the request of our clients.

How thorough is Globalyzer in reviewing and modifying my code?

It is very thorough, but some of the detection and filtering specificity is controlled by the user. Globalyzer allows for strong detection and filtering controls using regular expressions, as well as built in search management capabilities. The more you learn Globalyzer's capabilities, the easier to refine your results. With regard to modifying code, Globalyzer allows for the editing of code within its fully-functional Eclipse IDE, though you can use a different IDE to edit source code if you prefer. Globalyzer helps you navigate right from reports to instances in your code that need externalization or further analysis. You can also choose to mark issues with a comment for later review.

Why would I use Globalyzer versus my own scripts?

Globalyzer encapsulates a terrific amount of research and development regarding internationalization issues and how to resolve them. It would be extremely difficult to develop an internationalization detection script that is as comprehensive and powerful, much less easily leveraged across your software team. And, even if you could come up with your own scripts, wouldn’t your team be better off working on your product, rather than on internationalization issue detection? Globalyzer was first released in 2001 and has been continually developed ever since, allowing for the inclusion of features desired from our broad customer base.

Can I use Globalyzer with my standard IDE?

Yes. Globalyzer comments can be inserted which can be quickly searched on and worked on with your preferred IDE. However, with the Globalyzer 4.0 Workbench, you will have a fully-functioning Eclipse IDE available to you.

How can Globalyzer be leveraged across my development team?

Software internationalization involves a surprisingly complex variety of issues, depending upon your requirements, technologies and unique application needs. Globalyzer’s client/server architecture lets you build and store internationalization detection and filtering rules (which we call Rule Sets), and which can then be shared within your development team. Developers can then perform internationalization tasks efficiently, whether they are working in the next cube or in the next country.

How can Globalyzer support batch processes?

Globalyzer’s Command Line Client supports batch reporting during automated processes, such as a nightly build. The Command Line Client will automate reports on internationalization status, including output of both summary and detailed reports itemizing internationalization issues and their precise location within source code. Globalyzer is also useful as a QA benchmark, so that code submitted for testing has been clearly analyzed for internationalization compliance, reducing the iterative burden between internationalization and localization testing and development.

What results should I expect from running Globalyzer on my source code?

Globalyzer looks for four categories of internationalization issues:

• Embedded Strings: Strings that must be extracted from the source code into translatable resource files so that their display can be in any language

• Locale-Sensitive Methods: Methods and functions (depending upon your programming language) that may restrict character encoding (ISO-Latin or Unicode support), as well as cultural formatting, including date, time, number and currency formatting

• Static File References: References to static files, such as images, which will need to be reviewed for cultural appropriateness and translation of string components within the file

• General Patterns: User-defined patterns that detect internationalization issues that are specific to your source code

Remember that in demo mode, Globalyzer will limit you to viewing the first 100 issues it detects.

How long does it take to run Globalyzer?

This depends on what you are searching for and how many lines of code you are searching through, as well as if you are optionally using an additional database for tracking results. Most Globalyzer scans can review over two million lines of code in about the amount of time it takes to get a cup of coffee.

For example for an initial scan: 2.3 million lines of code = 3 minutes, 37 seconds for C++, similar results for Java and C# on a 2.5 GHz dual core laptop.

With each release we are always finding little ways to improve performance, and we think you’ll find Globalyzer quite responsive, especially considering that in many cases it is searching on hundreds of internationalization issues simultaneously.

Can Globalyzer help me build resource files and externalize strings from my source code?

Yes it can, and it will add great productivity to that long and tedious task. It is common for developers to be able to comfortably externalize 1,000 strings and more per day using Globalyzer. Globalyzer lets you see the string within your code and manages the whole externalization process. It is customizable, giving the developer complete control while aiding productivity.

Is Globalyzer automatically (automagically) fixing my code? Is Globalyzer adding anything proprietary?

No, Globalyzer does not make changes without your knowledge and does not add any proprietary elements to your source code. However, once you do approve the fix for one or more internationalization issues, Globalyzer does have highly productive capabilities to speed up repetitive internationalization tasks, such as string externalization.

Do I have to submit my source code to the Globalyzer web site?

No. Your source code and any information about is never copied from your local machine. Globalyzer only accesses its server for the account rule set configurations for detection and filtering and for storing summary counts from scans. The Globalyzer desktop client and Command Line client perform all code scanning and reporting on your local machine.

Are there any built-in limitations with respect to number of files, number of code lines being processed?

No, Globalyzer is built to be able to work on large code bases. We test and regularly work on millions of lines of code using Globalyzer, in our normal testing cycle and in our internationalization services practice. That said, you do want to make Globalyzer manageable for your development needs. For example, often a client with create a Globalyzer projects for each application component. This allows for quicker scanning and more focused results that can be addressed by that component’s development team.

Note: running in “demo” mode, you are limited to viewing approximately the first 100 results.

How can Globalyzer help in creating i18n-aware applications throughout the lifecycle of an application

The Globalyzer Workbench installation includes both the Workbench and the Command Line Client. You can use the Command Line Client to integrate into automated build processes so that you can monitor internationalization status on an ongoing basis.

How can Globalyzer help determine project tasks, estimated efforts and project costs?

In our internationalization services practice, we use Globlayzer heavily to scope internationalization work which provides metrics of internationalization issues, and then use these results to understand and build extensive project plans.