Difference between revisions of "About Localyzer"
(→What Does the Lingoport Resource Manager Do?) |
|||
Line 59: | Line 59: | ||
'''Absolutely'''. The Resource Manager helps automate tasks. It also shows the status of the state of translation within the source code itself. It helps different software development cultures, in particular those applying Agile processes, by facilitating the tracking, sending, and receiving of resource kits. Non Agile processes do still benefit from the Resource Manager. |
'''Absolutely'''. The Resource Manager helps automate tasks. It also shows the status of the state of translation within the source code itself. It helps different software development cultures, in particular those applying Agile processes, by facilitating the tracking, sending, and receiving of resource kits. Non Agile processes do still benefit from the Resource Manager. |
||
− | = Components Diagram = |
||
+ | [[Components Diagram|A Typical LRM Deployment]] |
||
− | |||
− | |||
− | |||
− | |||
− | *[[General LRM FAQ|Introduction to LRM]] |
||
− | *[[Components Diagram]] |
||
[[File:Lrm-icon.png]] |
[[File:Lrm-icon.png]] |
Revision as of 23:30, 29 December 2016
Contents
Lingoport Resource Manager Overview
Lingoport Resource Manager (LRM) is a software product that bridges the gap between software development and the localization processes. It is geared toward project development organizations tackling globalization of their software so 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 all benefit from the status.
What are the Major Benefits of LRM?
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 provides a translation status for resource files.
- LRM 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 prep kit.
- When the corresponding prep kit is received for a locale, LRM 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?
Lingoport Resource Manager supports the following file types:
- .json (with some restrictions for L10n purposes - See JSON Resource Bundles - 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 with automating error prone tasks, as well as managing and tracking 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?
Absolutely. The Resource Manager helps automate tasks. It also shows the status of the state of translation within the source code itself. It helps different software development cultures, in particular those applying Agile processes, by facilitating the tracking, sending, and receiving of resource kits. Non Agile processes do still benefit from the Resource Manager.