LRM html Support - Revision history

Llawson: /* LRM interaction with html parser type files */

2019-11-18T17:19:27Z

LRM interaction with html parser type files

← Older revision		Revision as of 17:19, 18 November 2019
Line 28:		Line 28:

	===Number of keys in file is 1 ===		===Number of keys in file is 1 ===
	All files that are parsed using the ''html'' parser have only 1 key called '''key1'''. The value that corresponds to this key is the entire html type file. Because there are no key/values pairs ''html'' parsed files cannot be instrumented (used in our InContext Reviewer/Translation product).		All files that are parsed using the ''html'' parser have only 1 key called '''key1'''. The value that corresponds to this key is the entire html type file. Because there are no key/values pairs, ''html'' parsed files cannot be instrumented (used in our InContext Reviewer/Translation product).
	=== Prep kit files are always full file ===		=== Prep kit files are always full file ===
	If the checksum of the base file has changed then the file will be sent out in the next prep kit for all target locales. Since the file contains only 1 key, the entire file will be sent out for translation.		If the checksum of the base file has changed then the file will be sent out in the next prep kit for all target locales. Since the file contains only 1 key, the entire file will be sent out for translation.

Llawson: /* XHTML - well-formed xml needs to define html parser type */

2019-11-18T17:19:00Z

XHTML - well-formed xml needs to define html parser type

← Older revision		Revision as of 17:19, 18 November 2019
Line 23:		Line 23:

	=== ''XHTML'' - well-formed xml needs to define ''html'' parser type ===		=== ''XHTML'' - well-formed xml needs to define ''html'' parser type ===
	A well-formed document in XML can be parsed by the ''html'' parser type. If there are well-defined keys/values, such as in a ''.resx'' or ''strings.xml'' file then the [[LRM_xml_Support\|''xml'']] parser type should be used.		A well-formed document in XML, such as .dita files, can be parsed by using the ''html'' parser type. If there are well-defined keys/values, such as in a ''.resx'' or ''strings.xml'' file then the [[LRM_xml_Support\|''xml'']] parser type should be used.

	== LRM interaction with html parser type files ==		== LRM interaction with html parser type files ==

Llawson: /* LRM interaction with html parser type files */

2019-11-18T17:18:14Z

LRM interaction with html parser type files

← Older revision		Revision as of 17:18, 18 November 2019
Line 28:		Line 28:

	===Number of keys in file is 1 ===		===Number of keys in file is 1 ===
	All files that are parsed using the ''html'' parser have only 1 key called '''key1'''. The value that corresponds to this key is the entire html type file.		All files that are parsed using the ''html'' parser have only 1 key called '''key1'''. The value that corresponds to this key is the entire html type file. Because there are no key/values pairs ''html'' parsed files cannot be instrumented (used in our InContext Reviewer/Translation product).
	=== Prep kit files are always full file ===		=== Prep kit files are always full file ===
	If the checksum of the base file has changed then the file will be sent out in the next prep kit for all target locales. Since the file contains only 1 key, the entire file will be sent out for translation.		If the checksum of the base file has changed then the file will be sent out in the next prep kit for all target locales. Since the file contains only 1 key, the entire file will be sent out for translation.
			=== File can be pseudo-localized and number of words counted ===
			Since LRM is able to parse the text portion of ''html'' parsed files, the files can be pseudo-localized and the number of words counted.

	== Example of Project Definition for Resources ==		== Example of Project Definition for Resources ==

Llawson: /* XHTML - well-formed xml needs to define html parser type */

2019-11-18T17:11:49Z

XHTML - well-formed xml needs to define html parser type

← Older revision		Revision as of 17:11, 18 November 2019
Line 23:		Line 23:

	=== ''XHTML'' - well-formed xml needs to define ''html'' parser type ===		=== ''XHTML'' - well-formed xml needs to define ''html'' parser type ===
	A well-formed document in XML can be parsed by the ''html'' parser type. If there are well-defined keys/values, such as in a ''.resx'' or ''strings.xml'' file then the ''xml'' parser type should be used~~. See..~~.		A well-formed document in XML can be parsed by the ''html'' parser type. If there are well-defined keys/values, such as in a ''.resx'' or ''strings.xml'' file then the [[LRM_xml_Support\|''xml'']] parser type should be used.

	== LRM interaction with html parser type files ==		== LRM interaction with html parser type files ==

Llawson: /* html parser type */

2019-11-18T17:08:19Z

html parser type

← Older revision		Revision as of 17:08, 18 November 2019
Line 21:		Line 21:
	=== unique file extension needs to define ''html'' parser type ===		=== unique file extension needs to define ''html'' parser type ===
	If a unique file extension is a valid html file, then the ''<parser-type>'' should be ''html'' in the project definition file.		If a unique file extension is a valid html file, then the ''<parser-type>'' should be ''html'' in the project definition file.

			=== ''XHTML'' - well-formed xml needs to define ''html'' parser type ===
			A well-formed document in XML can be parsed by the ''html'' parser type. If there are well-defined keys/values, such as in a ''.resx'' or ''strings.xml'' file then the ''xml'' parser type should be used. See...

	== LRM interaction with html parser type files ==		== LRM interaction with html parser type files ==

Llawson: /* Examples of .html or .htm Files or a file extension that uses the html parser type */

2019-11-18T17:03:44Z

Examples of .html or .htm Files or a file extension that uses the html parser type

← Older revision		Revision as of 17:03, 18 November 2019
Line 10:		Line 10:
	<p>This is a html text fragment</p>		<p>This is a html text fragment</p>
	</body>		</body>


	</pre>		</pre>

Llawson: /* Example .html or .htm File or a file extension that uses the html parser type */

2019-11-18T17:03:31Z

Example .html or .htm File or a file extension that uses the html parser type

← Older revision		Revision as of 17:03, 18 November 2019
Line 1:		Line 1:
	== ~~Example~~ .html or .htm ~~File~~ or a file extension that uses the ''html'' parser type ==		== Examples of .html or .htm Files or a file extension that uses the ''html'' parser type ==
	<pre>		<pre>
			1.
	<html>		<html>
	<p>This is some text in an html file</p>		<p>This is some text in an html file</p>
	</html>		</html>

			2.
			<body>
			<p>This is a html text fragment</p>
			</body>


	</pre>		</pre>

	== ''html'' parser type ==		== ''html'' parser type ==
	=== valid html syntax ===		=== valid html syntax ===

Llawson: /* Example of Project Definition for Resources */

2018-11-27T23:20:47Z

Example of Project Definition for Resources

Llawson: /* Example Project Definition File */

2017-09-18T20:27:17Z

Example Project Definition File

@@ Line 22: / Line 22: @@
 If the checksum of the base file has changed then the file will be sent out in the next prep kit for all target locales. Since the file contains only 1 key, the entire file will be sent out for translation.
-== 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 .html is a standard LRM extension that maps to the ''html'' parser type --&gt;'''
@@ Line 79: / Line 61: @@
      </resource-extension>
    </resource-extensions>

Llawson: /* htm/html uses the html parser type */

2017-09-01T15:47:37Z

htm/html uses the html parser type

← Older revision		Revision as of 15:47, 1 September 2017
Line 10:		Line 10:

	=== htm/html uses the ''html'' parser type===		=== htm/html uses the ''html'' parser type===
	When defining a project containing LRM Standard .html or .html ~~extension~~ resource files, there is no need to define a ''<parser-type>'' as the ''html'' parser will always be used.		When defining a project containing LRM Standard .html or .html resource files, there is no need to define a ''<parser-type>'' as the ''html'' parser will always be used.

	=== unique file extension needs to define ''html'' parser type ===		=== unique file extension needs to define ''html'' parser type ===

← Older revision		Revision as of 23:20, 27 November 2018
Line 29:		Line 29:
	'''<!-- parser-type not needed since .html is a standard LRM extension that maps to the ''html'' parser type -->'''		'''<!-- parser-type not needed since .html is a standard LRM extension that maps to the ''html'' parser type -->'''
	'''<extension>html</extension>'''		'''<extension>html</extension>'''
	~~'''~~<file-name-pattern>*-l_c_v</file-name-pattern>~~'''~~		<file-name-pattern>*-l_c_v</file-name-pattern>
	~~'''~~<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>l_c_v</file-location-pattern>~~'''~~		<file-location-pattern>l_c_v</file-location-pattern>
	~~'''~~<use-location-pattern-on-dflt-locale>1</use-location-pattern-on-dflt-locale>~~'''~~		<use-location-pattern-on-dflt-locale>1</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>
	~~'''~~<parameter-regex-pattern></parameter-regex-pattern>~~'''~~		<parameter-regex-pattern></parameter-regex-pattern>
	</resource-extension>		</resource-extension>
	<resource-extension>		<resource-extension>
	'''<!-- parser-type not needed since .htm is a standard LRM extension that maps to the ''html'' parser type -->'''		'''<!-- parser-type not needed since .htm is a standard LRM extension that maps to the ''html'' parser type -->'''
	'''<extension>htm</extension>'''		'''<extension>htm</extension>'''
	~~'''~~<file-name-pattern>*-l_c_v</file-name-pattern>~~'''~~		<file-name-pattern>*-l_c_v</file-name-pattern>
	~~'''~~<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>l_c_v</file-location-pattern>~~'''~~		<file-location-pattern>l_c_v</file-location-pattern>
	~~'''~~<use-location-pattern-on-dflt-locale>1</use-location-pattern-on-dflt-locale>~~'''~~		<use-location-pattern-on-dflt-locale>1</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>
	~~'''~~<parameter-regex-pattern></parameter-regex-pattern>~~'''~~		<parameter-regex-pattern></parameter-regex-pattern>
	</resource-extension>		</resource-extension>
	<resource-extension>		<resource-extension>
Line 52:		Line 52:
	'''<extension>''myext''</extension>'''		'''<extension>''myext''</extension>'''
	'''''<parser-type>html</parser-type>'''''		'''''<parser-type>html</parser-type>'''''
	~~'''~~<file-name-pattern>*-l_c_v</file-name-pattern>~~'''~~		<file-name-pattern>*-l_c_v</file-name-pattern>
	~~'''~~<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>l_c_v</file-location-pattern>~~'''~~		<file-location-pattern>l_c_v</file-location-pattern>
	~~'''~~<use-location-pattern-on-dflt-locale>1</use-location-pattern-on-dflt-locale>~~'''~~		<use-location-pattern-on-dflt-locale>1</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>
	~~'''~~<parameter-regex-pattern></parameter-regex-pattern>~~'''~~		<parameter-regex-pattern></parameter-regex-pattern>
	</resource-extension>		</resource-extension>
	</resource-extensions>		</resource-extensions>