An online application localization service tends to be targeted at dynamic web sites such as market places, online booking systems, business portals, intranets, etc. In fact, this kind of service has a wider scope, potentially covering any centralized online application accessed by a multitude of concurrent users. Although this category of services will mostly be web-based, it nevertheless includes other architectures, such as client/server platforms.

The challenge is a consistent, fast turnaround of multilingual content

The challenge inherent in this service category, which involves platforms that generate revenue, lies in the speed of turnaround. WhP is able to quickly turn around—on an ongoing basis—small amounts of text in multiple languages, while consistently delivering high quality content, for example in connection with a sales promotion lasting only a few days, and soon replaced by another.

Localization should be part of the application's initial development

WhP has the experience and the ability to advise its customers throughout the localization cycle, however, the earlier localization needs are taken into account, the better the result. WhP will often interact with its customers as a consultant during the development phase to maximize localization quality, time and cost efficiency.

All major online frameworks and development platforms – Unicode, HTML, XML, libraries etc. are localization-friendly. Nevertheless, it is best to enable localization features from day one, when the application is first written. Elements for translation should be clearly identified or externalized into libraries for future integration in different text messages, since different languages use different syntactic structures. Early access to the application's beta version allows WhP to produce optimum quality translation.

An efficient process for localizing dynamic information also implies efficient content management by the online application operator. Data for translation will be exported automatically or semi-automatically from the customer's Content Management System (CMS) to WhP's internal workflow and management system; the translated data will be imported back the same way to the CMS.

Two communication systems are currently implemented: pull mode through secured FTP, and web services.

When a service develops into a partnership

WhP keeps in regular contact with the customer throughout the localization process, and allocates a Project Manager as the key contact. This Project Manager submits weekly progress reports, and can call on WhP subject-matter experts whenever necessary.

The WhP Project Manager is also asked to evaluate the performance and the process in place on a regular basis (i.e. quarterly) in order to identify possible improvements that will benefit the customer in terms of cost, speed and quality.

For more information, request our White Paper "Online Dynamic Content".