General LRM FAQ

What is the Lingoport Resource Manager?

Lingoport Resource Manager (LRM) is a software product that bridges the gap between development and localization processes. It is geared toward development organizations tackling globalization of their software they can target international markets. The Lingoport Dashboard utilizes LRM's report capacity to show translation status in a user-friendly display.

On the development side, users can type in shell commands to replace manual and error-prone steps to:

• Hand over resource files to translation.
• Process translated files received from translation.

The shell commands can then be used to automate the processes, for instance, by integrating them into a build environment.

On the project and globalization management side, the Lingoport Dashboard provides an up-to-date status of the resources and their translation by locale. A number of views are presented, with drill-down to the specific issues detected by the Lingoport Resource Manager.

The Dashboard permission settings allows a granular presentation of the Lingoport Resource Manager project so management, development, and/or the translation vendor can each benefit from the status.

What are the Major Benefits?

This list capture some of the major benefits of the Lingoport Resource Manager (LRM):

• LRM integrates seamlessly, sending files from repositories to translation and back.
• LRM automates iterative, non-value-added file management tasks.
• LRM automates validation checking for common errors.
• LRM processes reduces human error.
• LRM provides an intuitive, real-time dashboard status overview for all stakeholders.
• LRM supports ease of deployment and operation.
• LRM bridges the gap between development and localization.
• LRM speeds localized resource turnaround time.
• LRM reduces human resource opportunity cost.
• LRM supports industry-standard development environments.
• LRM enhances Agile localization.

What Does the Lingoport Resource Manager Do?

The Lingoport Resource Manager facilitates and helps automate passing resource files from the development environment to the translation vendor and back. It validates and packages the resources to be sent for translation in a kit. When the corresponding kit is received for a locale, it validates the translated files and helps put the translated files into the source code.

The overall process is managed using Jenkins.

What Resource File Types are Supported?

Version 2.1 of the Resource Manager supports the following file types:

• .json (with some restrictions for L10n purposes - See Release Notes 2.1 - Mostly JavaScript, and other programming languages)
• .msg (C, C++, ...)
• .po files
• .properties files (for instance, Java-type resources)
• .resx files (used in the .Net world)
• .rc (Delphi, ...)
• .rjs (for JavaScript)
• .rxml (for xml)
• .strings (Mobile iOS)
• strings.xml (Android)

Does the Resource Manager Compete with Translation Products?

No. The Resource Manager assists development organizations to automate error prone tasks, manage and track resources for global readiness. The Resource Manager is not a translation tool nor is it a content management system (CMS).

Does the Resource Manager Help with Agile Processes?

The Resource Manager helps automate tasks and provide status on the state of translation in the source code itself. It helps different software development cultures, and in particular Agile processes as the tracking, sending, and receiving of resource kits is facilitated. Non Agile processes do benefit from the Resource Manager.