LRM rjs Support: Difference between revisions

From Lingoport Wiki
Jump to navigation Jump to search
Line 14: Line 14:
== ''js'' parser type ==
== ''js'' parser type ==
=== valid rjs syntax ===
=== valid rjs syntax ===
Files that use the ''js'' parser are expected to have valid rjs syntax as defined above.
Files that use the ''js'' parser are expected to have valid rjs syntax as defined [[LRM_rjs_Support#Example_.rjs_File|above]].


=== .rjs uses the ''js'' parser type===
=== .rjs uses the ''js'' parser type===

Revision as of 16:06, 1 September 2017

Example .rjs File

// SOURCE_FILE C:/Users/rdaly/Desktop/2016/SmokeTestSource/javascript/FilterPatternOrderTests.js
var FILT_DDMMYYY_7="dd/MM/yyyy";
var FILT_CHCHCHC_8="chchchc";
var FILT_CHCHCHC_9="chchchc";

// SOURCE_FILE C:/Users/rdaly/Desktop/2016/SmokeTestSource/javascript/methods/javascriptmethods.jsp
var JAVA_INSETCM_10="In SetCmd - value = ";
var JAVA_YOUHAVE_11="You have made some changes on this page.  Do you want to continue without saving the changes?";
var JAVA_ENTERAN_12="Enter an evaluation name.\n";

js parser type

valid rjs syntax

Files that use the js parser are expected to have valid rjs syntax as defined above.

.rjs uses the js parser type

When defining a project containing LRM Standard .js extension resource files, there is no need to define a <parser-type> as the js parser will always be used.

unique file extension needs to define js parser type

If a unique file extension is a valid .js file, then the <parser-type> should be js in the project definition file.

Example Project Definition File

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<lrmconf>
 <model-version>2.0.11</model-version>
 <project-name>DemoRjs</project-name>
 <project-desc>This is a sample LRM Project definition file, configured for Globalyzer RJS files</project-desc>
 <group-name>acme</group-name>
 <top-level-dir>C:\acme\source</top-level-dir>
 <detect-errors>
   <missed-trans-error>0</missed-trans-error>
   <parameter-mismatch-error>1</parameter-mismatch-error>
 </detect-errors>
 <track-back-locale>br</track-back-locale>
 <pseudo-locale>eo</pseudo-locale>
 <target-locales>
   <locale>es_MX</locale>
   <locale>fr_CA</locale>
   <locale>fr_FR</locale>
 </target-locales>
 <default-locale>en_US</default-locale>
 <resource-extensions>
   <resource-extension>
     <!-- parser-type not needed since .rjs is a standard LRM extension that maps to the js parser type -->
     <extension>rjs</extension>
     <file-name-pattern>*-l_c_v</file-name-pattern>
     <use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>
     <file-location-pattern/>
     <use-location-pattern-on-dflt-locale>0</use-location-pattern-on-dflt-locale>
     <base-file-encoding>UTF-8</base-file-encoding>
     <localized-file-encoding>UTF-8</localized-file-encoding>
     <parameter-regex-pattern><![CDATA[\{\d+\}|%[ds]]]></parameter-regex-pattern>
   </resource-extension>
   <resource-extension>
     <!-- parser-type is required because .myext is not a standard LRM extension >
     <extension>myext</extension>
     <parser-type>js</parser-type>
     <file-name-pattern>*-l_c_v</file-name-pattern>
     <use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>
     <file-location-pattern/>
     <use-location-pattern-on-dflt-locale>0</use-location-pattern-on-dflt-locale>
     <base-file-encoding>UTF-8</base-file-encoding>
     <localized-file-encoding>UTF-8</localized-file-encoding>
     <parameter-regex-pattern><![CDATA[\{\d+\}|%[ds]]]></parameter-regex-pattern>
   </resource-extension>
 </resource-extensions>
 <dirset>
  <includes>
      <include-dir-file>**/src/**</include-dir-file>
   </includes>
   <excludes>
     <exclude-dir-file>**/src/test/**</exclude-dir-file>
   </excludes>  
  </dirset>
</lrmconf>