Is it simply translating the User Interface content? No, it is more involved than that.
Studies show that the number one factor affecting translation quality is the inconsistent and inaccurate translation of terminology. The traditional process to software string translation involves isolating all text elements first such as GUI strings, dialog box messages, and menu text into external resource files. These files are then sent to the localization service provider (LSP) for translation, typically in a static Excel file or RC (resource file) in either TXT or XML format.
Where the issue lies in this approach is that often times the source language strings go through changes, requiring the corresponding translations to be updated accordingly. Since the strings are stored offline and in static files, scattered on people’s hard drives, translation changes are not automatically captured causing inconsistent and incorrect translations to be introduced to the localized project (different string translations appearing in the GUI, IFUs, online help, and other user-facing content.)
Meet TermWiki Pro
CSOFT’s terminological approach (TermWiki Pro) to software string translation is a modern process that centralizes all software strings on a secured cloud drive that’s accessible by all team members, anywhere and anytime. It supports capabilities for each software string to be translated, reviewed, and approved directly in the system for all to see and reference. Our Term Assist and APIs support automate terminology lookup and check during translation, ensuring total translation consistency between GUI strings and user documentation.
TermWiki Pro is a secure platform that allows software developers to manage the entire software localization lifecycle from initial source string creation to translation, linguistic review and approval.
TermWiki Pro (TWP) allows you to improve translation quality while reducing costs and time-to-market by eliminating costly rework of your translated content.
In addition to the terminology challenge above, ask our CSOFT experts and they will tell you that the following will need to be considered and addressed:
- The formats of how the dates are displayed (day-month-year or is it month-day-year)
- How double-type characters such as Chinese, Japanese and Korean will be managed
- Cultural and regional nuances will need to be adapted
- How about dealing with the different calendar systems where some are based on the lunar months and others on the imperial calendar
- The currency of the different regions will need to be accounted for
- Many more…
Ask our experts. They will be more than happy to have a conversation with you.