Yes! The times they are a’changing. Users now run their software apps on android phones and iOS tablets on the move and all over the world. So, software developers now design their applications to not only target the different devices but also with an international customer base in mind. The ability to support multiple languages on both desktop and mobile platforms is now a major development trend in the software business. With Internet and cloud-based solutions, multilingual software products can now be localized and launched globally, and that means a world of revenue for software developers.
Software localization is not as simple as just translating the words that appear in the software GUI (graphic user interface). Quality software localization involves a number of highly specialized processes that systematically localize the GUI strings. The greater the number and complexity of dialog boxes, menus, alert messages, online help and user documentation, more specialized the processes needed to localize in a variety of languages. Great software localization also requires testing the localized software on the target platforms to fix any linguistic, cosmetic and functional errors.
Software GUI Localization refers to the translation of the software’s graphical user interface (GUI) components: dialog boxes, menus, and error and status messages that display on a user's screen. 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 taken care of and reviewed. This is because online help and user manuals often contain numerous references to software user interface elements; with all GUI strings translated, consistency across all documents and for all product components is ensured.
In a typical software localization project, the following GUI components need to be translated:
In modern application development, most of the GUI components are stored in external resource files. These resource files are then compiled into binary executable files. For example, on Windows, .rc files are compiled into .dll files using a compiler such as Visual C++.
CSOFT offers complete support whatever the file format for translation. We work directly with compiled binary executable files to minimize accidental changes to formatting codes within the .rc files. In addition to translating .rc and binary program files, the CSOFT localization engineering team can also help our clients perform localized dialog box resizing and cosmetic and linguistic testing.
Online help is one of the largest translation components for today's localization projects. Online help files have become the medium of choice for the following reasons:
CSOFT is fully capable of localizing any online help system:
Our translators and help publishers are intimately familiar with various components used to build a help system such as hidden text, formatting tags, footnotes, sorted items and cascading style sheets (CSS). CSOFT uses a variety of software tools for each phase of the localization cycle: CAT tools (Trados, Transit, ForeignDesk) for translating the text, help authoring tools (Robohelp, Webworks, Help&Manual, Forehelp) for formatting and engineering the localized help, and testing tools (HelpQA, HTMLQA) for assuring the proper functionality of the help file.
CSOFT offers professional localization testing in addition to our standalone software testing solutions which include internationalization (I18n), functionality, and localization testing.
Localization testing focuses primarily on a product's cosmetic and linguistic characteristics. For example, once localized, the software needs to be verified on different platforms to see if translated options fill in the target dialog boxes and if all hotkeys use unique letters. CSOFT conducts localization testing separately for each target language using a subset of the testing scripts developed for the English version. If such testing scripts are not available, we can also work with our clients to develop a testing strategy such as going through the translated resource files to check every menu, dialog box and message.
Our linguistic testing usually concerns the following issues:
The following is a list of items we test for cosmetic issues:
Need to localize your software? Let the best in the business do it for you!