Globalyzer 3.7 Release Notes

Should you encounter problems or have questions, please email support@lingoport.com.

This is a minor release, with one particularly useful feature and a few bug fixes:

• File Extension Filters: The new feature we’ve added for this small release allows you to filter files and directories from a scan by setting up File Extension Filters. The filters can be written using Ant patterns (useful when filtering directories) or regular expressions (useful when filtering files with common characters in their path).

The following lists some of the features that are new for Globalyzer 3.6:

With this release, we have added some new programming languages, as well as support to help your team share the string externalization work.

• Qt Rule Set: Qt is a C++-based cross-platform application framework that has good internationalization support.
• ActionScript Rule Set: Globalyzer can now scan and externalize strings from ActionScript code, used in Flex and Flash applications.
• XML Rule Set: Scan attribute and tag data using Globalyzer’s new XML Rule Set.
• MXML Rule Set: Used in Flex applications, MXML is a variant of the XML Rule Set. Scan the CDATA sections using an ActionScript Rule Set.
• Shared String Externalization: Share the work of externalizing strings. Set up in Preferences, Globalyzer prefaces each string ID with your Unique User ID, ensuring string key uniqueness across your team.
• Internationalization Scorecard: While this feature currently must involve Lingoport’s service team for configuration, we have created a new scorecard system that provides a dashboard of internationalization status and progress using XML data collected via scan history using Globalyzer’s Command Line. Please email scorecard@lingoport.com for more details.
• Globalyzer Scorecard webinar recording: We recently discussed the new i18n scorecard in a webinar presentation which also featured guest-speakers Mike McKenna, Sr. Manager, International Engineering, from Zynga, and Leandro Reis, Senior Globalization Program Manager, from Adobe Systems. Click the following link to view the webinar recording of: Is it Internationalized? A New Way to Keep Score.

The following lists some of the features that are new for Globalyzer 3.5:

With this new release, our focus has been on making your internationalization work as productive as possible.

• Streamline your project creation: We’ve added Copy Scan to the Project Properties dialog box, allowing you to set up a first Scan with all its customized settings and then make copies which retain all your prior customization.
• Prioritize your internationalization work: Globalyzer now prioritizes its embedded string detections, helping you focus on the most likely issues first. 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. Issues of other scan types can also be manually prioritized.
• Quickly ignore false positives: With our new features, Ignore this Line and Ignore this Issue, you can now select one or more issues in the Scan Results table, and then choose to append NLS (National Language System) comments at the end of the corresponding source code lines, indicating that Globalyzer is to ignore these issues during its next scan. In combination with Globalyzer’s rule set filters, this is an efficient way to ensure that your scan results only contain valid internationalization issues for your team to address.
• Divide and conquer your work: The Scan Results can now reflect parts of the entire project by clicking on a subdirectory or file in the Source Tree pane and choosing View Directory/File Scan Results. This is an easy way to partition the internationalization work among a development team.
• Locale-Sensitive method grouping: In version 3.4, we added groups to the Globalyzer Server; now we show those groupings in our Quick Summary pane as well as various Globalyzer reports. This allows you to manage and track your internationalization efforts one locale-sensitivie area at a time.
• Use Globalyzer’s new XML report: This latest reporting format rounds out Globalyzer’s extensive reporting capabilities.
• Monitor and manage your globalization work as part of your build process: Globalyzer Command Line and Ant Clients now support an XSL reporting option, which gives you the ability to transform your Globalyzer data into customized layouts and file formats as part of your nightly build. Check out our new XSL Reporting help to learn more about this feature and about the default XSL files included with your Client installation.

With this new release, our Globalyzer Server has been overhauled for increased customization of Rule Sets, along with management features, such as support for teams within your company.

The following lists some of the features that are new for Globalyzer 3.4:

Should you encounter problems or have questions, please email support@lingoport.com.

With this new release, our Globalyzer Server has been overhauled for increased customization of Rule Sets, along with management features, such as support for teams within your company.

The following lists some of the features that are new for Globalyzer 3.4:

• As a Team Member you can:
  • Share Rule Sets with other team members
  • Create and manage Groups of Locale-Sensitive Methods
  • Add new Locale-Sensitive Methods to your Rule Sets, along with help links
  • Save Rule Set data to the Globalyzer Server respository to either download to your local system or allow others to add to their set of Rule Sets
  • All Rule Set data, including File Extensions, Filters and Detection Patterns can now have help associated with them
• As a Manager you can also:
  • Create Project Teams and assign Team Members
  • View a team member’s Globalyzer Client scanning history and usage data which is now sent and available for viewing on the Globalyzer Server
• In addition, as a Globalyzer Enterprise Administrator you can:
  • Alter the default Rule Set data that newly created Rule Sets will have
  • Modify and manage the Globlayzer Client’s File Inspector default groups

And here are some other important Globalyzer features that were available previous to this release:

• File Inspector – Run this Globalyzer Client tool to get an inventory of your application files and their underlying programming languages. The File Inspector also helps you determine which Globalyzer Rule Sets you’ll need to create.
• Batch scanning across multiple programming languages – Internationalization issues are quite different among programming languages, requiring Globalyzer to use different Rule Sets to detect the various internationalization issues. Use our batch scanning process across your multi-language code base. For example, for JSP’s you can combine HTML scanning with Java scanning in one effort.
• Fast performance – How fast source is scanned depends a lot on the code you are scanning, but Globalyzer is running on well over a million lines of code in about the time it takes you to go get a cup of coffee. Subsequent scans are also much faster because of Globalyzer’s intelligence in not repeating work it has done already (e.g. skipping files that have not changed since the last scan).
• Dictionary-based Filtering – Compares embedded strings found to dictionary entries, which helps further filter programmatic strings that should not be translated. This is particularly effective in isolating embedded strings for localization, while reducing the number of custom Rule Set filters to avoid false positive reporting. This feature can be enabled/disabled in the Edit=>Preferences dialog box.
• Scan Results Reason – Scanning results list the filter or detection pattern used in categorizing an issue. For example, if the issue is filtered, the Reason column will display the Rule Set filter that was applied. In the case of a General Patterns scan, if the issue is not filtered, the Reason column will display the Rule Set’s General Pattern that was used to detect the issue.
• Keeping track of issues you want to ignore – Besides Globalyzer’s great filtering capabilities for isolating complex internationalization issues, Globalyzer tracks your code line by line, so that you can elect to ignore, or even emphasize issues, and track and revisit them without Globalyzer needing to insert its own comments in your code. That keeps your code clean, just the way you like it.
• Tight integration between Globalyzer Client and Server – You can quickly navigate to your Globalyzer Server account to access your Rule Sets, customizing them for more refined Globalyzer scan results.
• Command Line, Ant and Maven Support – Command line and Ant integration offer tremendous power in supporting entire teams of developers in monitoring and measuring internationalization. With this integration, Globalyzer can be used in assessing world-wide readiness. Read Globalyzer’s Maven Integration help to assist you in setting up Maven to run Globalyzer Ant tasks.
• Database enabling of Globalyzer Client – Globalyzer Client uses a database for project and scan data. It can use its own embedded (file system-based) database, or you have the option to create a database on an existing MySQL database server. This facilitates comparing Globalyzer results over time, tracking individual internationalization issues across scans and sharing results and fixes with your fellow developers.
• Easy sharing of scan results for fixing i18n issues – Scan results can be quickly and easily exported and imported so that teams of developers can work together to fix internationalization issues efficiently.
• String externalization – String externalization supports both grouped and appended resource files for incremental translation support.
• Globalyzer Client PseudoJudo – Simulate another language for your resource files by adding non-English characters to grow each of your strings by a set percentage.
• Globalyzer reports – With our extensive reporting functionality you can produce summary and detailed reports in various file formats (txt, csv, Excel) for sharing Globalyzer output with your colleagues.

The following lists some of the features that are new for Globalyzer 3.3:

• New Aggregate Summary Report – The Quick Summary information from each of your scans can now be output to an Excel file, for an easy way to report on your overall scanning results.
• New XML Detailed Report – In addition to Excel and CSV format for your scan results, Globalyzer now supports XML format.
• Better PseudoJudo – Simulate another language for your resource files by adding non-English characters to grow each of your strings by a set percentage.
• Maven Integration Help – Read Globalyzer’s Maven Integration help to assist you in setting up Maven to run Globalyzer Ant tasks.
• Command Line and Ant Enhancements – Added support for Batch Scanning from the Command Line or Ant Clients.
• Change your Globalyzer Client’s Data and Log File Directories – Read Globalyzer’s Command Line Client Help for detailed information on how to change the location of Globalyzer’s Data and Log files from its default [userhome] directory.

The following lists some of the features that are new for Globalyzer 3.2:

• Dictionary-based Filtering – Compares embedded strings found to dictionary entries, which helps further filter programmatic strings that should not be translated. This is particularly effective in isolating embedded strings for localization, while reducing the number of custom rule set filters to avoid false positive reporting. This feature can be enabled/disabled in the Edit=>Preferences dialog box.
• Scan Results Reason – Scanning results now list the filter or detection pattern used in categorizing an issue. For example, if the issue is filtered, the Reason column will display the Rule Set filter that was applied. In the case of a General Patterns scan, if the issue is not filtered, the Reason column will display the Rule Set’s General Pattern that was used to detect the issue.
• General Patterns Line Filter – The General Patterns scan now supports a line filter which filters detections based on patterns found in the source code line.
• .properties files – .properties files as a Resource File type are no longer restricted to only Java Rule Sets. Globalyzer now supports this key-value format for all programming languages, allowing more customization and flexibility during string externalization.

The following lists some of the features that are new for Globalyzer 3.1:

• JVM max memory increased – The max memory for the JVM that Globalyzer runs in has been increased to 1024 MB. If you need to modify this (due to memory limitations or other reason) you will need to change the max memory startup argument (in the shortcut or startup script) from “-Xmx1024m” to another value (e.g. “-Xmx512m”).
• File Inspector – You can run this utility to get an inventory of the programming languages you have within your source code, and help with which Globalyzer rule sets you’ll need to create.
• Improved default rule sets on the Globalyzer Server – This gives you better results faster, increasing the number of default filters within many rule sets.
• JavaScript enhancements – Added Unsafe Method support to JavaScript rule set, and string externalization to .JS resource files.
• Client-Server rule set integration – Tighter integration of rule set creation on the Globalyzer server, with auto-updating on the Globalyzer Client.
• String externalization enhancement – Enhancement of string externalization when appending existing resource files for incremental translation support.

The following lists some of the features that are new for Globalyzer 3.0:

• Database enabling of Globalyzer Client – Globalyzer Client now uses a database for project and scan data. It can use its own embedded (file system-based) database, or you have the option to create a database on an existing database server (MySQL or PostgreSQL). This facilitates comparing Globalyzer results over time, tracking individual internationalization issues across scans and sharing results and fixes with your fellow developers.
• Command-line and Ant integration – Command line and Ant integration offer tremendous power in supporting entire teams of developers in monitoring and measuring internationalization. With this integration, Globalyzer can now become the benchmark for localization readiness.
• New reporting functionality – With the new reporting functionality you can produce summary and detailed reports in various file formats (txt, csv, Excel) for sharing Globalyzer output with your colleagues.
• Easy sharing of scan results for fixing i18n issues – Scan results can be quickly and easily loaded into Globalyzer’s Client desktop interface so that teams of developers can work together to fix internationalization issues efficiently.
• Single-pass scanning of large code volumes – Previous versions of Globalyzer were limited in the amount of source code that could be scanned in a single pass, so when you wanted to scan large applications you needed to break up the source. Now with Globalyzer, you can scan literally millions of lines of code at a time.
• Batch scanning across multiple programming languages – Internationalization issues are quite different among programming languages, requiring Globalyzer to use different rule sets to detect the various internationalization issues. We’ve now allowed you to batch scanning processes across your multi-language code base. For example, for JSP’s you can combine HTML scanning with Java scanning in one effort.
• Keeping track of issues you want to ignore – Besides Globalyzer’s great filtering capabilities for isolating complex internationalization issues, Globalyzer now tracks your code line by line, so that you can elect to ignore, or even emphasize issues, and track and revisit them without Globalyzer needing to insert its own comments in your code. That keeps your code clean, just the way you like it.
• Faster performance – How fast source is scanned depends a lot on the code you are scanning, but Globalyzer is running on well over a million lines of code in about the time it takes you to go get a cup of coffee. Subsequent scans are also much faster because of Globalyzer’s intelligence in not repeating work it has done already (e.g. skipping files that have not changed since the last scan).
• New look on the interface – We redesigned the Globalyzer Client’s UI, giving it an updated look and feel. We did this to enhance usability and provide flexibility for upcoming feature enhancements.
• Improved programming language support – Globalyzer already supports a wide variety of programming languages, and we’ve enhanced the support.
• Tighter integration between Globalyzer Client and Server – You can now quickly navigate to your Globalyzer Server account to access your rule sets, customizing them for more refined Globalyzer scan results.