Software GUI localization is an essential part of the localization process for many software companies marketing across languages. Graphical user interface (GUI, pronounced “gooey”) localization refers to translating text strings on a user interface, including icons, windows, dialog boxes, menus, check boxes, and error and status messages. GUIs are ubiquitous; they are used by Mac, Windows, Android, and even most Linux-based operating systems. However, compared with text-based interfaces, a GUI design can present several challenges for downstream localization.

For example, icons designed to fit English text often become too big or too small once localized due to text contraction or expansion. Hardcoded strings, or even bitmap text, usually lead to missing translations in the localized software. Font sizing and formatting of the right-to-left layout also require quality control. To avoid these problems, an experienced software localization service provider must be hired to ensure the best translation quality and the most efficient GUI localization process.

The best localization process usually starts with the software GUI translation. Online help and user documentation translation should only begin after all software GUI strings have been fully translated and reviewed. This is because online help and user manuals frequently reference the software user interface elements. Overall, our work will ensure that all GUI strings are translated consistently for all product components, and through this process, CSOFT helps companies ensure that their products are usable for a diverse audience.

What Can You Do as a Software Developer?

A software developer can do several things to ensure the best outcome for a GUI localization project. Here are just some of them:

• Make sure to select a software development tool that supports international character sets. The development tool should have built-in support for double-byte characters and right-to-left UI (User Interface) layouts for bi-directional languages such as Arabic or Hebrew. Most modern development environments (such as those for iOS, Android, Mac OS , and Windows) support these requirements out of the box, but double-check to make sure.
• Separate all localizable elements from the main source code, a best practice requirement for the MVC (model–view–controller) architecture. MVC divides a given software application into three interconnected parts to separate internal representations of information from the ways that information is presented to or accepted by the user. Isolating localizable resources in a repository, such as a Windows resource file (*.rc), .Net assembly file, or a database when dealing with web content, ensures the greatest project efficiency.
• Make sure that no hardcoded elements/strings (i.e., hardcoded messages, etc.) are used in the code. Hardcoded elements are difficult to localize because they do not appear until the localized software is compiled and executed. Again, all localizable strings should be separated into one or more resource files. The major program elements that require localization include menus, messages, dialog boxes, prompts, images, sounds, toolbars, status bars, and constants.

These are just a few of the many other case-specific considerations when undertaking a GUI localization project, and they can often be overwhelming without expert assistance. If you find yourself drowning in a GUI nightmare, you can contact our software GUI localization experts for a quick rescue.

Cosmetic and Linguistic Validation

Some businesses conduct software GUI localization without requiring a separate localization testing service. While this approach can initially save some time and money, it usually leads to costly localization quality issues down the road, resulting in the need for reworks and delays. This is because linguists usually translate the strings in a tabular environment without the ability to reference the localized GUI in real-time. Once the translated strings are compiled back into the runtime software, slight changes can affect readability; the strings must be linguistically validated to ensure quality. Linguistic validation checks all translations for correctness in context. Some translations may need to be shortened to eliminate truncation and better fit the existing screen real estate. Linguistic validation also checks for missing translations that may have been caused by hardcoded strings or bitmap text.

The localized GUI also needs to undergo cosmetic validation to ensure that all text formatting, layout, and alignment are correct once the foreign language texts are incorporated into the user interface. Dialog boxes need to be adjusted often to better accommodate the localized strings. Other issues, such as corrupted characters, incorrect text wrapping, and inappropriate font/size, must be fixed.

Localized Screenshot Capture

Once the software GUI has been localized, screenshots may be used in user-help documents. This is why the GUI should always be localized before translating user help and other documents starts. Starting with GUI localization will prevent rework on UI string translations that may need to be adjusted during linguistic and cosmetic validation. Furthermore, the localized GUI strings can be compiled into a terminology library to help speed up the translation of user help files.

There are several ways that localized screenshots can be captured efficiently; some are third-party tools, while custom scripts can be written to program automatic screenshot capture. The localization service provider can also take screenshots manually with the aid of a test case or help system.