Terminology Leveraging Step - Revision history

Vmykhalets: /* Limitations */

2017-09-11T14:13:08Z

Limitations

← Older revision		Revision as of 10:13, 11 September 2017
Line 26:		Line 26:
	==Limitations==		==Limitations==

	* ~~None known~~.		* It is '''not''' possible to chain several steps if you want to leverage against several terminology resources.

	[[Category:Steps]]		[[Category:Steps]]

2017-09-11T14:12:46Z

Overview

← Older revision		Revision as of 10:12, 11 September 2017
Line 10:		Line 10:

	* The text units that are flagged as non-translatable are skipped.		* The text units that are flagged as non-translatable are skipped.
	* It is '''not''' possible to chain several steps if you want to leverage against several terminology resources.
	* Terminology resource connector is capable to define its own strategy for generation of glossary entry ids and glossary translation ids.		* Terminology resource connector is capable to define its own strategy for generation of glossary entry ids and glossary translation ids.

2017-09-11T14:12:04Z

Parameters

← Older revision		Revision as of 10:12, 11 September 2017
Line 15:		Line 15:
	==Parameters==		==Parameters==

	~~TODO~~		<cite>Leverage</cite> — Set this option to enable the step. This option allows you to keep the step in your pipeline and to set it on and off.

			<cite>Annotate source</cite> — Set this option to enable the source unit segment annotation with found glossary entries. Annotation will be done if term is found within source segment text.

			<cite>Annotate target</cite> — Set this option to enable the target unit segment annotation with found glossary entries. Annotation will be done if translation of the term is found within target segment text.

			<cite>Connector Class Name</cite> — Select a terminology resource connector. It can be the subclass of the <code>BaseTerminologyConnector</code> abstract class or custom implementation of the <code>ITerminologyQuery</code> interface.

			<cite>Connector Parameters</cite> — Click this button to edit the settings associated to the terminology resource you have selected.

	==Limitations==		==Limitations==

2017-09-11T14:07:28Z

Overview

← Older revision		Revision as of 10:07, 11 September 2017
Line 3:		Line 3:
	==Overview==		==Overview==

	~~TODO~~		This step leverages glossary terms into extracted text units.

			Takes: Filter text unit events. Sends: Filter text unit events.

			This step allows you to send the list of unit segments to a terminology resource and get a list of found glossary terms for corresponding segment, if any is available. The terminology resource should split the segment into source terms or apply any other technique which will provide a list of existing glossary terms found for corresponding segment.

			* The text units that are flagged as non-translatable are skipped.
			* It is '''not''' possible to chain several steps if you want to leverage against several terminology resources.
			* Terminology resource connector is capable to define its own strategy for generation of glossary entry ids and glossary translation ids.

	==Parameters==		==Parameters==

2017-07-24T15:52:57Z

Limitations

2017-07-21T06:09:15Z

Created page with "{{Steps Header}} __TOC__ ==Overview== TODO ==Parameters== TODO ==Limitations== * None known. Category:Steps Category:ITS"

New page

{{Steps Header}}
__TOC__
==Overview==

TODO

==Parameters==

TODO

==Limitations==

* None known.

[[Category:Steps]] [[Category:ITS]]