The Ultimate Guide to JavaScript i18n

Why It’s Important to Internationalize Your JavaScript

Internationalization (i18n) is the process of preparing software so that it supports local languages and cultural settings. In other words, JavaScript i18n is the process of making your JavaScript application localization-ready. An internationalized product supports the requirements of local markets around the world, functioning more appropriately based on local norms and better meeting in-country user expectations.

Benefits of JavaScript i18n include:

  • Higher quality software that meets the technical and cultural needs of multiple locales
  • Reduced time, cost, and effort for localization (L10n)
  • Single source code for all languages of the product
  • Simpler, easier maintenance for future iterations of the product
  • Greater in-country customer acceptance and satisfaction

The global software market is increasingly growing in demand and volume. Many major software companies derive the majority of their revenue from markets other than the country in which the company was founded. Going global often leads to revenue growth for software organizations.

If you have international users, or if you plan to move into additional international markets, it behooves you to not only internationalize your JavaScript but to also localize your product to deliver both the linguistic and cultural experience that a local user would (and should) expect.

The Risks of Not Internationalizing Your JavaScript

If you choose to skip internationalizing your JavaScript, be prepared for several significantly negative ramifications, including lower sales, weakened competitiveness, and frustrated local users.

It will start when your JavaScript application is confusing to use for a native speaker. When they review and spread the word about the product’s subpar and confusing interface your initial market impression will be poor. Although your audience will want your software’s functionality, they will want and expect an experience tailored to their needs, much as you’ve accounted for in your domestic market.

You may be able to attract early adopters without internationalizing, but for many markets you won’t be able to achieve deeper market penetration. Users will be contacting you and tying up your tech support to understand miscommunicated or simply poorly identified aspects of your program and likely demanding fixes for a number of small internationalization bugs that should have been addressed before the program was released. As word spreads you will have introduced a need for direct competition to your offering in the market.

There’s a better way. Internationalize from the start and satisfy the needs of local users in your global markets.

JavaScript Internationalization Resources

Internationalization & Localization Software

Lingoport Suite is your operating system for exceptional global software, empowering more than 300,000 developers to release software in global markets successfully.

  • Internationalization Software
    With Lingoport Globalyzer, find and fix i18n issues that inhibit localization and global user experience during development. Catch up on i18n technical debt. Avoid rework. Eliminate the manual tracking of locale updates. Collaborate on your i18n efforts via Slack.
  • Localization Process Software
    Make localization proactive using Lingoport Resource Manager. Eliminate error-prone, tedious, manual processes that slow down localization. Detect & manage changes to resource files in your source code. Streamline translation jobs. Automate localization updates between development and translation. Collaborate on your L10n efforts via Slack.
  • Linguistic QA Software
    With Lingoport InContext QA, quickly identify an issue during linguistic QA, enter in a new translation, edit directly on your screen, enter a bug, and have the file automatically updated after approval using your workflows. You’ll be editing directly in the context of your software. No more screenshots!

Questions?

Questions about JavaScript i18n? Contact us for a consultation or to schedule a demo of Lingoport Suite, our i18n software suite.

Top 5 i18n Summer Reading Picks

Perhaps you’re feeling a tad guilty about reading that tawdry novel while on the beach? Here’s some highlighted reading from our globalization archives that will balance things out for you:

i18n Summer Reading 11) The Fastest Growing Global Markets of 2018

Around vacation time everyone likes thinking about travel. There’s no better time to review which of the global markets you should considering entering by the end of this year and see if you can’t make a great argument for a working vacation before the next holiday season.

https://lingoport.com/fastest-growing-global-markets-in-2018/

i18n Summer Reading 22)  2018 Language Services Market Overview

Everyone enjoys a quick read. Common Sense Advisory’s 2018 Language Services Market Overview can be read in just a few minutes. With 10 compelling facts, you’ll feel more knowledgeable about the industry than before you clicked.

https://www.commonsenseadvisory.com/Research/Market_Overview.aspx

i18n Summer Reading 33) The Finnish Language Services Market

Sometimes digging into the details gives the larger picture more context. Nimdzi has done just that by exploring many of the peculiarities of the Finnish market.

https://www.nimdzi.com/finnish-market-2020/

i18n Summer Reading 44) JavaScript Internationalization – the Good, the Bad, and the Ugly Whitepaper

This reading is more technical, providing instruction for i18n within JavaScript. This whitepaper gives a great overview for developers and localization specialists alike.

https://lingoport.com/javascript-whitepaper/

i18n Summer Reading 55) Going Global

We saved the best for last. This book is an absolute must for any business looking at starting or expanding their global presence. Anna Schlegel has written the book you need to read if you want to succeed in an increasingly competitive global economy.

https://www.trulyglobalbusiness.com/about-the-book.html

 

There’s always more on the Lingoport.com blog and resources page.

Happy Summer!

New Webinar: Next Generation In-Context QA

Watch Lingoport’s webinar, Next Generation In-Context QA, and learn about our new InContext QA product, which helps your team eliminate the frustration of linguistic QA for agile global software releases.

View i18n Webinar Recording

Webinar Date/Time

Date: June 26, 2018
Time: 9am Pacific | 12pm Eastern | 17:00 CET
Duration: 30 minutes, plus audience Q&A

Linguistic QA

The de facto practices for linguistic QA are awkward. Linguistic review often happens late or after development, with the reviewers or in-country stakeholders capturing a screenshot, circling an issue and submitting a bug with suggested changes. Fixing bugs often goes unaddressed or is handled late, only after release.

No More Screenshots!

Watch the webinar recording, and learn how, through the use of Lingoport InContext QA, you can quickly identify an issue, enter a new translation, edit directly on your screen, enter a bug, and have the file automatically updated after approval using your workflows. No more screenshots! You’ll be editing directly in the context of your software.

View i18n Webinar Recording

i18n Quick Planning Guide

Internationalization (i18n) is the process of preparing software so that it can support local languages and cultural settings. Let’s say you land a new contract with a company in Japan, or your management team is looking to make an aggressive push into the EU. Then internationalizing your software is the path towards meeting the needs and expectations of local users in those markets.

Software i18n, though, involves many steps and is difficult to achieve efficiently and reliably without the proper step-by-step methodology. The wrong execution can have major ramifications for your development team’s time and your company’s revenue.

To that end, Lingoport has published the i18n Quick Planning Guide to ensure a more successful i18n process. Submit the form below, and receive the guide via email.

Enter Your Information to Download the Planning Guide

  • This field is for validation purposes and should be left unchanged.

What Is i18n?

Internationalization (i18n) is the process of preparing software so that it can support local languages and cultural settings. An internationalized product supports the requirements of local markets around the world, functioning more appropriately based on local norms and better meeting in-country user expectations.

Let’s say you land a new contract with a company in Japan, or your management team is looking to make an aggressive push into the EU. Then internationalizing your software is the path towards meeting the needs and expectations of local users in those markets.

I18n is often misrepresented as Localization (L10n) and sometimes even Translation. I18n is product development focused so that in the case of software, one code base is made capable of supporting worldwide languages and locale-specific formatting and behaviors. It’s a critical and sometimes underestimated step that is needed for successful and scalable L10n. Conversely, Localization makes a product specific to a target market or region(s), including translation of the interface and possible adaptation of terminologies and more.

Releasing software that has not been properly internationalized can lead to many problems, including lack of market acceptance. Addressing and fixing i18n bugs after product release results in additional costs, time, resources, and a potentially damaged reputation in local markets. Retrofitting a product for a global market after release, in contrast to internationalizing the source or during development, can be time-consuming, costly, and provide alternative products with a competitive advantage.

What Does Software i18n Involve?

Typical software internationalization tasks include:

  • Developing software to be independent from a specific language or limiting character set, and independent from cultural conventions (e.g., date display, time display)
  • Locale Frameworks
  • Achieving Unicode compliance
  • Elimination of hard-coded text (strings) in the code
  • Removal and reworking of concatenated strings
  • Support for collation of data
  • Support for bi-directional languages, such as Hebrew and Arabic
  • Plus more, including issues that may be application and market specific

Benefits of Internationalizing Software

Benefits of software i18n include:

  • Higher quality software that meets the technical and cultural needs of multiple locales
  • Reduced time, cost, and effort for localization (L10n)
  • Single source code for all languages of the product
  • Simpler, easier maintenance for future iterations of the product
  • Greater in-country customer acceptance and satisfaction

i18n Stories

Companies come to Lingoport with their i18n problems, so we’ve seen a lot that can go wrong with global software releases. Here are some brief examples:

One company had been internationalizing for years, but had persistent i18n bugs that garnered complaints. When counted, there were nearly 500 of them on one product alone. That’s a significant impact, expensive to fix and distracting from new features. By using Lingoport software to support ongoing development, they can now measure and fix i18n issues during development, which is much faster and results in a higher quality global product experience. Using Lingoport’s Globalyzer and Lingoport services assistance, they are working their way through the i18n bugs.

Still another company knew they had an i18n business case, but it was not immediate. They hired summer interns to externalize strings and perform minimal i18n adaptations. Without good direction or appropriate skills allocation, they didn’t get very far. They then sent the i18n offshore to a general contractor, spent over $500,000, and still didn’t have a properly internationalized application. In the meantime, they didn’t feel they were much closer to product readiness, and were passing up new opportunities.

Continuous Internationalization & Localization

Agile development has changed i18n and L10n tasks dramatically, as software changes faster but in smaller increments. It’s easy for i18n and L10n to fall behind. Regarding i18n, it’s often not apparent to a developer that there is an i18n problem in the code they are writing, as the scope of i18n is broad and there are QA challenges. For L10n, there is all kinds of management and manual task overhead, as files get moved around and updated. We believe that some of the biggest globalization efficiency gains for software companies to realize will be in systematically and continuously integrating i18n and L10n with agile teams, rather than hoping to find and fix issues in QA cycles when the development team may have moved on.

The key here is automation. Not necessarily of the actual translation via some machine translation, but managing legacy and new development for i18n issues and moving files for localization from the build to the translator and back again in a very visible and verified manner.

To do this, we automatically monitor software code repositories for i18n and L10n changes and issues/violations.

Continuous i18n and L10n features include:

  • Visibility – Dashboard measurement and drill-down of i18n and L10n violations and changes via static analysis of source code repositories including tools for fixing problems early during development
  • Automation – i18n support in the developer’s IDE, upon check-in and regularly run on targeted source code. Automated analysis, verification and exchanging of localization resource files from the build to translation (or translation management technologies) and back again to the build for staging and linguistic QA
  • Metrics – Tracking progress, coding quality, translation timing and more so that you can plan and improve
  • Integration – Integration with the tools that you are already using, such as a Translation Management Solution (TMS) and Slack for communications

As you add and update features and locales to your software, you have an automated framework for faster, trouble-free global releases.

Why Continuous i18n and L10n is important:

In practice, most software development endeavors treat localization as a delayed and often manually managed process, outside of ongoing sprints and releases. This is contrary to agile and good software development management practices.

There’s all kinds of “bookkeeping” issues around managing what’s changed, missing files, getting it out for localization, then putting it back in the source code. By its nature, this delays the process, lends itself to handling errors later when the teams have moved on, shortchanges QA efforts and delays localized releases. It’s costing you time, headcount, and cleanup, and it impacts the global imperatives of your company. Continuous i18n and L10n is simply a much more effective strategy.

i18n Implementation Tips

For legacy i18n refactoring and new development:

1. Learn, Build and Support the Business Case
Continuous i18n and localization (l10n) in support of agile development is going to have a cost. Unless the business case is defined, the project is unlikely to get done. Make sure you build a strong business case to compel all team members to align on i18n implementation.

2. Clarify Your Global Release Objectives and Concurrent Development
i18n touches a good deal if not all of your application, rather than being like adding a feature or fixing a bug in a particular sprint and area of your code. It usually involves more than your software’s presentation layer, as data is input, stored, transformed and retrieved. When internationalizing your product for the first time, you’ll need a branching, merging and testing strategy that covers the full i18n scope.

3. Assess and Document Requirements
Establish user requirements as they relate to target locales. i18n is almost never just a string externalization exercise you can pass to an intern. You’re going to need to put some thought into locale requirements, how data is going to flow through your application, changes to your database, methods/functions/classes that will have to be made locale-aware and of course the U/I and all it’s strings.

4. Build a Plan
An i18n project plan typically starts with about 200 tasks and increases with size and complexity (consider this for multi-tiered applications). To build this type of plan, one option is to analyze the code base with Lingoport’s i18n software product, Globalyzer, which provides detailed static analysis on internationalization issues that will need to be addressed. Combine that with architectural analysis from whiteboard discussions and requirements documentation.

5. Reduce Risks and Manage Trade-offs
Being late in deploying your global software is very costly to your business. The risk can be a broken agreement, market launch and business plan. A three-month delay may make an annual revenue goal unattainable. Ensure that your executive management team is fully bought in to your i18n efforts, and that your team has the budget, resources and tools to get the job done efficiently, reliably and successfully.

Internationalizing a large application is generally resource intensive. In cases where you have lots of legacy code, you may need an implementation partner in order to keep up with ongoing development objectives outside of internationalization.

6. Long Term Support
Once you internationalize and localize your software, your ongoing development has a new set of requirements. Measure i18n just like any other coding quality. Do not wait until testing to find out if i18n is broken. For your ongoing agile development, it’s good to automate the management of changes to strings that may change somewhat with every release.

Common Mistakes Made When Trying to Internationalize

Be sure to avoid these 10 common i18n process mistakes:

1. Don’t Forget What Drives Internationalization
Your company’s top and bottom lines. The costs of being late or delivering lousy quality products endure beyond any benefits of cutting corners on development.

2. Don’t Assume Internationalization Is Just an Older Software Legacy Issue
No framework, whether it’s React.JS, J2EE, .Net, Java, Ruby on Rails, PHP or whatever is new and improved, internationalizes itself. You still need to perform all the steps necessary to implement locale and all the associated i18n practices.

3. Don’t Assume You Can Treat Internationalization Like Any Other Feature Improvement When It Comes to Source Control Management
It’s typical for new feature development and bug fixing to be conducted in parallel with i18n. However, in the process of performing i18n, you are going to be breaking major pieces of functionality within your application as you make large changes to your database and other application components. In order for respective developers to work on their own tasks and bugs, you typically need to branch code, often with specifically orchestrated code merges.

4. Don’t Assume Internationalization Is Just a String Externalization Exercise
String externalization is important and highly visible, but the scope of i18n includes so much more. For example: creating a locale framework, character encoding support, major changes to the database, refactoring of methods/functions and classes for data input, manipulation and output.

5. Don’t Wing It on Locale
Designing how locale will be selected and managed often doesn’t get the amount of thought and planning deserved. How the application interacts with the user, detects or selects locale, and then how it correspondingly behaves is a design process needing input from an experienced architect, product marketing and the development team.

6. Don’t Create Your Very Own Internationalization Framework
Various companies have half-way implemented internationalization using their own homegrown methods for string extraction and locale management when there were already well established methods provided within their programming language framework or established solutions like ICU. Using these methods or solutions will ensure that your code is far easier to maintain. No unpleasant surprises.

7. Don’t Think That the Team Internationalizing Your Software Can Work without a Working Build
Without a working build, the developers can’t smoke test the changes they are making. Even if you provide a dedicated QA person, developers need to be able to compile and run themselves to head off problems later. It’s too hard to rely on reconstructing coding errors at a later time and make for unnecessary bug fixing iterations, lost time and poor quality. It’s odd that we even have to mention this, but it comes up.

8. Don’t Run Out of Money
I18n planning often suffers from underscoping. Lapses in funding can cause expensive delays, as new funding takes more time than anyone imagined to get approved. And chances are, if you need to ask for more money, than you also need more time, which brings you back to consequences regarding tip #1.

9. Don’t Use a Half Thought-Out Character Encoding Strategy
Use Unicode, rather than native encodings. If you have budget and time constraints and you’re only targeting dominant languages in markets like Western Europe, North and South America, you can often get away with ISO Latin – 1, but even for Eastern European languages, go Unicode. Then when you do, make sure your encoding works all the way through the application.

10. Don’t Use Your Same Testing Plan, or Just Rely on Localization Testing, When Your Functional Testing Needs to Grow to Include Internationalization Requirements
Use pseudo-localization of not only the interface, but send test data using target character sets, locale altered date/time formats, phone numbers and more, from data input to database, to reports and so on. In your pseudo-localization testing, expand data fields to fit physically longer strings, accounting for expanded strings from translation. Pseudo-localization is automated when you use Lingoport’s Resource Manager.

State of the i18n Industry

Lingoport recently conducted The State of Continuous Internationalization & Localization Survey. There’s been plenty of talk within our industry about making i18n and L10n continuous, automated and in step with Agile development. However, we wanted to uncover the true state of the industry and therefore launched the survey.

The reality is, the industry still has a long way to go… For example, only 8% of respondents thought they did an excellent job at measuring and managing i18n requirements. Download the report to see where the industry stands on localizing for every sprint, the lag time between feature releases and L10n turnaround, and other global software development issues.

Download the survey results.

Lingoport’s Market-Leading i18n Software & Services

Lingoport is the premier i18n software and services company in the market. If you are looking for software, or for i18n assessment, consulting or implementation services, we encourage you to explore the following links and to contact us at any time.

  • Lingoport Globalyzer – Find and fix i18n bugs. Lingoport Globalyzer is your operating system for exceptional global software. Avoid rework. Find and fix i18n issues as the code is written. Default rules and machine learning pinpoint existing i18n issues in source code for a wide variety of programming languages and database scripts. Improve your agile software development for global markets with Lingoport’s flagship i18n software.
  • Lingoport Resource Manager – Automate change detection and export/import resource files for localization with Lingoport’s localization process management software. Eliminate error-prone, manual processes and save thousands of hours of engineering time.
  • Lingoport Dashboard – The hub of our i18n suite. See it all, drill down, create notifications and manage the process. Bridge gaps between localization & development. Increase visibility and track globalization metrics.
  • Lingoport i18n Services – Benefit from our 17 years of experience. Enjoy expert teams for software i18n assessment, planning and implementation.

Lingoport Webinar: Highly Effective i18n Planning

JavaScript Internationalization – the Good, the Bad, and the Ugly Whitepaper

There are many standard practices to follow when implementing proper internationalization (i18n). For those looking to understand the details of proper i18n when coding in JavaScript we’ve put together this white offering.

Download “JavaScript i18n-the Good, the Bad, and the Ugly” whitepaper, which will allow you to leverage the expertise of Lingoport’s experts to improve your i18n JavaScript.

Submit the form below, and the whitepaper will be emailed to you.

Current Locale Resulting Block | Internationalize JavaScript

Enter Your Information to Download the Whitepaper

  • This field is for validation purposes and should be left unchanged.

Feature Release: Lingobot IDE – make the i18n workflow even more efficient

For those looking to get through their i18n (internationalization) workflow in less time, we are introducing a new feature. Lingobot will now be accessible within development’s IDEs (Integrated Development Environment) such as Eclipse, IntelliJ, or Microsoft Visual Studio. Meaning users can now push i18n commands, check on L10n (localization) status and more directly within their development environment.

New Face for Lingobot

This new access point is a direct extension of Lingobot, which means developers have direct access to push commands through the Lingoport Suite without leaving their work environment. Lingobot has previously been available through collaborative tools such as Slack or Flowdock. Either method allows the team to leverage the power and benefit of Lingobot, at whichever point is most convenient, keeping them focused on the task at hand.

Project List

Dropdown

Lingobot functionality can be accessed via prompts with a command line which is a direct but unintuitive approach. This new access reaches beyond and can integrate a dropdown menu for i18n commands directly within the IDE. Meaning strings can be pushed for translation with a couple of clicks. This also means developers don’t need to reference a syntax guide any time they want to push an i18n command. The drop-down menu is easier to use and far more accessible.

Developers are now able to check for critical errors, pseudo-localize, view their projects, or even view the status of translations in a specific branch of their program without ever clicking away from their code.

Lingobot Menu Options

Reporting

Lingobot will also track the status of translations in real time. This means even to check on the progress of a project developers won’t need to leave IDE. This also allows users to react more quickly. If users are waiting for the translation to come back before taking the next step in a project they can keep an eye on the progress in their work environment. This helps cement coordination with the localization effort, by not needing to click between applications. 

Lingobot Translation Status

Now anyone needing to access the power of Lingobot can do so directly through the Lingoport Suite, via their collaborative tool, or even directly in their IDE.

This new IDE access is but one feature to make i18n work for your company while your team spends less time working on i18n.

If you’d like to learn more about this or other features please contact us.

Lingoport Releases Globalyzer 6.1: Machine Learning and more

Breakthrough for Software Internationalization with Machine Learning

TLDR: Globalyzer finds and fixes internationalization issues that are complex and important for creating software for worldwide customers. Highlights:

  • New machine learning accelerates i18n issue detection accuracy, lowers false positives
  • More intuitive tuning than existing methods
  • Faster time to global releases

5/14/18

For Immediate Release

Lingoport has released Globalyzer 6.1, which adds the power of machine learning to find internationalization (i18n) issues faster, and with pinpoint accuracy, over multiple programming languages and database scripts. Machine learning makes i18n easier and more intuitive.

Globalyzer’s Machine learning is a step forward in automatically and accurately finding internationalization (i18n) errors within source code as it’s being written or checked in. Machine learning makes customizing i18n detection faster and more accurate while eliminating false positive detections quickly.

Internationalization is the first step to making applications that behave elegantly in terms of regional formatting and other requirements. It’s a critical but difficult requirement for software companies looking to expand their reach in worldwide markets. Finding i18n issues early in software development, when they are fast and easy to fix, saves time to market and expense.

Source code has unique conditions that can make i18n detection challenging. Often what is wrong in some cases is perfectly fine in others. For example, elements can seem to need translation, that in some cases have become programming variable names, which creates an i18n false positive detection. Globalyzer has always had methods to manage problematic false positives, however, machine learning makes customizing Globalyzer’s many default programming language i18n rules three to five times faster, with better immediate results and a more intuitive tuning process.  

Lingoport’s Globalyzer is used by many of the world’s best known technology companies, supporting development for worldwide customers. These companies avoid i18n and L10n rework and produce a high quality user experience concurrent with their new development and product releases.

“Managing false positives is the number one concern we hear from developers, so it’s exciting that our team has built a new approach that’s easy and straightforward,” stated Adam Asnes, Lingoport’s CEO. “With Machine Learning, Globalyzer becomes even more adaptable for the speed of agile development globalization.”  

Globalyzer 6.1. Includes additional features, such as access to Lingobot within the developer’s IDE. Release notes are available here: http://bit.ly/2rCTyTz


About Lingoport:

Lingoport provides a software suite and professional services that enable globally focused companies to create and maintain software that works elegantly in every language and locale.

The Lingoport Suite includes Globalyzer, Resource Manager, and Lingoport Dashboard. Working together, these products continuously monitor, fix and manage both internationalization and localization in each software sprint and release.

www.lingoport.com

Contact: Adam Asnes, aasnes@lingoport.com

Address: 3180 Sterling Cir #201

   Boulder, CO

   80301

###

Globalyzer 6.1

Machine Learning and New Bot Assistance Enhance Software Internationalization

Lingoport is releasing a major update to Globalyzer, which helps globally focused technology companies develop software that is internationalized to support worldwide languages and cultural formats. The release leverages machine learning to help developers pinpoint internationalization (i18n) issues in code faster, with more intuitive controls.

Lingoport’s Globalyzer 6.1 Release improvements include:

  • Machine Learning to fine tune internalization error detection within software
  • Ability to customize the string comparison dictionary
  • Lingobot access via developer IDE
  • Rule Set Importing Enhancements

Machine Learning

Machine learning capabilities add a whole new and exciting method to address false positives that occur when first setting up and tuning Globalyzer i18n code scans. I18n issues can be initially misleading; as they can be conditional depending upon coding context. The ability to save time during internationalization tuning is compounded as machine learning is conditioned by user input.  The team will mark logged errors as true or false as they progress through reports which will improve the reporting of future results.

Managing false positives is the number one concern we hear from developers, so it’s exciting that our team has built a new approach that’s easy, straightforward and even a little addictive to use.” stated Adam Asnes, Lingoport’s CEO. “With Machine Learning, Globalyzer becomes even more adaptable for the speed of agile development globalization.”  

You can see Globalyzer’s machine learning in action here.

Customizable Dictionary Detection

Bolstering the user’s ability to combat false positives includes updates to Globalyzer’s  dictionary comparison functionality. Users can now update the default dictionary and ensure that any approved language doesn’t populate as an error during reporting. Coupled with the improvements of Machine Learning users have enormous control over error reporting.

Lingobot from within the IDE

Developers will be able to access Lingobot, which helps users launch batch Globalyzer and Resource Manager functions, from within their development application or IDE (Integrated Development Environment). Common actions include pushing new content for localization, checking the status of a current project, and running a check on the code for internationalization errors.  

This new Lingobot extension offers a drop-down menu that can be plugged into the interface which can access all the same functionality. The same functionality can be accessed via command line interaction as well, allowing developers to choose whichever method to access the tools of Globalyzer that works best for them. Lingobot was previously accessible via collaboration tools such as Slack, which for some Lingoport customers, were prohibited due to IT security policies.

You can read more about this Lingobot feature here.

Globalyzer 6.1 also features bulk rule set imports, terminology improvements and bug fixes.

The release notes for Globalyzer 6.1 can be read here.

Please feel free to contact us with any questions or comments you have about this release.

New Webinar: Highly Effective i18n Planning

Watch Lingoport’s webinar, Highly Effective i18n Planning. During the webinar, we advise you on a step-by-step planning methodology for achieving a reliable software internationalization (i18n) process.

View i18n Planning Webinar Recording

Webinar Date/Time:

Date: May 29, 2018
Time: 9am Pacific | 12pm Eastern | 17:00 CET
Duration: 30 minutes, plus audience Q&A

Step-By-Step i18n Planning

There are many ways that i18n efforts can go wayward, costing you time, resources, and revenue. During the webinar, we outline the specific planning steps required for more reliable software i18n success. The steps are essential knowledge for anyone involved in software i18n, including localization professionals, product and program managers, scrum masters, product owners, development managers, and senior engineers.

I18n Planning Guide

Complementary to the webinar, download Lingoport’s i18n Quick Planning Guide. With both the webinar and the guide, you’ll learn what it takes to achieve a smooth, efficient, and effective i18n process.

View i18n Planning Webinar Recording