LRM rxml Support - Revision history

Llawson: /* xml parser type using RxmlParser.xml format definition */

2017-09-01T19:05:42Z

xml parser type using RxmlParser.xml format definition

← Older revision		Revision as of 19:05, 1 September 2017
Line 16:		Line 16:
	== ''xml'' parser type using RxmlParser.xml format definition ==		== ''xml'' parser type using RxmlParser.xml format definition ==
	=== valid rxml syntax ===		=== valid rxml syntax ===
	Files that use the ''xml'' parser and the RxmlParser.xml format definition are expected to have valid rxml syntax		Files that use the ''xml'' parser and the [[LRM_XML_Support#RxmlParser.xml_structure\|RxmlParser.xml]] format definition are expected to have valid rxml syntax

	=== .rxml uses the ''xml'' parser type===		=== .rxml uses the ''xml'' parser type===

Llawson: /* Example Project Definition File */

2017-09-01T16:09:07Z

Example Project Definition File

@@ Line 13: / Line 13: @@
 </properties>
 </pre>
 == Example Project Definition File ==

Llawson: /* Example Project Definition File */

2017-08-31T22:24:15Z

Example Project Definition File

← Older revision		Revision as of 22:24, 31 August 2017
Line 24:		Line 24:
	<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 .rxml File */

2017-08-31T22:03:41Z

Example .rxml File

← Older revision		Revision as of 22:03, 31 August 2017
Line 1:		Line 1:
	== Example .rxml File ==		== Example .rxml File or a file extension using the ''xml'' parser type and the RxmlParser.xml definition ==
	<pre>		<pre>
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>

Llawson: /* Example Project Definition File */

2017-08-31T21:58:06Z

Example Project Definition File

← Older revision		Revision as of 21:58, 31 August 2017
Line 64:		Line 64:
	<dirset>		<dirset>
	<includes>		<includes>
	<include-dir>/</include-dir>		<include-dir-file>/</include-dir-file>
	</includes>		</includes>
	<excludes>		<excludes>

Llawson: /* Example Project Definition File */

2017-08-31T21:51:42Z

Example Project Definition File

@@ Line 37: / Line 37: @@
    <resource-extensions>
      <resource-extension>
        '''<extension>rxml</extension>'''
        '''<file-name-pattern>*-l_c_v</file-name-pattern>'''
        '''<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>'''
@@ Line 48: / Line 63: @@
    </resource-extensions>
    <dirset>
-    <!--Define the search patterns to include and/or exclude. (Uses Apache Ant pattern search).-->
+   <includes>
-    <!--Examples: -->
+     <include-dir>**/**</include-dir>
-    <!--   A. '**/*.properties' matches all .properties files/dirs in a directory tree.-->
+   </includes>
      <excludes>
-      <!--Directories or files to exclude in the search -->
+     <exclude-dir-file>**/source/bin/**</exclude-dir-file>
-      <!--Examples: -->
+   </excludes>
    </dirset>
   </lrmconf>

Llawson: /* Example Project Definition File */

2017-08-31T21:48:21Z

Example Project Definition File

← Older revision		Revision as of 21:48, 31 August 2017
Line 21:		Line 21:
	<project-name>DemoRxml</project-name>		<project-name>DemoRxml</project-name>
	<project-desc>This is a sample LRM Project definition file, configured for Globalyzer Rxml resource files</project-desc>		<project-desc>This is a sample LRM Project definition file, configured for Globalyzer Rxml resource 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 47:		Line 34:
	<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>rxml</extension>		'''<extension>rxml</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 -->~~		'''<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>'''
	~~<!--then set use-pattern-on-dflt-locale to 1, if not then set to 0-->~~		'''<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>'''
	~~<!--If the base resource files use the file-location-pattern in their name -->~~		'''<localized-file-encoding>UTF-8</localized-file-encoding>'''
	~~<!--then set use-location-pattern-on-dflt-locale to 1, if not then set to 0-->~~		'''<parameter-regex-pattern><![CDATA[%[ds]\|%\d+\$[ds]\|%\{\w+\}]]></parameter-regex-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>
	~~<!--Default pattern for rxml is~~ '~~![CDATA[%[ds]\|%\d+\$[ds]\|%\{\w+\}]]~~'~~-->~~
	<parameter-regex-pattern><![CDATA[%[ds]\|%\d+\$[ds]\|%\{\w+\}]]></parameter-regex-pattern>
	</resource-extension>		</resource-extension>
	</resource-extensions>		</resource-extensions>

Rdaly: /* Example Project Definition File */

2017-02-02T17:36:29Z

Example Project Definition File

← Older revision		Revision as of 17:36, 2 February 2017
Line 15:		Line 15:

	== Example 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>DemoRxml</project-name>
			<project-desc>This is a sample LRM Project definition file, configured for Globalyzer Rxml resource files</project-desc>
			<!--group-name contains either the company name or the 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>
			<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>
			<parameter-mismatch-error>1</parameter-mismatch-error>
			</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>
			<!--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>
			<!--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>
			<locale>es_MX</locale>
			<locale>fr_CA</locale>
			<locale>fr_FR</locale>
			</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>
			<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>
			<extension>rxml</extension>
			<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>
			<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>
			<base-file-encoding>UTF-8</base-file-encoding>
			<localized-file-encoding>UTF-8</localized-file-encoding>
			<!--Default pattern for rxml is '![CDATA[%[ds]\|%\d+\$[ds]\|%\{\w+\}]]'-->
			<parameter-regex-pattern><![CDATA[%[ds]\|%\d+\$[ds]\|%\{\w+\}]]></parameter-regex-pattern>
			</resource-extension>
			</resource-extensions>
			<dirset>
			<!--Define the search patterns to include and/or exclude. (Uses Apache Ant pattern search).-->
			<!--Examples: -->
			<!-- 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>
			<excludes>
			<!--Directories or files to exclude in the search -->
			<!--Examples: -->
			<!-- <exclude-dir-file>/source/bin/</exclude-dir-file> -->
			<!-- <exclude-dir-file>*/fileToIgnore.</exclude-dir-file> -->
			</excludes>
			</dirset>
			</lrmconf>

Rdaly: /* Example .rxml File */

2017-02-02T17:28:52Z

Example .rxml File

← Older revision		Revision as of 17:28, 2 February 2017
Line 1:		Line 1:
	== Example .rxml File ==		== Example .rxml File ==
			<pre>
			<?xml version="1.0" encoding="UTF-8"?>
			<properties>
			<!--SOURCE_FILE C:/Path/to/source/file/StringBug2.h-->
			<entry xml:space="preserve" key="STRI_MCAFEEC_15"><![CDATA[\\McAfee.com Personal Firewall]]></entry>
			<!--SOURCE_FILE C:/Path/to/source/file/StringBug3.cpp-->
			<entry xml:space="preserve" key="STRI_40FORAL_16"><![CDATA[%40 for all]]></entry>
			<entry xml:space="preserve" key="STRI_WRITELO_18"><![CDATA[Write Log Error]]></entry>
			<!--SOURCE_FILE C:/Path/to/source/file/weird.cpp-->
			<entry xml:space="preserve" key="WEIR_TWASTHE_20"><![CDATA['Twas the night before \"Christmas\"]]></entry>
			<entry xml:space="preserve" key="WEIR_ANDALLT_21"><![CDATA[and all through the house]]></entry>
			</properties>
			</pre>

	== Example Project Definition File ==		== Example Project Definition File ==

Rdaly: Created page with "== Example .rxml File == == Example Project Definition File =="

2017-02-02T16:58:01Z

Created page with "== Example .rxml File == == Example Project Definition File =="

New page

== Example .rxml File ==

== Example Project Definition File ==