LRM resx Support - Revision history

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

2017-09-01T19:05:07Z

xml parser type using ResxParser.xml format definition

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

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

2017-09-01T19:04:25Z

xml parser type using ResxParser.xml format definition

← Older revision		Revision as of 19:04, 1 September 2017
Line 77:		Line 77:
	== ''xml'' parser type using ResxParser.xml format definition ==		== ''xml'' parser type using ResxParser.xml format definition ==
	=== valid resx syntax ===		=== valid resx syntax ===
	Files that use the ''xml'' parser and the ResxParser.xml format definition are expected to have valid resx syntax		Files that use the ''xml'' parser and the [[LRM_XML_Support#Parser_definition_for_Resx_files\|ResxParser.xml]] format definition are expected to have valid resx syntax

	=== .resx uses the ''xml'' parser type===		=== .resx uses the ''xml'' parser type===
Line 92:		Line 92:
	</ul>		</ul>
	</ul>		</ul>


	== Sample LRM Project Definition File for .resx==		== Sample LRM Project Definition File for .resx==

2017-09-01T15:51:37Z

.resx uses the xml parser type

← Older revision		Revision as of 15:51, 1 September 2017
Line 80:		Line 80:

	=== .resx uses the ''xml'' parser type===		=== .resx uses the ''xml'' parser type===
	When defining a project ~~with~~ .resx ~~extension~~, there is no need to define a ''<parser-type>'' as the ''xml'' parser will always be used along with the ResxParser.xml format definition.		When defining a project containing LRM Standard .resx resource files, there is no need to define a ''<parser-type>'' as the ''xml'' parser will always be used along with the ResxParser.xml format definition.

	=== unique file extension needs to define ''xml'' parser type and copy over the ResxParser.xml format definition ===		=== unique file extension needs to define ''xml'' parser type and copy over the ResxParser.xml format definition ===

2017-08-31T23:34:17Z

Sample LRM Project Definition File for .resx

@@ Line 74: / Line 74: @@
    </root>
 </pre>
 == Sample LRM Project Definition File for .resx==

2017-08-31T22:23:25Z

Sample LRM Project Definition File for .resx

← Older revision		Revision as of 22:23, 31 August 2017
Line 84:		Line 84:
	<top-level-dir>/var/lib/jenkins/jobs/Lingoport.WinApp/workspace</top-level-dir>		<top-level-dir>/var/lib/jenkins/jobs/Lingoport.WinApp/workspace</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-31T22:04:26Z

Example of .resx Files

← Older revision		Revision as of 22:04, 31 August 2017
Line 27:		Line 27:
	</pre>		</pre>

	== Example of .resx Files ==		== Example of .resx Files or a file extension that uses the ''xml'' parser type and the ResxParser.xml definition ==
	<pre>		<pre>
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>

2017-08-31T21:57:14Z

Sample LRM Project Definition File for .resx

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

2017-08-31T21:45:30Z

Sample LRM Project Definition File for .resx

← Older revision		Revision as of 21:45, 31 August 2017
Line 110:		Line 110:
	'''<!-- parser-type is required because .myext is not a standard LRM extension -->'''		'''<!-- parser-type is required because .myext is not a standard LRM extension -->'''
	'''<extension>''myext''</extension>'''		'''<extension>''myext''</extension>'''
			'''''<!-- Once the project is created, the ResxParser.xml, located in the samples/XmlParserExamples, '''''
			''''' needs to copied over the project's config folder and renamed xmlParser.xml -->'''''
	'''''<parser-type>xml</parser-type>'''''		'''''<parser-type>xml</parser-type>'''''
	'''<file-name-pattern>*.l-c-v</file-name-pattern>'''		'''<file-name-pattern>*.l-c-v</file-name-pattern>'''

2017-08-31T21:03:03Z

Sample LRM Project Definition File for .resx

@@ Line 97: / Line 97: @@
    <resource-extensions>
       <resource-extension>
        '''<extension>resx</extension>'''
        '''<file-name-pattern>*.l-c-v</file-name-pattern>'''
        '''<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>'''

2017-02-02T16:29:23Z

What is resx files encoding?

← Older revision		Revision as of 16:29, 2 February 2017
Line 7:		Line 7:
	== What is resx files encoding?==		== What is resx files encoding?==
	.Net resx files must be UTF-8 encoded, as per the resx schema, Hence, on-boarding resx resource files with LRM must specify the UTF-8 encoding:		.Net resx files must be UTF-8 encoded, as per the resx schema, Hence, on-boarding resx resource files with LRM must specify the UTF-8 encoding:


	~~https://msdn.microsoft.com/en-us/library/ekyft91f%28v=VS.90%29.aspx~~

	<pre>		<pre>
Line 29:		Line 26:

	</pre>		</pre>

	== Example of .resx Files ==		== Example of .resx Files ==
	<pre>		<pre>