LRM text Support - Revision history

Llawson: /* File can be pseudo-localized and number of words counted */

2019-11-18T18:51:49Z

File can be pseudo-localized and number of words counted

← Older revision		Revision as of 18:51, 18 November 2019
Line 16:		Line 16:
	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 ===		=== File can be pseudo-localized and number of words counted ===
	The entire file is treated as text and as such, the entire file is pseudo-localized. If this is not appropriate for the file, then perhaps the '''binary'' parser type would be a better fit.		The entire file is treated as text and as such, the entire file is pseudo-localized. If this is not appropriate for the file, then perhaps the [[LRM_Binary_Support\|''binary'']] parser type would be a better fit.

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

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

2019-11-18T18:21:21Z

LRM interaction with text parser type files

← Older revision		Revision as of 18:21, 18 November 2019
Line 12:		Line 12:

	===Number of keys in file is 1 ===		===Number of keys in file is 1 ===
	All files that are parsed using the ''text'' parser have only 1 key called '''key1'''. The value that corresponds to this key is the entire text ~~file~~.		All files that are parsed using the ''text'' 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, ''text'' 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 ===
			The entire file is treated as text and as such, the entire file is pseudo-localized. If this is not appropriate for the file, then perhaps the '''binary'' parser type would be a better fit.

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

Llawson: /* unique file extension needs to define text parser type */

2018-12-10T21:54:07Z

unique file extension needs to define text parser type

← Older revision		Revision as of 21:54, 10 December 2018
Line 6:		Line 6:
	When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.		When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.

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

Llawson: /* txt file extension use the text parser type */

2018-12-10T21:53:55Z

txt file extension use the text parser type

← Older revision		Revision as of 21:53, 10 December 2018
Line 3:		Line 3:
	--- and some more text		--- and some more text

	=== txt file extension use the ''text'' parser type===		== txt file extension use the ''text'' parser type==
	When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.		When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.

Llawson: /* txt file extension use the text parser type */

2018-12-10T21:53:35Z

txt file extension use the text parser type

← Older revision		Revision as of 21:53, 10 December 2018
Line 1:		Line 1:
			== Example of a file extension that uses the ''text'' parser type ==
			This is just a file that contains some text
			--- and some more text

	=== txt file extension use the ''text'' parser type===		=== txt file extension use the ''text'' parser type===
	When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.		When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.

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

2018-11-27T23:26:37Z

Example of Project Definition for Resources

@@ Line 18: / Line 18: @@
      <resource-extension>
        '''&lt;!-- parser-type not needed since .text is a standard LRM extension that maps to the ''text'' parser type --&gt;'''
        '''<extension>txt</extension>'''
        <file-name-pattern>*-l_c_v</file-name-pattern>

Llawson: /* text/txt file extension use the text parser type */

2018-11-27T23:25:52Z

text/txt file extension use the text parser type

← Older revision		Revision as of 23:25, 27 November 2018
Line 1:		Line 1:
	=== ~~text/~~txt file extension use the ''text'' parser type===		=== txt file extension use the ''text'' parser type===
	When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.		When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.

Llawson: /* text/txt file extension use the text parser type */

2018-11-27T23:25:34Z

text/txt file extension use the text parser type

← Older revision		Revision as of 23:25, 27 November 2018
Line 1:		Line 1:
	=== text/txt file extension use the ''text'' parser type===		=== text/txt file extension use the ''text'' parser type===
	When defining a project containing LRM Standard .txt ~~or .text~~ resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.		When defining a project containing LRM Standard .txt resource files, there is no need to define a ''<parser-type>'' as the ''text'' parser will always be used.

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

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

2018-11-27T23:19:03Z

Example of Project Definition for Resources

Llawson: Created page with "=== text/txt file extension use the ''text'' parser type=== When defining a project containing LRM Standard .txt or .text resource files, there is no need to define a ''<pa..."

2018-11-27T23:15:42Z

Created page with "=== text/txt file extension use the ''text'' parser type=== When defining a project containing LRM Standard .txt or .text resource files, there is no need to define a ''<pa..."

New page

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

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

== LRM interaction with text parser type files ==

===Number of keys in file is 1 ===
All files that are parsed using the ''text'' parser have only 1 key called '''key1'''. The value that corresponds to this key is the entire text 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.

== Example of Project Definition for Resources ==
The following is an example of text resource file definitions. See [[Supported_Resource_Bundles#Resource_Extensions| resource extensions]] for more information.

<resource-extensions>
<resource-extension>
''''''
'''<extension>text</extension>'''
'''<file-name-pattern>*-l_c_v</file-name-pattern>'''
'''<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>'''
'''<file-location-pattern>l_c_v</file-location-pattern>'''
'''<use-location-pattern-on-dflt-locale>1</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></parameter-regex-pattern>'''
</resource-extension>
<resource-extension>
''''''
'''<extension>txt</extension>'''
'''<file-name-pattern>*-l_c_v</file-name-pattern>'''
'''<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>'''
'''<file-location-pattern>l_c_v</file-location-pattern>'''
'''<use-location-pattern-on-dflt-locale>1</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></parameter-regex-pattern>'''
</resource-extension>
<resource-extension>
''''''
'''<extension>''myext''</extension>'''
'''''<parser-type>text</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>l_c_v</file-location-pattern>'''
'''<use-location-pattern-on-dflt-locale>1</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></parameter-regex-pattern>'''
</resource-extension>
</resource-extensions>

← Older revision		Revision as of 23:19, 27 November 2018
Line 19:		Line 19:
	'''<!-- parser-type not needed since .text is a standard LRM extension that maps to the ''text'' parser type -->'''		'''<!-- parser-type not needed since .text is a standard LRM extension that maps to the ''text'' parser type -->'''
	'''<extension>text</extension>'''		'''<extension>text</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 .txt is a standard LRM extension that maps to the ''text'' parser type -->'''		'''<!-- parser-type not needed since .txt is a standard LRM extension that maps to the ''text'' parser type -->'''
	'''<extension>txt</extension>'''		'''<extension>txt</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 42:		Line 42:
	'''<extension>''myext''</extension>'''		'''<extension>''myext''</extension>'''
	'''''<parser-type>text</parser-type>'''''		'''''<parser-type>text</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>