Localization QA: Are You Ready to Be a Global Player?

DZone 's Guide to

Localization QA: Are You Ready to Be a Global Player?

Localization of your application doesn't just stop at translation.

· DevOps Zone ·
Free Resource

What Is Localization?

Localization is the translation of your software. I'm not merely talking about language, although that's a big part. When looking at developing software for markets that you may not be familiar with, it's extremely important to get someone on your team who understands the local culture.

There are four pillars of localization: language, culture, location, and legal.

Language is the most obvious aspect, and is usually where most companies stop. But that's not localization; it's translation, and it ignores crucial societal and cultural factors.

There's also a crucial technical element of localization. Translating something is easy, but making software render non-ASCII characters is an entirely different process.

While translating your app into the correct language is one thing, the product may display characters as the empty box that signals to a user that the program doesn't know how to "read" a certain character. Something similar to "Conf□rm□ng here ple□se." It also signals that your Localization Quality Assurance (LQA) may have been rushed.

While only 25 percent of internet users are English speakers, the rest of the internet has learned to deal with these types of User Interface (UI) issues caused by translations from English.

But should it be that way? If you could run above standard LQA, you'd be able to excite the other 75 percent of users looking for a seamless experience with your product.

So What Are the Advantages of Localizing Products?

Surveys have said that 55 percent of users prefer products in their native languages. That's over half of your potential market. It's also worth pointing out that 70 percent of Fortune 500 companies localize their products. That's a strong signal that the advantages of localizing your product far outweigh any investment that you would need to make.

Where Should I Start with Localization?

That's a simple answer. Start locally.

That means if you've built your product with the English language, you need to make sure that the English you have in your product or website adheres to the meaning you're trying to convey. If you're Snapchat, which has been translated into 31 to 40 different languages, and you need to make a change to the "source" text (English) you'll need to make 31 to 40 changes, just to make it a consistent experience.

It will save you money if you can work from the first language outwards. So spend some extra time getting it right, before starting any localization project.

The second thing you'll need to look at is the internationalization of your product. That means that your program will work as expected in a given language. Localization testing to ensure that your program can "read" and display special characters is the first step to internationalization...and a prerequisite to any localization project.

It's also important to include language settings in the program itself and make the user experience as universal as possible. This will help later on when you need to make changes with your translators.

Translators Are the Key to Localization

If you're going to invest in localization, it's worth looking at the quality of your translators. One of the bigger problems here for a developer is finding a trusted network of translators in the country they would like to enter. Most developers have an idea of the country they want to enter and why, but not necessarily the language expertise in-house to evaluate the quality of translations.

This is where a third-party agency could help assure that quality translations are what you're getting. It's also important to invest in a quality agency. Some agencies will say that they have native speakers only, but do no due-diligence when allowing translators to offer their services. So do your homework and save yourself the headache later.

Having a native-speaking translator is a great first step, but it's also important to employ a native-speaking editor as well. They'll be able to check the quality of translations coming in and give your LQA team a head start.

Native speakers will also point out where a word or phrase is "lost in translation."

For example, in the US we tend to use euphemisms to be polite. In other countries, words like "restroom" and "bathroom" translate directly to "the room where I take a rest" and the "room where one takes a bath".

A good question to ask your users, "Does the app feel like it was created in your country?"

Localization for Localization's Sake

When a company decides to localize for a certain market, it's important to look at the overall costs and investment needed. There are a lot of reputable agencies out there that can help with translations and your LQA project, so they're worth looking at.

Localization can be a big win for companies that get it right, such as most Fortune 500 companies, but it's important to look at the pitfalls and cost-saving measures you can take to make it a success.

With testers currently located in over 80 percent of the world, Testlio offers one of the most reliable localization testing services in the industry. Contact us — or should we say обращайтесь к нам or 联系他们 or võtke meiega ühendust — today!

devops ,localization ,localization testing ,translation

Published at DZone with permission of Lauren Gilmore , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}