Difference between revisions of "Resource Files"

From Lingoport Wiki
Jump to: navigation, search
(Unique Extensions)
(Unique Extensions)
Line 35: Line 35:
 
<li><b>[[LRM_strings_Support#strings_parser_type|''strings'']]</b> parser</li>
 
<li><b>[[LRM_strings_Support#strings_parser_type|''strings'']]</b> parser</li>
 
<li><b>[[LRM_text_Support|''text'']]</b> parser</li>
 
<li><b>[[LRM_text_Support|''text'']]</b> parser</li>
<li><b>[[LRM_XML_Support|xml]]</b> parser</li>
+
<li><b>[[LRM_XML_Support|''xml'']]</b> parser</li>
<li><b>[[LRM_yaml_Support|yaml]]</b> parser</li>
+
<li><b>[[LRM_yaml_Support|''yaml'']]</b> parser</li>
 
</ul>
 
</ul>

Revision as of 21:39, 17 June 2019

What resource file types are supported by LRM?

Standard LRM extensions

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.

ExtensionParserType.jpg

Above is an example configuring a Jenkins LRM project. The Extension is 'properties' and the Parser Type is 'properties' so LRM will recognize the file myfile_en_US.properties as a resource file. If the filename is myfile_en_US.prop, that would not be recognized as a properties resource file. Changing the Extension to 'prop' would allow myfile_en_US.prop to be recognized as a properties parser type file.

The parser types are: