Home

Login
 
Learn More
 
About Us

Globalyzer's Latest Improvements

Our engineering team at Lingoport is always working with our customers to meet their demands for internationalization capabilities. Many internationalization efforts turn out to be an exercise of exceptions and special cases unique to an application. It's why we made Globalyzer so flexible right from version 1. And because we provide globalization & internationalization services that are highly leveraged by Globalyzer, we are constantly cycling practical enhancements into Globalyzer. Here's the short list of what's new in 2.4 and 2.3 along with brief explanations. If you need additional information or if there's something else you need in Globalyzer, please contact us.

What's New in Globalyzer 2.4:

   Improved HTML String Detection
   Expanded Support for Pseudo-Localization

What's New in Globalyzer 2.3:

   Added programming language support
   PseudoJudo, pseudo-localization module
   Filtering enhancements
   Report distribution spreadsheet export

Improved HTML String Detection
Believe it or not, HTML is one of the hardest languages to parse for internationalization issues. It's not structured in the same way as programming languages such as C++, Java and C# and therefore a different approach to parsing it is required. We found that no matter how we tweaked our old HTML internationalization engine, we were still missing some strings. We ended up adapting an entirely new approach to parsing HTML and are happy to report both higher accuracy (finding all the strings, plus less false positives) and much faster performance. It's a big win for all of us, with higher project accuracy, faster scanning, and less clean up needed in testing.

You can take advantage of the HTML improvements for projects using JSPs, ASPs, ASPX or any HTML code. You still have to separately scan for embedded Java, VB, C++ and C# as internationalization logic for these programming languages is completely different than the HTML portions.

PseudoJudo Improvements
We expanded PseudoJudo to work with entire directories of resource files rather than just one at a time. PseudoJudo's pseudo-localization capabilities, added for our 2.3 release, have been extremely popular for our clients. PseudoJudo let's you pad resource files with characters from your target locale, while expanding strings as well. It lets you test for internationalization without waiting for translation, also allowing your testers not to need to speak the target language. For more information, on how PseudoJudo works, please go here. PseudoJudo started as an internal tool we were using on internationalization service projects, and it was natural to make it part of Globalyzer. The improvements in Globalyzer 2.4 allow you to point PseudoJudo at whole directories of files, rather than one file at a time. Within the Globalyzer client, select the tools menu to get started. Email support@lingoport.com

Added programming language internationalization support:

  • PHP - including detection, filtering and string extraction
  • Expanded support for Delphi string externalization
  • SQL scanning for Oracle, Microsoft SQL Server, MySQL and PostgreSQL

PseudoJudo, pseudo-localization of resource files:
      This new module within Globalyzer lets developers and testers review and test their products in multiple languages, without waiting for translation, and without having foreign language skills. We're especially excited about this improvement as it's been a big time saver for all our own service projects and a highly requested feature. Pseudo-localization is done by adding "pad" characters around messages that can include various character sets, and interface geometry expansion depending upon marketing locale requirements (e.g. German almost always takes up more interface real estate as compared to English). We call this feature and process PseudoJudo just for fun. A couple of screenshots of what we mean are below:


Setting Up to use PseudoJudo (Click to enlarge)


Resource Files Before and After (Click to enlarge)

Expansions on filtering capabilities:
      Helps our customers filter out possible false-positive reporting, pinpointing internationalization issues even more accurately in large amounts of code:

  • Method Line Filter (filter method detection based on a programming pattern within a line of code)
  • Image Filter (filter image detections based on pattern that matches path + filename)
  • Image Line Filter (filter image detections based on line pattern)
  • String Retention Pattern (allows you to override String Literal Filters)

Reporting improvements:
      Distribute Detailed Globalyzer Reports using Excel with automated exporting and formatting. While this capability was always in Globalyzer, it has been expanded to help you produce and circulate reporting results to others in your company. Detailed reports list internationalization issues detected by category along with their line number and file information. Summary reports providing issue totals and hyperlinks to suggested remedies are provided in HTML format.