LRM rjs Support - Revision history

Olibouban at 16:59, 7 January 2019

2019-01-07T16:59:52Z

← Older revision		Revision as of 16:59, 7 January 2019
Line 1:		Line 1:
			rjs is a deprecated format. rjs files are generated by Globalyzer Workbench and this format has been superseded by .json string externalization as a more standardized format for JavaScript.

	== Example .rjs File ==		== Example .rjs File ==
	<pre>		<pre>

Llawson: /* Example Project Definition File */

2017-09-18T20:26:50Z

Example Project Definition File

@@ Line 22: / Line 22: @@
 If a unique file extension is a valid .js file, then the ''&lt;parser-type&gt;'' should be ''js'' in the project definition file.
-== Example Project Definition File ==
+== Example of Project Definition for Resources ==
- <?xml version="1.0" encoding="UTF-8" standalone="no"?>
+   <resource-extensions>
      <resource-extension>
        '''&lt;!-- parser-type not needed since .rjs is a standard LRM extension that maps to the ''js'' parser type --&gt;'''
@@ Line 68: / Line 50: @@
      </resource-extension>
    </resource-extensions>

Llawson: /* .rjs uses the js parser type */

2017-09-01T16:06:36Z

.rjs uses the js parser type

← Older revision		Revision as of 16:06, 1 September 2017
Line 17:		Line 17:

	=== .rjs uses the ''js'' parser type===		=== .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.		When defining a project containing LRM Standard '''.rjs''' 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 ===		=== 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.		If a unique file extension is a valid .js file, then the ''<parser-type>'' should be ''js'' in the project definition file.

Llawson: /* valid rjs syntax */

2017-09-01T16:06:18Z

valid rjs syntax

← Older revision		Revision as of 16:06, 1 September 2017
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===

Llawson: /* valid js syntax */

2017-09-01T16:05:52Z

valid js syntax

← Older revision		Revision as of 16:05, 1 September 2017
Line 13:		Line 13:

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

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

Llawson: /* Example Project Definition File */

2017-09-01T16:01:31Z

Example Project Definition File

← Older revision		Revision as of 16:01, 1 September 2017
Line 11:		Line 11:
	var JAVA_ENTERAN_12="Enter an evaluation name.\n";		var JAVA_ENTERAN_12="Enter an evaluation name.\n";
	</pre>		</pre>

			== ''js'' parser type ==
			=== valid js syntax ===
			Files that use the ''js'' parser are expected to have valid js syntax

			=== .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 ==		== Example Project Definition File ==

Llawson: /* Example Project Definition File */

2017-08-31T22:23:54Z

Example Project Definition File

← Older revision		Revision as of 22:23, 31 August 2017
Line 22:		Line 22:
	<top-level-dir>C:\acme\source</top-level-dir>		<top-level-dir>C:\acme\source</top-level-dir>
	<detect-errors>		<detect-errors>
	<missed-trans-error>1</missed-trans-error>		<missed-trans-error>0</missed-trans-error>
	<parameter-mismatch-error>1</parameter-mismatch-error>		<parameter-mismatch-error>1</parameter-mismatch-error>
	</detect-errors>		</detect-errors>

Llawson: /* Example Project Definition File */

2017-08-31T21:39:03Z

Example Project Definition File

← Older revision		Revision as of 21:39, 31 August 2017
Line 35:		Line 35:
	<resource-extensions>		<resource-extensions>
	<resource-extension>		<resource-extension>
	<extension>rjs</extension>		'''<!-- parser-type not needed since .rjs is a standard LRM extension that maps to the ''js'' parser type -->'''
	<file-name-pattern>*-l_c_v</file-name-pattern>		'''<extension>rjs</extension>'''
	<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>		'''<file-name-pattern>*-l_c_v</file-name-pattern>'''
	<file-location-pattern/>		'''<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>'''
	<use-location-pattern-on-dflt-locale>0</use-location-pattern-on-dflt-locale>		'''<file-location-pattern/>'''
	<base-file-encoding>UTF-8</base-file-encoding>		'''<use-location-pattern-on-dflt-locale>0</use-location-pattern-on-dflt-locale>'''
	<localized-file-encoding>UTF-8</localized-file-encoding>		'''<base-file-encoding>UTF-8</base-file-encoding>'''
	<parameter-regex-pattern><![CDATA[\{\d+\}\|%[ds]]]></parameter-regex-pattern>		'''<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-extension>
	</resource-extensions>		</resource-extensions>

Llawson: /* Example Project Definition File */

2017-08-31T21:35:49Z

Example Project Definition File

← Older revision		Revision as of 21:35, 31 August 2017
Line 51:		Line 51:
	<excludes>		<excludes>
	<exclude-dir-file>/src/test/</exclude-dir-file>		<exclude-dir-file>/src/test/</exclude-dir-file>
	</excludes> </dirset>		</excludes>
			</dirset>
	</lrmconf>		</lrmconf>

Llawson: /* Example Project Definition File */

2017-08-31T21:14:58Z

Example Project Definition File

← Older revision		Revision as of 21:14, 31 August 2017
Line 19:		Line 19:
	<project-name>DemoRjs</project-name>		<project-name>DemoRjs</project-name>
	<project-desc>This is a sample LRM Project definition file, configured for Globalyzer RJS files</project-desc>		<project-desc>This is a sample LRM Project definition file, configured for Globalyzer RJS files</project-desc>
	~~<!--group-name contains either the company name or the group name. -->~~
	<group-name>acme</group-name>		<group-name>acme</group-name>
	~~<!-- Example, linux -->~~
	~~<!--<top-level-dir>/var/lib/job/workspace/acme/source</top-level-dir>-->~~
	<top-level-dir>C:\acme\source</top-level-dir>		<top-level-dir>C:\acme\source</top-level-dir>
	<detect-errors>		<detect-errors>
	~~<!--If set to '0' (false), then the 'missed translation' error will not be triggered-->~~
	~~<!--if the non-base file has the same text as the base file.-->~~
	~~<!--Missed Translation error will still occur if the base file has a different key or if-->~~
	~~<!--the base file has changed since it was last prepped.-->~~
	<missed-trans-error>1</missed-trans-error>		<missed-trans-error>1</missed-trans-error>
	<parameter-mismatch-error>1</parameter-mismatch-error>		<parameter-mismatch-error>1</parameter-mismatch-error>
	</detect-errors>		</detect-errors>
	~~<!--If you wish to create Track Back resource files, enter the Track Back locale such as `br`-->~~
	~~<!--The track back locale is mutually exclusive of the base (default) locale, target locales and pseudo-locale-->~~
	<track-back-locale>br</track-back-locale>		<track-back-locale>br</track-back-locale>
	~~<!--If you wish to pseudo-localized your files enter a pseudo-locale-->~~
	~~<!--The pseudo-locale is mutually exclusive of the base (default) locale and target locales-->~~
	<pseudo-locale>eo</pseudo-locale>		<pseudo-locale>eo</pseudo-locale>
	~~<!--Target locales are the locales where the corresponding resource files will be translated. -->~~
	~~<!--These target locales are mutually exclusive of the base (default) locale-->~~
	<target-locales>		<target-locales>
	<locale>es_MX</locale>		<locale>es_MX</locale>
Line 45:		Line 32:
	<locale>fr_FR</locale>		<locale>fr_FR</locale>
	</target-locales>		</target-locales>
	~~<!--Default locale is the base locale. This is the locale where corresponding resource files will not be translated.-->~~
	~~<!--The base (default) locale is mutually exclusive of the target locales-->~~
	<default-locale>en_US</default-locale>		<default-locale>en_US</default-locale>
	<resource-extensions>		<resource-extensions>
	~~<!--The file-name-pattern and/or file-location-pattern indicate the pattern of the-->~~
	~~<!--localized file names (file-name-pattern) and the localized folder names (file-location-pattern).-->~~
	~~<!--If the names contain the locale then a pattern of 1,c and v will be used.-->~~
	~~<!--If the names contain the Locale ID then LCID will be used.-->~~
	~~<!--Example pattern using locale-->~~
	~~<!-- If your localized resource files use their locale in their names then the locale pattern will-->~~
	~~<!-- be used where l stands for language; c for country; v for variant; and the characters between-->~~
	~~<!-- are used as the separator characters.-->~~
	~~<!-- <file-name-pattern>*_l_c_v</file-name-pattern>-->~~
	~~<!--Example pattern using LCID (locale ID)-->~~
	~~<!-- If your resource files are under a folder named 'resources' with an LCID suffix separated by an-->~~
	~~<!-- underscore, then the pattern would be:-->~~
	~~<!-- <file-location-pattern>resources_LCID</file-location-pattern>-->~~
	<resource-extension>		<resource-extension>
	<extension>rjs</extension>		<extension>rjs</extension>
	<file-name-pattern>*-l_c_v</file-name-pattern>		<file-name-pattern>*-l_c_v</file-name-pattern>
	~~<!--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-->~~
	<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>		<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>
	<file-location-pattern/>		<file-location-pattern/>
	~~<!--If the base resource files use the file-location-pattern in their name -->~~
	~~<!--then set use-location-pattern-on-dflt-locale to 1, if not then set to 0-->~~
	<use-location-pattern-on-dflt-locale>0</use-location-pattern-on-dflt-locale>		<use-location-pattern-on-dflt-locale>0</use-location-pattern-on-dflt-locale>
	<base-file-encoding>UTF-8</base-file-encoding>		<base-file-encoding>UTF-8</base-file-encoding>
	<localized-file-encoding>UTF-8</localized-file-encoding>		<localized-file-encoding>UTF-8</localized-file-encoding>
	~~<!--Default pattern for rjs is '![CDATA[\{\d+\}\|%[ds]]]'-->~~
	<parameter-regex-pattern><![CDATA[\{\d+\}\|%[ds]]]></parameter-regex-pattern>		<parameter-regex-pattern><![CDATA[\{\d+\}\|%[ds]]]></parameter-regex-pattern>
	</resource-extension>		</resource-extension>
	</resource-extensions>		</resource-extensions>
	<dirset>		<dirset>
	~~<!--Define the search patterns to include and/or exclude. (Uses Apache Ant pattern search).-->~~		<includes>
	~~<!--Examples: -->~~		<include-dir-file>/src/</include-dir-file>
	~~<!-- A. '*/.properties' matches all .properties files/dirs in a directory tree.-->~~
	~~<!-- B. 'test/a??.resx' matches all files/dirs which start with an 'a', -->~~
	~~<!-- then two more characters and then '.resx', in a directory called test.-->~~
	~~<!-- C. '**' matches everything in a directory tree. -->~~
	~~<!-- D. '/source//XYZ*' matches all files/dirs which start with 'XYZ'-->~~
	~~<!-- and where there is a parent directory called source (e.g. 'abc/source/def/ghi/XYZ123'). -->~~
	<includes>
	<~~!--Directories to~~ include ~~in the search for base resource files~~ -->
	~~<!--Examples: -->~~
	~~<!-- <include-dir~~>/~~source~~/</include-dir>-->
	~~<include-dir>/</include-dir~~>
	</includes>		</includes>
	<excludes>		<excludes>
	~~<!--Directories or files to exclude in the search -->~~		<exclude-dir-file>/src/test/</exclude-dir-file>
	~~<!--Examples: -->~~		</excludes> </dirset>
	~~<!--~~ <exclude-dir-file>/~~source/bin~~/</~~exclude-dir-file> -->~~
	<!-- <exclude-dir-file>*~~/fileToIgnore.~~</exclude-dir-file~~> --~~>
	</excludes>
	</dirset>
	</lrmconf>		</lrmconf>