...
The analysis / pre-translation of a task is started via the following two operations on a specific task.
URL: | /editor/task/TASK_ID/analysis/operation | |
Available Methods: | PUT only | |
| Purpose: | Starts the analysis of a task | |
Parameters: | internalFuzzy | 0 or 1 if internal fuzzies should be used or not |
| Availability: | public |
URL: | /editor/task/TASK_ID/pretranslation/operation | |
Available Methods: | PUT only | |
| Purpose: | Starts the analysis and pre-translation of a task | |
Parameters: | internalFuzzy | 0 or 1 if internal fuzzies should be used |
| pretranslateMatchrate | number between 0 and 100, the minimum matchrate of a found TM match to be considered as a valid pre-translation | |
| pretranslateTmAndTerm | 0 or 1, defines if TMs and Term Collections should be used for pre-translation | |
| pretranslateMt | 0 or 1, only usable if |
| above pretranslateTmAndTerm is |
| used, defines if MTs should be used also for pre-translation if no usable TM / Term was found | ||
| termtaggerSegment | 0 or 1 if terminology should be marked if a term collection is assigned as well, currently only usable on import | |
| isTaskImport | 0 or 1 defines if call is in import or not, will be removed in the future, since can be loaded from the task as well, only needed when using termtaggerSegment | |
| Availability: | public |