Difference between revisions of "Supported Resource Bundles"

From Lingoport Wiki
Jump to: navigation, search
(Project Info)
(Include/Exclude Files/Directories)
Line 53: Line 53:
=== Include/Exclude Files/Directories ===
=== Include/Exclude Files/Directories ===
This will create a project called '''wiley''' in the group '''Acme'''. The resource files are located in the '''<code>/var/lib/jenkins/jobs/Acme.wiley/workspace</code>''' directory. The resources are targeting six different locales. The resource files to be translated are .properties files.
This is the LRM project name that will be created. LRM will create a project called com.company.project
This is the LRM group name that the project will be under.
This is the location of the resource files for source code associated with the com.company.project LRM project.
This is the locale to translate '''from'''
This is the locale to translate '''from'''

Revision as of 00:00, 14 September 2017

What resource file types are supported by LRM?

Standard LRM extensions

  • .htm and .html files using the html parser
  • .json (Mostly JavaScript, and other programming languages) using the json parser
  • .msg (C, C++, ...) using the msg parser
  • .po files using the po parser
  • .properties files (Java-type resources) using properties parser
  • .resx files (used in the .Net world) using xml parser and the ResxParser.xml format definition
  • .rc (Delphi, ...) using the rc parser
  • .rjs (for JavaScript) using the js parser
  • .rxml using the xml parser and the RxmlParser.xml format definition)
  • .strings (Mobile iOS) using the strings parser
  • strings.xml (Android) using the xml parser and the AndroidParser.xml format definition

Unique Extensions

Any file extension can be handled by LRM as long as the corresponding parser type is defined. The file must be able to be parsed correctly by the defined parser type or an error will occur. The parser types are:

Lingoport Resource Manager Configuration

LRM creates projects using a Project Definition XML file that contains information about the resources and types for translation. Here is a typical .xml definition for projects with .properties files.

Project Info

Project information includes the following:

  • Project Name - the repository name. This cannot be changed once the project is created.
  • Project desc - description, if any, for the project
  • Group Name - the owner of the repository. This cannot be changed once the project is created.
  • Top Level Directory - The top level directory is an absolute path. Usually it is something like /var/lib/jenkins/jobs/Acme.wiley/workspace. There are times where there is 1 repository for multiple projects. In this case the top level directory may be /var/lib/jenkins/jobs/Acme.wiley/workspace/wileyProject1. This value cannot be changed once the project is created.

This example is the project info for the wiley repository under the Acme group. (Under git, Acme would be the owner of the wiley repo)


Detect Errors Flags


Resource Extensions

Include/Exclude Files/Directories

This is the locale to translate from


Here are the locales which will be translated into


This tells LRM to look for .properties resource files.


Here is a sample Project Definition file to create an LRM project. This example is for .properties files. Additional <resource-extension> stanzas can be added to include other extensions. Samples for the supported extensions can be found in <HOME>/lingoport/lrm-server-x.y/samples.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  <project-desc>This is a sample LRM Project definition file, configured to support Java properties files</project-desc>
  <!--group-name contains the group name that the LRM license is under-->
    <!--If set to '0' (false), then the 'missed translation' error will not be triggered-->
      <!--If the base resource files use the file-name-pattern in their name -->
      <!--then set use-pattern-on-dflt-locale to 1, if not then set to 0-->
      <!--Default pattern for properties is '![CDATA[\{\d+\}|%[ds]]]'-->