Continuous Globalization Whitepaper

Integrate Internationalization and Localization with Agile Development

Continuous GlobalizationDespite the fact that the agile manifesto origins date back to 2001 and forms of extreme programming considerably earlier, the localization industry has lagged in terms of systems and processes that support continuous internationalization and localization. You do find some trail blazing companies who have developed their own systems, often in the form of manually executed scripts and processes. However that is not the same as we see from technology that supports other critical continuous requirements, such as coding quality and security.

Since internationalization and localization are important revenue generating activities and form a pillar of software usability, they should be easy to deliver as part of daily product development activities. The problem is that as development has moved to faster and even continuous release cycles, manual and disconnected localization tasks create departmental discord and backlogs.

The Lingoport Suite continuously measures, visualizes, and automates internationalization and localization at the source code repository and developer desktop and checkin level.

Download our Continuous Globalization white paper, which examines making internationalization and localization integrated and ongoing development activities. We explain the needs, benefits and returns. For access, please use the registration form below and we will email it to you.

Internationalization Projects: Not that Simple

From beginning to end, internationalization projects offer a wide-range of challenges; challenges Lingoport has helped companies overcome since 2001.In this whitepaper, Lingoport’s Globalization Lead Olivier Libouban goes over the complex issues faced during an i18n project and offers examples on how Lingoport has helped companies with their unique challenges. Other points of the white paper include:

  • Expertise required to tackle an i18n project
  • Specific examples on the challenges, process and solutions for i18n faced by companies
  • How application environments, including locale tracking, large databases and various programming languages affect i18n

Path to Agile Localization White Paper

This white paper will cover

  • The causes for friction between development and localization teams during Agile development.
  • How automation technology can be used to allow localization to become an Agile process.
  • Why embracing change instead of resisting it is the key to unlocking Agile localization.

Lingoport Resource Manager: Automated File Management

Lingoport Resource Manager ProcessTypical software localization projects succumb to a system of resource file management that is often inaccurate and time-consuming. Rapid development projects have a constant stream of files being sent from development to localization, prepped and sent to translation, then received, verified and reintegrated to the source code repository. By managing this stream and creating a scalable solution for ongoing releases, globally focused companies are able to avoid this sunken time and ensure that global software releases are ready to go.

This white paper will cover:

  • The manual inefficiency of typical file handling for translatable content
  • How to bridge file management between development and localization
  • Why Agile methodology is significantly helped by localization automation

Measuring Internationalization with Lingoport Dashboard

Lingoport's i18n & L10n Dashboard Product

What gets measured gets done. Period. A recent Lingoport webinar poll revealed that nearly ¾ of all respondents experienced delays in releasing global software products. Getting software products to market late can have a huge impact on a company’s bottom line and can put the company’s reputation on the line.

We invite you to read this white paper and learn how globally oriented enterprises are now able to track, analyze and act on code quality data to avoid costly mistakes using Lingoport Dashboard.

In this white paper, readers will learn:

  • How software producers may better prepare globally sound products
  • Why measuring i18n inefficiencies at the source code will help localization
  • How the dashboard display is intuitive and usable by both developers and managers

Productive Globalization by Shifting Left: Moving the Productivity Pendulum

As meeting global release dates becomes more vital to a company’s bottom line, technology firms are investigating how to better streamline internationalization processes and compliance within software development.

In recent conversations with many respected globalization departments, Lingoport has found that top technology companies are:

  • Investing in software and strategies to track i18n progress
  • Generating methods to track and generate ROI
  • Saving $500 per bug

Keyboards and Internationalization

As software is developed and shipped around the world, how end users enter data becomes a major issues for developers to consider. In this white paper, Lingoport’s Globalization Lead, Olivier Libouban, shares his insight to creating a software-based keyboard that will map to any language.

In this step-by-step piece, readers will learn how to:

  • Switch an application from one locale to another
  • Change keyboard settings with the same hardware keyboard
  • Edit input method editors (IME’s)

I18n JavaScript – the Good, the Bad, and the Ugly

i18n JavaScript: Given JavaScript’s status as the de facto browser client scripting language, and given the international nature of the Internet, it was inevitable that JavaScript and internationalization (i18n) would eventually cross paths. Fortunately, in this day and age of Unicode, character corruption can be avoided if care is taken to make sure JavaScript is using it. Unfortunately, strings are hard coded in JavaScript and locale-specific methods are unpredictable, making localization more difficult.

To continue reading, and to see how JavaScript strings and data formatting can be supported by your selected locale, please fill out the form below. A brief preview:

Assuming currentLocale is set to English (US), the resulting code block should look like this:

Current Locale Resulting Block | Internationalize JavaScript