Localization

Because of the multitude of different programming languages, programming approaches, and design preferences, a "standard" localization project does not exist. The most important aspect of any website or software localization is thus to approach the project with the flexibility and capability to find a custom solution.

Our IT staff can draw on hands-on experience with application configuration in Unix, Windows and Macintosh environments, programming in Java, C++, and various scripting languages, website design with HTML and related markup languages with client-side and server-side scripting, as well as interfacing with relational (SQL) and object-oriented databases.

While we own and use a variety of localization-specific software utilities, we find that most projects can be handled with standard word processing and translation tools. We provide initial consulting to prepare your software or your Website for internationalization, and throughout the project we collaborate with your engineers at the level of involvement that suits you.

Case Studies

Website Localization: Translating at the Speed of Business

It is a fast-paced world out there. Our clients are continually amazed at how quickly we can translate and turn around their projects. GE Medical Systems was developing a new product client website to incorporate its focus on complete digitization. They needed a Japanese translation truly "as soon as possible." The Geo Group used a "translation memory" database specifically created from past GE translation projects, immediately translating an entire website, allowing us to deliver a final, flawless translation in days.

Software Localization: Customized Processes Save Time and Money

One Geo client uses a web-based application to control scoring and reporting on workstations in large bowling alleys. The user interface consists of Active Server Pages, which were to be translated. We initially approached the project similar to a website translation, which would have involved processing of almost 300 files. During our on-site discussions with the engineer, it turned out that the programmers were using a custom-written text extraction tool for maintaining the interface strings that used a database for storage. We decided to translate a single database export file instead, which significantly reduced both cost and time.