| Service name | Info | Tag handling info | Additional infos |
|---|---|---|---|
We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead if the MT returns a tag error or invalid xml, all tags are removed(stripped) from the result and error is logged. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. | |||
| Lucy | This MT should be deprecated. The link for the api provided int this issue is no longer valid: TINTERNAL-8 - Getting issue details... STATUS This can be removed if not needed to be listed here. | Special tag processing is done for this MT resource. Before sending the content for translation, all translate5 internal tags are replaced with custom tag <internalTag> containing id attribute representing the current tag index in the content: <internalTag id="internal-'.($id++).'"/> After this all tags except <internalTag> are removed and this content is send for translation. When we receive the result, once again we clean up(strip) all other tags expect <internalTag> (in case we did receive something which we did not expect, because we did make sure when sending the content for translation, the content contains only <internalTag>) and after this all <internalTag> are replaced with translate5 internal tags based on previous tag mapping. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. | May be outdated |
| MS Translator Microsoft | We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead if the MT returns a tag error or invalid xml, all tags are removed(stripped) from the result and error is logged. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. | ||
| Moses | Not used in production. Can be removed if not needed to be listed here. | All tags are removed. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. | |
| SDL LanguageCloud | All tags are removed. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. | ||
| DeepL | Tags are send and in case of tag errors, we try to repair them. Since DeepL produces a lot of tag errors (wrong nesting, partially deleted parts of a paired tag, wrong order, etc.) we spend a lot of time in logic, that repairs them. If there should still tag errors remain, they will be listed in translate5s AutoQA section for tag errors. | Terminology integration with translate5 exists. Simply check the check box "DeepL glossary source" for a translate5 TermCollection. Translate5 will then upload the terminology to DeepL for language combinations, where DeepL supports it. For translate5 projects and InstantTranslate usage as well. | |
| GlobalesePreTranslation | This is not typical MT engine. For pre-translation, we convert all task segments to specific xml file and upload them to the remote api. After the process is finished, we will receive the translated file back and we will update the segments in the translate5 task accordingly. | All tags are removed. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. | So far not integrated as language resource. Integration within the import wizard, that is offered, if the Globalese plug-in is activated. |
| PangeaMT | We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead if the MT returns a tag error or invalid xml, all tags are removed(stripped) from the result and error is logged. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. | ||
| TildeMT | We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead if the MT returns a tag error or invalid xml, all tags are removed(stripped) from the result and error is logged. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. | On segment save the segment can be send to Tilde for training on the fly. This can be configured for each task and the default for each language resource in the same way it can be configured for TMs. | |
ZDemoMT | Used for testing and development purposes. | - | This is only for testing, how MT works in translate5. Mainly for testing our development. No meaningful translation output. |
We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead if the MT returns a tag error or invalid xml, all tags are removed(stripped) from the result and error is logged. Potentially resulting tag errors will be listed in translate5s AutoQA section for tag errors. |
Overview
Content Tools