...
| Service name | Info | Tag handling info | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead, all tags are removed(stripped) from the result and error is logged. | ||||||||||
| Lucy | This MT should be deprecated. The link for the api provided int this issue is no longer valid:
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 placeholder:tag <internalTag> containing id attribute representing the current tag index in the content: <internalTag id="internal-'.($id++).'"/> where $id is the tag index in the current content. After this all other tags then internlTag tags expect <internalTag> are removed and the this content is send for translation. When we receive the content is received, all other tags then internalTag is removed from the received content, and at the end theinternalTag tags 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. | ||||||||
| MS Translator Microsoft | We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead, all tags are removed(stripped) from the result and error is logged. | |||||||||
| Moses | Not used in production. Can be removed if not needed to be listed here. | All tags are removed. | ||||||||
| SDL LanguageCloud | All tags are removed. | |||||||||
| DeepL | We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead, all tags are removed(stripped) from the result and error is logged. | |||||||||
| 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. | ||||||||
| PangeaMT | We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead, all tags are removed(stripped) from the result and error is logged. | |||||||||
| TildeMT | We send tags and in case the tags from the result are wrong, we don't try to repair them. Instead, all tags are removed(stripped) from the result and error is logged. | |||||||||
ZDemoMT | Used for testing and development purposes. | - |
...