LRM po Support - Revision history

Llawson: /* Example Project Definition File */

2017-09-18T20:25:26Z

Example Project Definition File

@@ Line 49: / Line 49: @@
 If a unique file extension is a valid po file, then the ''&lt;parser-type&gt;'' should be ''po'' in the project definition file.
-== Example Project Definition File ==
+== Example of Project Definition for Resources ==
    <resource-extensions>
      <resource-extension>
@@ Line 95: / Line 77: @@
      </resource-extension>
    </resource-extensions>

2017-09-01T15:50:13Z

.po uses the po parser type

← Older revision		Revision as of 15:50, 1 September 2017
Line 44:		Line 44:
	Files that use the ''po'' parser are expected to have valid po syntax		Files that use the ''po'' parser are expected to have valid po syntax
	=== .po uses the ''po'' parser type===		=== .po uses the ''po'' parser type===
	When defining a project ~~with~~ .po ~~extension~~, there is no need to define a ''<parser-type>'' as the ''po'' parser will always be used.		When defining a project containing LRM Standard .po resource files, there is no need to define a ''<parser-type>'' as the ''po'' parser will always be used.

	=== unique file extension needs to define ''json'' parser type ===		=== unique file extension needs to define ''json'' parser type ===
	If a unique file extension is a valid po file, then the ''<parser-type>'' should be ''po'' in the project definition file.		If a unique file extension is a valid po file, then the ''<parser-type>'' should be ''po'' in the project definition file.

2017-08-31T23:17:46Z

Example Project Definition File

← Older revision		Revision as of 23:17, 31 August 2017
Line 39:		Line 39:
	msgstr "//record[record]"		msgstr "//record[record]"
	</pre>		</pre>

			== ''po'' parser type ==
			=== valid po syntax ===
			Files that use the ''po'' parser are expected to have valid po syntax
			=== .po uses the ''po'' parser type===
			When defining a project with .po extension, there is no need to define a ''<parser-type>'' as the ''po'' parser will always be used.
			=== unique file extension needs to define ''json'' parser type ===
			If a unique file extension is a valid po file, then the ''<parser-type>'' should be ''po'' in the project definition file.

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

2017-08-31T22:22:50Z

Example Project Definition File

← Older revision		Revision as of 22:22, 31 August 2017
Line 50:		Line 50:
	<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>

2017-08-31T20:59:47Z

Example Project Definition File

← Older revision		Revision as of 20:59, 31 August 2017
Line 63:		Line 63:
	<resource-extensions>		<resource-extensions>
	<resource-extension>		<resource-extension>
			'''<!-- parser-type not needed since .po is a standard LRM extension that maps to the po parser type -->'''
	'''<extension>po</extension>'''		'''<extension>po</extension>'''
	'''<file-name-pattern>*-l_c_v</file-name-pattern>'''		'''<file-name-pattern>*-l_c_v</file-name-pattern>'''
Line 73:		Line 74:
	</resource-extension>		</resource-extension>
	<resource-extension>		<resource-extension>
			'''<!-- parser-type is required because .myext is not a standard LRM extension -->'''
	'''<extension>''myext''</extension>'''		'''<extension>''myext''</extension>'''
	'''''<parser-type>po</parser-type>'''''		'''''<parser-type>po</parser-type>'''''

2017-08-31T20:47:56Z

Example Project Definition File

← Older revision		Revision as of 20:47, 31 August 2017
Line 89:		Line 89:
	</includes>		</includes>
	<excludes>		<excludes>
	<exclude-dir-file>**/src/test</exclude-dir-file>		<exclude-dir-file>/src/test/</exclude-dir-file>
	</excludes>		</excludes>
	</dirset>		</dirset>
	</lrmconf>		</lrmconf>

2017-08-31T20:47:22Z

Example Project Definition File

2017-08-31T20:24:06Z

Example of .po files as well as file extensions using the po parser type

← Older revision		Revision as of 20:24, 31 August 2017
Line 1:		Line 1:
	== Example of .po files as well as file extensions using the po parser type ==		== Example of .po files as well as file extensions using the ''po'' parser type ==
	<pre>		<pre>
	# SOME DESCRIPTIVE TITLE.		# SOME DESCRIPTIVE TITLE.

2017-08-31T19:54:42Z

Example .po files as well as file extensions using the po parser type

← Older revision		Revision as of 19:54, 31 August 2017
Line 1:		Line 1:
	== Example .po files as well as file extensions using the po parser type ==		== Example of .po files as well as file extensions using the po parser type ==
	<pre>		<pre>
	# SOME DESCRIPTIVE TITLE.		# SOME DESCRIPTIVE TITLE.

2017-08-31T19:53:52Z

Example Project Definition File

← Older revision		Revision as of 19:53, 31 August 2017
Line 107:		Line 107:
	<resource-extension>		<resource-extension>
	'''<extension>''myext''</extension>'''		'''<extension>''myext''</extension>'''
	'''<parser-type>po</parser-type>'''		'''''<parser-type>po</parser-type>'''''
	'''<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 -->		<!--If the base resource files use the file-name-pattern in their name -->