Terminology Leveraging Step: Difference between revisions
Jump to navigation
Jump to search
Vmykhalets (talk | contribs) |
|||
| Line 3: | Line 3: | ||
==Overview== | ==Overview== | ||
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== | ||
Revision as of 10:07, 11 September 2017
Overview
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
TODO
Limitations
- None known.