Difference between revisions of "General LRM FAQ"

From Lingoport Wiki
Jump to: navigation, search
(→‎What problems does Lingoport Resource Manager solve?)
(→‎What Does the Lingoport Resource Manager Do?)
 
(49 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
== What Problems does Lingoport Resource Manager Solve? ==
 +
== What is the Lingoport Resource Manager? ==
−
The Resource Manager bridges the gap between development and localization processes. It replaces some manual and error-prone steps development organization take in order to hand over files to translation or process translated files received from translation.
+
Lingoport Resource Manager (LRM) is a software product that bridges the gap between development and [[Terms_and_Definitions|localization]] processes. It is geared toward development organizations tackling [[Terms_and_Definitions|globalization]] of their software they can target international markets. The [[Terms_and_Definitions|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:
−
Furthermore, the Resource Manager provides to the Lingoport Dashboard an up-to-date status on global market readiness, for use by management, engineering, or translation groups depending on permission settings.
  
   
  +
* Hand over [[Terms_and_Definitions|resource files]] to translation.
−
== What does the Lingoport Resource Manager do? ==
  
  +
* 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.
−
The Lingoport Resource Manager facilitates and helps automate the back and forth of 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 and helps put the translated files into the source code.
  
   
  +
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.
−
== What resource file types are supported? ==
  
   
  +
The [[Terms_and_Definitions|Dashboard]] permission settings allows a granular presentation of the [[Terms_and_Definitions|Lingoport Resource Manager project]] so management, development, and/or the translation vendor can all benefit from the status.
−
Version 1.0 of the Resource Manager supports:
  
−
<ul>
  
−
<li> <b>.properties</b> files (for instance for Java type resources) </li>
  
−
<li><b>.resx</b> files (used in the .Net world)</li>
  
−
<li><b>.po</b> files </li>
  
−
<li><b>.rjs</b> (for JavaScript)</li>
  
−
<li> <b>.rxml</b> (for xml</li>
  
−
<li><b>.rc</b> (Delphi, ...)</li>
  
−
</ul>
  
   
  +
[[File:Footer.png]]
−
== Does the Resource Manager compete with translation products? ==
  
−
No. The Resource Manager helps mostly development organization to automate error prone tasks, manage and track resources for global readiness.
  
−  
−
== 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.
  
   
 
== What are the Major Benefits? ==
  
== What are the Major Benefits? ==
−
This list capture some of the major benefits of the Resource Manager:
 +
This list capture some of the major benefits of the Lingoport Resource Manager (LRM):
  +
−
<ul><li>Automates iterative, non-value-added file management tasks.</li>
  
  +
* LRM integrates seamlessly, sending files from repositories to translation and back.
−
<li>Automates validation checking for common errors.</LI>
  
  +
* LRM automates iterative, non-value-added file management tasks.
−
<li>Reduces human error.</LI>
  
  +
* LRM automates validation checking for common errors.
−
<li>Provides intuitive, real-time dashboard status overview for all stakeholders.</LI>
  
  +
* LRM processes reduces human error.
−
<li>Supports ease of deployment and operation.</LI>
  
  +
* LRM provides an intuitive, real-time dashboard status overview for all stakeholders.
−
<li>Bridges the gap between development and localization.</LI>
  
  +
* LRM supports ease of deployment and operation.
−
<LI>Speeds localized resource turnaround time.</LI>
  
  +
* LRM bridges the gap between development and localization.
−
<LI>Reduces human resource opportunity cost.</LI>
  
  +
* LRM speeds localized resource turnaround time.
−
<LI>Supports industry-standard development environments.</LI>
  
  +
* LRM reduces human resource opportunity cost.
−
</UL>
  
  +
* LRM supports industry-standard development environments.
−
Enhances agile localization
  
  +
* LRM enhances Agile [[Terms_and_Definitions|localization]].
  +
  +
== What Does the Lingoport Resource Manager Do? ==
  +
The Lingoport Resource Manager provides a translation '''status''' for [[Terms_and_Definitions|resource files]] and facilitates and helps '''automate passing resource files from the development environment to the [[Terms_and_Definitions|translation vendor]] and back'''. It validates and packages the resources to be sent for translation in a [[Terms_and_Definitions|prep 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 [[Terms_and_Definitions|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.

Latest revision as of 16:43, 23 December 2016

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 all benefit from the status.

Footer.png

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 provides a translation status for resource files and 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 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?

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.

Retrieved from "http://wiki.lingoport.com/index.php?title=General_LRM_FAQ&oldid=88878"