About Globalyzer

Lingoport’s Globalyzer was designed to bring internationalization to the forefront and facilitate making software world-ready a priority. See for yourself how Globalyzer generates an assessment of internationalization readiness and applications for real-time i18n detection, validation and resolution by requesting a free trial of Globalyzer.

Getting Started Videos

The following videos introduce Globalyzer: Globalyzer Quick Tutorial organizes the videos below in one logical sequence.

What is Globalyzer

Creating a Project in Globalyzer

Scanning Code and Refining Rules

Fixing i18n Issues

Generating i18n Reports

Language Support

Globalyzer allows users to scan ActionScript, C#, C/C++ (Windows, ANSI), Delphi, HTML (in various web files), Java, JavaScript, Objective-C, MXML, Perl, PHP, Qt, SQL (Oracle, MS SQL, MySQL, PostgreSQL), XML, Visual Basic (Classic, .NET), and VBScript source code for internationalization issues and will assist you in fixing those issues.

Globalyzer is flexible in its programming language support and can be adapted to support any language not listed.

FAQ

Further information: Globalyzer FAQ

Licensing

Globalyzer can be licensed in a hosted account configuration, where Lingoport hosts the Globalyzer server, or as a Team server, hosted within your company’s network. Globalyzer is licensed based on organizational use as internationalization is a team development activity and ongoing process. Please contact sales@lingoport.com for more information.

You can also try Globalyzer with a Demo Account. Demo Accounts have two limitations: 1) Globalyzer limits the number of internationalization issues it will report on to approximately 100. 2) You will not be able to see or modify Locale-Sensitive Methods for your Globalyzer Rule Sets.

The following lists new features in the Globalyzer 4.3 release.

This release includes various bug fixes and the following new features.

• Shared Globalyzer Projects: Globalyzer project and scan configuration (without scan results) can now be shared. Instead of explicitly importing and exporting projects, Globalyzer manages these tasks automatically, enabling team members to work on the same project seamlessly. See the Shared Projects reference page for more information on how to use this new feature.
• Import/Merge: When importing a Globalyzer project that already exists in your workspace, you now have the option to either Overwrite or Merge. Overwrite deletes your existing project before importing the new one; merge combines the imported project with your existing one.
• Globalyzer Data Directory Location: During Client Installation, you are now prompted for the location of the Data Directory, where Globalyzer stores application data and log files as well as the optional HSQLDB database. The default is [userhome]/.globalyzer, but this can be set to another location.
• Additional Help on Headless Globalyzer Install: The Client Installation download page includes instructions on how to install the Globalyzer Client via a script as opposed to a GUI. You'll want to use this when installing Globalyzer to build machines where Globalyzer scanning can be part of the nightly build.
• Suggested Rule Sets for Unsupported Languages: The Create Rule Set reference page provides Rule Set suggestions for currently unsupported languages.
• File Inspector Report Line Counts: Line counts have been added to File Inspector Reports.

The following lists new features in the Globalyzer 4.2 release.

This release includes various bug fixes and the following new features.

• Objective-C Rule Set: We've added this important rule set to help you internationalize your iOS and other Objective-C applications. In addition to scanning for i18n issues in Objective-C source code, Globalyzer supports string externalization to Objective-C's preferred text resource file type: strings .
• Ability to Assign Rule Sets to Others: Though team members can share rule sets, only the rule set owner can made modifications. This feature facilitates passing rule set ownership to another. Just edit the rule set and select a new owner in the Owner dropdown.
• Launch Client without First Creating a Rule Set on the Server: This feature supports the natural process of using Globalyzer: first create a Project, then run File Inspector, then create Rule Sets and Scans.
• Create Rule Sets from the Client: To facilitate rule set creation, Globalyzer now supports the ability to create new rule sets directly from the Client. You may still want do some customization on the Server, but it's now even easier to create that first set of rule sets as you're running the Client, creating your Globalyzer Project and looking at the results of your File Inspection report to determine which rule sets you'll need for scanning your source code.
• Additional default Scan Views: In addition to All Active, there are now default Scan Views for Priority 1, Priority 2, Priority 1 and 2, Ignore, Invalid, ToDo, Filtered, All, and All but Active and Filtered.
• Notification of Newer Globalyzer Versions on Client Startup: On Client startup, a popup displays if there is a newer version of the Client available or if there is a Client/Server version mismatch; the popup includes a link to the latest Client download.
• Demo Results displayed based on Priority: When a demo user executes scans, up to 100 active results are reported. This feature focuses on reporting mostly higher priority issues. It reports 50 Priority 1 issues, 30 Priority 2 issues, 20 Priority 3 issues, 5 Priority 4 issues, and 5 Priority 5 issues.

The following lists new features in the Globalyzer 4.1.1 release.

This release includes various bug fixes and the following new features.

• Additional options when pseudo-localizing your resource files:
  • Pseudo-localize all your base resource files at one time by using the new Localize All button.
  • Use the new Start and End fields to specify characters to be displayed before and after each string. This helps you quickly identify layout issues where the full string is not fitting. For example [String]
  • You can also specify that each character of the string itself be replaced by an accented character for easier differentiation from English strings. For example Šţŕîñĝ
• Support for Delphi RC resource file type: The Delphi language requires its own version of the RC resource file type. Upon string externalization, a .pas file is created and updated, along with the .h and .rc files.
• .NET Tutorial: To accompany our Java tutorial, the .NET tutorial takes your through the basic steps involved in internationalizing a simple .NET Web application.

The following lists new features in the Globalyzer 4.1 release.

With this release, we have added features to streamline the scanning and filtering process, enhance resource file management, and improve overall scanning efficiency.

• Refine your Rule Set from within the Client: The Globayzer Client now allows you to create both filter and detection rules, rescan your code to see their effects, and update the Rule Set on the server when you are satisfied with the results. This Scan Result driven approach to fine-tuning your Rule Set should help you significantly streamline your scanning and filtering process.
• Prioritize your internationalization work: Globalyzer now prioritizes its locale-sensitive method, general pattern, and static file reference detections (in addition to embedded string detections implemented in version 3.5), helping you focus on the most likely issues first. These priority settings can be customized. You’ll see the priority breakdown both on screen and in the many reports that are provided for you to track and manage your progress.
• Retain and prioritize strings passed to specified methods: Rule Sets now include a new detection, called String Method Patterns. This feature allows you to specifically identify methods that are passed strings that would be displayed to the end user. For example, in javascript we have added confirm, in C# Show, and in java JLabel. By identifying these types of methods and configuring them in your Rule Set, you can set the priority for these string detections and ensure that they are addressed during your internationalization process.
• Disable Scan Feature: Scans can now be disabled. Disabled scans can be configured but are not scanned (automatically or manually) and the scan results are not available/displayed. This feature is useful for limiting the amount of rescanning that occurs when configuring scans. The user can focus on one scan, disabling the others.
• All resource types now support group mode: In group mode, externalized strings are grouped by file in the resource file.
• All resource types now support comments: Comments can be added to resource files and will be preserved during subsequent string externalizations.

Globalyzer 4.0 takes advantage of the Eclipse Integrated Development Environment. The Globalyzer 4.0 Workbench can be installed as a stand-alone application or as an Eclipse 3.7 plugin. This new architecture means you’ll be able to check out source, scan and fix internationalization issues with Globalyzer, build and run with your modifications, and check in your changes, all within your development environment!

Here are only some of the new capabilities you'll have with Globalyzer 4.0:

• Interact with source code repositories from the Workbench: CVS is included with the Globalyzer Workbench; plug-in for other source control systems can be easily added.
• Manage multiple Globalyzer Projects from within the Workbench: Just click on each Globalyzer Project in the Explorer Window to switch projects.
• More powerful searching: Search results are now in their own window for easy management.
• New Resource File Editor: Create and edit your locale-specific resource files and check for duplicate, missing and unused resource keys.
• Improved Globalyzer Help: To ensure that you have full use of Globalyzer, we've added several kinds of help - Context sensitive, Cheat Sheets, as well as an extensive online Help System - all within the Workbench.
• More powerful Project Explorer window: With Eclipse's underlying support, Globalyzer's features can be applied at subdirectory and file levels, giving you much more flexibility in how you do your internationalization work.
• Enhanced editing: Enjoy the full editing capabilities of an IDE from within Globalyzer.
• Plug-in extensibility: Add additional functionality to your internationalization and application development environment using Eclipse's plug-in support.

Be sure to check the help and run a tutorial to get a better idea of Globalyzer 4.0's enhanced usability.