Software Localization FAQ

My company followed software localization and internationalization best practices during development. Should we still do testing before getting our resource files translated?

Unless you have done some formal testing, you should consider testing before your resource files are translated. Pseudo-translation testing does not take much time; but it may save you a lot of time. For example: a single defect in pseudo-testing will substantially multiply with the number of languages that you localize into if it’s not corrected before testing. Considering the cost of a defect in its lifecycle, avoiding duplication is always a smart business decision. Globalme also recommends that you perform pseudo-testing on localized operating systems as you may discover additional issues before the formal localization testing cycle begins.

My company has the resources and will be localizing in-house, however there are areas where we need help. Can we get on demand help from Globalme?

Yes. Since 2005, Globalme has been providing support to many language service providers and software companies across the globe and has experienced and dedicated engineering, linguistic, and project management resources available to all of our customers. Help is usually requested in the following areas:
Localization quality assurance: Since 2005, Globalme has been providing localization quality assurance and localization resourcing services across the globe and is considered to have the best localization training and resourcing structure in the industry. If you require a QA cycle after each of your in-house handled engineering and translation activities, require experienced on-site resources or simply need a third party to review your existing localized software, Globalme has the answer.
Localization engineering consulting: Since all of Globalme’s engineers are localization experts, it is easier for them to root cause a localization issue. Our experts also provide internationalization consulting and can tailor these services to fit your company’s needs.

My company is starting software development and is considering localization, where do we begin?

It is very important that you do not ‘postpone’ localization, but that you treat it as a mainstream development activity. The best thing for you to do is to contact us as soon as possible so we can conduct a review of your product and design requirement documents. Why? Because this process will allow us to provide you with feedback on how you should proceed. We will also provide you with an internationalization checklist, additional information on localization best practices, and conduct a presentation to help educate your developers in building localization-friendly applications.

When is the best time to begin localization activities? Should my company wait until the release of the English version?

It is vital that you integrate localization in your development cycle rather than treating it as an additional activity to follow the English release of your software. This will not only ensure that your code is developed in a localization-friendly manner from the beginning, but it will also make localization a seamless activity. Globalme’s localization team will help you define a process that will work with your development methodology. As a result, your software will be localized by the time it is ready to go to the customer, thereby eliminating the possibility of dedicating additional resources and/or time for localization at the end. Because this is a very broad topic with many dependencies, we strongly suggest that you contact us for more information. Following recommendations during development will not only save your company time and money, it will also minimize the amount of modifications that may need to be implemented in the future. Give us a call today and let us explain how we can help you.

How can my company ensure that the dialog boxes provide enough room for text expansion?

If you followed localization best practices and designed your dialog boxes for dynamic expansion, you will face far less problems than with a static layout. You can use either text expansion software or pseudo-localization to test character support as translated text tends to expand about 25 to 35 percent. In addition, in certain cases, individual character width may also be an issue.

Does my company need to create new localization test plans or can we use our existing test cases?

This depends on the coverage of your current test plans as localization QA has a different focus. One of Globalme’s experienced localization testing leads can create a test plan for you to cover all of the necessary areas using your existing documents.

My company has specific hardware, software, and platform requirements for testing. What kind of testing equipment do you provide?

Globalme employs testing systems to cover common end user hardware configurations on Windows, Mac, and Linux platforms both as virtual or single installation images. If testing needs to be performed on specific hardware, Globalme’s technical staff will work with your company’s testing team to get our environment ready for testing.

What is Globalme’s process for localizing supporting documentation such as help files, user guides, etc?

Supporting documentation will be localized along with the application; whether it is a PDF document, an online wiki or compiled help files. We always use the ‘same’ translation teams to ensure translation consistency between the user interface and the documentation and if there are screen captures from the UI, they will be replaced with localized versions.