Gremlins aren’t new. They have existed in literature and entertainment for centuries – and they happen in i18n (internationalization). For a number of our clients, internationalization bugs are well over 50% of the backlog in their localization entries in bug tracking databases!
i18n Gremlins – in real-life software development – are often not immediately obvious (like those pesky alien monsters) and typically are not found until late in the development cycle.
They are annoying bugs for localized products that detract from your product quality for worldwide users. They might not break your code, they’ll just give it trouble and make it act in unexpected ways.
It’s hard on development, puts localization teams at a disadvantage, and slows releases.
Even worse is when your code has i18n gremlins (bugs) that are allowed into a release – your software can’t function the way it was intended, leaving users, support, and your development team with an expensive and time-consuming fix.
Of course, at Lingoport we know that gremlins don’t have to be a thorn in the side of your development team. In our webinar, Common i18n Gremlins and How to Squash Them we share how to avoid the worst of bug-related issues:
- The major types of i18n bugs and why they persist
- Testing is good, but it’s late in the process
- i18n in the developer’s continuous development daily workflow
- i18n for legacy issues – burning down the bugs
- i18n impacts on localization files
- Making testing and Localization QA continuous and in-context
Lingoport offers the tools you need to handle i18n bugs without the delays that can cause your software to have release delays – and lost customer opportunities.
i18n gremlins can be dealt with easily and quickly with Lingoport’s Globalyzer. This innovative enterprise tool is designed to find internationalization (i18n) bugs in your code during development, creating better-globalized products. We’ll show you how globally focused enterprises can kill i18n bugs before they become an issue, or exterminate the existing bugs.
The combination of Lingoport’s Globalyzer, Localyzer, and Localyzer QA, work together to help your team squash bugs and fix them before they become a problem with continuous automated checking during the development cycle.
Localyzer automatically pulls U/I strings from source code to TMS or translation portal and then puts it back when complete, all without needing any human touch. It kills localization file bugs or missing translations by verifying the files for over 40 issues that would impact quality. It also updates the U/I with continuous, configurable pseudo-localization that lets your testing team do their work without them needing to be target language proficient. You can even optionally automate machine translation which can be quickly updated with human review.
Unlike any other tool, LocalyzerQA lets your translators and in-country stakeholders review screens and suggest linguistic changes. Once approved, those changes are automatically updated in source code files with edits also tracked in your TMS.
I18n and L10n Bugs can be handled in hours, not days.
Ready to learn about the most common i18n bugs and how to fix them? Check out our informative infographic A Cheat Sheet for i18n Issues which will give you a summary of common i18n issues that break localization, creating bugs in localized versions.
Join us for even more information about i18n bugs and how to fix them at our newest webinar (May 4th – register here) where we will look at i18n bugs, why they keep getting introduced into code, why they are hard to fix, and HOW YOU CAN STOP THEM EARLY.
P.S. On that May 4th date, we’ll be performing i18n and L10n for a Star Wars themed application. May the fourth be with you!